Trunk subports sometimes not becoming ACTIVE and trunk:subport

Bug #1837916 reported by Michal Dulko on 2019-07-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
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 'standardattributes' expected to update 1 row(s); 0 were matched.

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
Boden R (boden) wrote :

Any idea if this is also happening on master branch, or is this just a problem with Rocky?

Michal Dulko (michal-dulko-f) wrote :

Unfortunately no idea at the moment and I'm currently unable to check. Will update if I'll be able to test it with other versions.

Bence Romsics (bence-romsics) wrote :

This seems like a duplicate of https://bugs.launchpad.net/neutron/+bug/1828375.

Can you try this proposed fix? https://review.opendev.org/662236

As you can see in the commit message that's a fix with some concerns, so feedback from people who actually hit this problem would be really appreciated.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers