Ubuntu
neutron package

  1. Focal (20.04)
  2. Bug #1927868
  3. Comment #31

Comment 31 for bug 1927868

Revision history for this message
Corey Bryant (corey.bryant) wrote (last edit ):

I haven't been able to recreate this when upgrading packages in the correct order and running db migrations as mentioned in https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/comments/23.

Today I attempted to recreate this a few times, and my HA routers look correct after upgrade.

Alexandros, if you have any more details on steps to take to recreate this please let me know. I understand your deployment is juju managed, and that's what I use for testing, so it may be simple to recreate if I get the right steps.

My general testing steps were: deploy train, create an HA router, upgrade neutron-api to ussuri 16.3.0, upgrade neutron-gateways to 16.3.0, upgrade neutron-api to 16.3.2, and finally upgrade neutron-gateway units to 16.3.2. All the while of course restarting services along the way, and running ip addr list in both router namespaces to ensure one qg-* is UP with an IP and the other is DOWN as well as monitoring L3 agents hosting the router are active/standby.