OVN trunk subport missing binding information

[Arnau Verdaguer]

After creating a trunk VM and attaching a trunk port and a subport, the trunk subport's info on the neutron db conatins the host_id and vif_details, but the subport doesn't.

(overcloud) [stack@undercloud-0 neutron-miscellaneous]$ openstack port show 0c5aa89a-a8d0-491f-92bc-1e2459ee7863 -f value -c binding_host_id -c binding_vif_details -c name
compute-1.redhat.local
{'port_filter': True, 'connectivity': 'l2'}
trunkport
(overcloud) [stack@undercloud-0 neutron-miscellaneous]$ openstack port show da4dc641-91fd-46f6-be8f-e907cab946e1 -f value -c binding_host_id -c binding_vif_details -c name

{}
trunksub

[Jakub Libosvar (libosvar)]

I don't see why is this wrong? I think this is intentional since the subport itself isn't claimed by ovn-controller, just the parent port.

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Patch: https://review.opendev.org/q/I34bb6f178c314907bdf9f76789777f6736938b67

Merged up to Wallaby.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 22.0.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 21.1.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 20.4.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 23.0.0.0b3 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron xena-eom release.