Public bug reported: The OVN driver of the Trunk service plugin is in charge of updating the port binding profile of the subports. Unlike with normal ports, where Nova sends a port binding update, the subports are no longer physical ports in the local OVS bridge but flows added to filter the parent port.
Despite of that, the VIF details of the subports should mimic the values of the parent port and [1] should use the same VIF type as the parent port. [1]https://github.com/openstack/neutron/blob/725f3cbd8e9dfab18cccdcb2073f49473e634346/neutron/services/trunk/drivers/ovn/trunk_driver.py#L94-L99 ** Affects: neutron Importance: Medium Status: New ** Changed in: neutron Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2074185 Title: [OVN] Trunk subports should have the same VIF type as the parent port Status in neutron: New Bug description: The OVN driver of the Trunk service plugin is in charge of updating the port binding profile of the subports. Unlike with normal ports, where Nova sends a port binding update, the subports are no longer physical ports in the local OVS bridge but flows added to filter the parent port. Despite of that, the VIF details of the subports should mimic the values of the parent port and [1] should use the same VIF type as the parent port. [1]https://github.com/openstack/neutron/blob/725f3cbd8e9dfab18cccdcb2073f49473e634346/neutron/services/trunk/drivers/ovn/trunk_driver.py#L94-L99 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2074185/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp