yahoo-eng-team team mailing list archive

[James Page <2030773@xxxxxxxxxxxxxxxxxx>]

Hello Lucas, or anyone else affected,

Accepted neutron into wallaby-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-wallaby-needed to verification-wallaby-done. If it
does not fix the bug for you, please add a comment stating that, and
change the tag to verification-wallaby-failed. In either case, details
of your testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/wallaby
       Status: Fix Released => Fix Committed

** Tags added: verification-wallaby-needed

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

Title:
  OVN DB Sync always logs warning messages about updating all router
  ports

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive antelope series:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Fix Released
Status in Ubuntu Cloud Archive victoria series:
  Fix Released
Status in Ubuntu Cloud Archive wallaby series:
  Fix Committed
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in Ubuntu Cloud Archive yoga series:
  Fix Released
Status in Ubuntu Cloud Archive zed series:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Focal:
  Fix Released
Status in neutron source package in Jammy:
  Fix Released
Status in neutron source package in Lunar:
  Fix Released

Bug description:
  Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156

  The ovn-db-sync script does not check if the router ports are actually
  out-of-sync before adding it to the list of ports that needs to be
  updated, this can create red herring problems by introducing an
  irrelevant piece of information [0] in the sync report (specially when
  ran in "log" mode) making the user think that the databases might be
  out-of-sync even when it is not.

  Looking at the code [1] we can see that the comment talks about
  checking the networks and ipv6_ra_configs changes but it does neither;
  instead, it adds every router port to the list of ports that needs to
  be updated.

  <snipet>

  # We dont have to check for the networks and
  # ipv6_ra_configs values. Lets add it to the
  # update_lrport_list. If they are in sync, then
  # update_router_port will be a no-op.
  update_lrport_list.append(db_router_ports[lrport])

  </snipet>

  This LP is about changing this behavior and checking for such
  differences in the router ports before marking them to be updated.

  [0]
  2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed

  [1]
  https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557

  ===== Ubuntu SRU Details =====

  [Impact]
  See bug description above.

  [Test Case]
  Deploy openstack with OVN and multiple routers. Run the ovn-db-sync script and ensure router ports that are not out of sync are not marked to be updated.

  [Where problems could occur]
  If the _is_router_port_changed() function had a bug there would be potential for ports to be filtered out that need updating. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upstream branches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2030773/+subscriptions