The broadcast_uri is NULL in my testing environments. The API works well. Also, according to the code, it should not be a problem if the broadcast_uri is NULL.
Strange. On Sat, Jun 15, 2024 at 1:37 PM Curious Pandora <p4nd...@gmail.com> wrote: > > All entries from select id,vnet from op_dc_vnet_alloc are populated. > > For the second query we have the same results as before: > > +-----+-----------------------------+---------------+ > | id | name | broadcast_uri | > +-----+-----------------------------+---------------+ > | 200 | NULL | NULL | > | 201 | NULL | NULL | > | 202 | NULL | NULL | > | 203 | NULL | NULL | > > select > id,name,broadcast_uri,broadcast_domain_type,guru_name,state,gateway,cidr > from networks where id < 204; > +-----+------+---------------+-----------------------+---------------------+-------+-------------+----------------+ > | id | name | broadcast_uri | broadcast_domain_type | guru_name > | state | gateway | cidr | > +-----+------+---------------+-----------------------+---------------------+-------+-------------+----------------+ > | 200 | NULL | NULL | Vxlan | PublicNetworkGuru > | Setup | NULL | NULL | > | 201 | NULL | NULL | Vxlan | PodBasedNetworkGuru > | Setup | NULL | NULL | > | 202 | NULL | NULL | LinkLocal | ControlNetworkGuru > | Setup | 169.254.0.1 | 169.254.0.0/16 | > | 203 | NULL | NULL | Native | StorageNetworkGuru > | Setup | NULL | NULL | > +-----+------+---------------+-----------------------+---------------------+-------+-------------+----------------+ > > By doing this: > update networks set set broadcast_uri='vlan://untagged' where id<204; > the problem goes away. If i remember correctly the broadcast_uri for > PublicNetworkGuru, PodBasedNetworkGuru, ControlNetworkGuru and > StorageNetworkGuru is null by default.
