Trunk subports sometimes not becoming ACTIVE and trunk:subport
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Undecided
|
Unassigned |
Bug Description
We're occasionally hitting a bug preventing Kuryr-Kubernetes from attaching ports to a trunk. The result of the operation on the API is 200, but ports never gets into ACTIVE and switches device_owner to trunk:subport. In our case Kuryr is creating those ports in bulks of 3, then tagging them one-by-one, then attaching to a trunk using random segmentation ID's.
Removing the subport from trunk and attaching it again resolves the issue.
In the logs of openvswitch-agent we see:
Remote error: StaleDataError UPDATE statement on table 'standardattrib
Version-Release number of selected component (if applicable):
Rocky
How reproducible:
Occasionally. :(
Steps to Reproduce (I'm putting what Kuryr does):
1. Create 3 ports in bulk.
2. Tag them.
3. Add them to a trunk.
Actual results:
Sometimes port stays DOWN and still has what Kuryr put as device_owner instead of trunk:subport.
Expected results:
Port becomes ACTIVE and has trunk:subport as device_owner.
tags: | added: trunk |
Any idea if this is also happening on master branch, or is this just a problem with Rocky?