Created attachment 1593383 [details]
Description of problem:
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 'standardattributes' expected to update 1 row(s); 0 were matched.
Version-Release number of selected component (if applicable):
Steps to Reproduce (I'm putting what Kuryr does):
1. Create 3 ports in bulk.
2. Tag them.
3. Add them to a trunk.
Sometimes port stays DOWN and still has what Kuryr put as device_owner instead of trunk:subport.
Port becomes ACTIVE and has trunk:subport as device_owner.
In the logs look for port 008a09d7-97a4-4aee-880c-c3dc5ad3d4f6, that's the affected one.
Created attachment 1593384 [details]
Slawek - I built neutron to pick up fix for https://bugzilla.redhat.com/show_bug.cgi?id=1717558 and in turn included fix here. The package is openstack-neutron-13.0.4-0.20190508213452.de95bc6.el7ost.
Thx Bob for building package and for info about it :)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.