Hello Mahudeeswaran:

This topic is being discussed in [1]. The patch [2] you are referring to is not changing the previous code related to the mentioned parameter "bridge name". Please check [3].

Also consider that this value was populated when using Trunk ports, to store the Trunk bridge name created on the port description. In ML2/OVN, all ports are attached to the integration bridge (there is a configuration parameter to define the integration name bridge called "integration_bridge", that by default is "br-int").

Regards.

[1]https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/X4GT7LA523FZWJCGEF2IKTG7VF5WSZWK/

[2]https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e49f099f96c363683#diff-3fb0e47430c01037fddef45c2ce7314f50a3df5ac41dbd604f9581d90f2985bb

[3]https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e49f099f96c363683#diff-3fb0e47430c01037fddef45c2ce7314f50a3df5ac41dbd604f9581d90f2985bbR33

On Mon, Dec 4, 2023 at 3:50 PM Mahudeeswaran Palanisamy <mahudees@gmail.com> wrote:

Hi All,

Looks like as part of the below commit, bridge_name info has been
removed from port binding vif_details dictionary. Is there any way
that we can get the bridge_name info of a port?

As far as checked we can get this info by checking if port UUID is
part of the “ports” array in “sudo ovs-vsctl list br” output. But
there is no equivalent way to get from Java SDK.

https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e49f099f96c363683#diff-3fb0e47430c01037fddef45c2ce7314f50a3df5ac41dbd604f9581d90f2985bb

Thanks,
Mahudees