yahoo-eng-team team mailing list archive

[Corey Bryant <corey.bryant@xxxxxxxxxxxxx>]

If we're sure the patch in comment #5 is causing the issue (which seems
likely based on the log) we could revert it in distro and fast-path that
SRU. This likely also affects stable/train as well.

** Changed in: neutron (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: neutron (Ubuntu)
   Importance: Undecided => Critical

** Also affects: neutron (Ubuntu Disco)
   Importance: Undecided
       Status: New

** Also affects: neutron (Ubuntu Focal)
   Importance: Critical
       Status: Triaged

** Also affects: neutron (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Changed in: neutron (Ubuntu Focal)
       Status: Triaged => Confirmed

** Changed in: neutron (Ubuntu Focal)
   Importance: Critical => Undecided

** Also affects: cloud-archive
   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/1859649

Title:
  networking disruption on upgrade from 14.0.0 to 14.0.3

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  New
Status in neutron package in Ubuntu:
  Confirmed
Status in neutron source package in Disco:
  New
Status in neutron source package in Eoan:
  New
Status in neutron source package in Focal:
  Confirmed

Bug description:
  Hi,

  Not entirely sure why, but if a cloud has services running these 2
  versions of neutron (2:14.0.3-0ubuntu1~cloud0 and
  2:14.0.0-0ubuntu1.1~cloud0), networking is basically broken until
  everything is running 2:14.0.3-0ubuntu1~cloud0.

  Which causes networking disruption when not all nodes are upgraded at
  the same time.

  Thanks

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