Comment 1 for bug 1974183
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hello:
This problem is happening in the OVN driver, in the Trunk service OVN driver (both networking-ovn [1] for Train deployments or Neutron [2] for newer).
When a trunk is created, regardless of the port binding (that means, even if the parent port is not bound to ML2/OVN), the Trunk OVS driver updates the status to ACTIVE. This is obviously something wrong that must be fixed but doesn't affect to any other service (**if** this service is not reading the trunk status).
Another topic, that is related to this bug is what is happening when a parent port is linked to a trunk and this parent port is then bound to a driver (SR-IOV in this specific case NOTE1) that doesn't have Trunk driver. In this case, the Trunk won't be created and the status of the Trunk must not be updated.
Regards.
NOTE1: the parent port is vnic-type direct and it is bound to a SR-IOV network. This is not defined in the bug description but I have access to the reporter environment.
[1]https:/
[2]https:/