yahoo-eng-team team mailing list archive

[Michal Dulko <mdulko@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1837916

Title:
  Trunk subports sometimes not becoming ACTIVE and trunk:subport

Status in neutron:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1837916/+subscriptions