@Chris, is this a landscape issue at this point?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
networking disruption on upgrade from 14.0.0 to 14.0.3
To manage notifications about th
Subscribing field medium to represent the issue this now causes with
landscape per-AZ upgrades
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
networking disruption on upgrade from 14.0
I have now run some tests and can confirm that upgrading the neutron
server package on the API units is enough. More specifically:
neutron-gateway 14.0.2 + neutron-api 14.0.2 + compute 14.0.4 ⇒ booting
instances fails
neutron-gateway 14.0.2 + neutron-api 14.0.4 + compute 14.0.4 ⇒ booting
instanc
Please also consider that this bug will easily hit cloud expansions: new
computes will get >= 2:14.0.3-0ubuntu1.1~cloud0, and if the neutron
gateway is running an older version they will not work until the neutron
packages are downgraded.
--
You received this bug notification because you are a me
For completeness, this affects even just 2:14.0.2-0ubuntu1.1~cloud0 to
2:14.0.3-0ubuntu1.1~cloud0.
Although we try as hard as we can to ensure that unattended upgrades are
disabled for the clouds we manage, upgrades between minor versions (not
just patch versions) should always be safe. This bug m
So how does that work when we use Landscape to auto-upgrades the
packages ?
** Changed in: cloud-archive
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
T
I opened a new bug for the charm guide at LP: #1859990
** No longer affects: charm-deployment-guide
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
networking disruption on upgrade fro
Comment #12, while I still think needs action, actually doesn't apply to
this bug since the package upgrades weren't done via charms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
net
Agree that a minor semver bump would be good in this scenario. Thanks
for updating the checklist @Slawek.
This page in the charm deployment guide needs better guidance on upgrade
order:
https://docs.openstack.org/project-deploy-guide/charm-deployment-
guide/latest/app-upgrade-openstack.html#known
** Also affects: charm-deployment-guide
Importance: Undecided
Status: New
** No longer affects: neutron (Ubuntu Disco)
** No longer affects: neutron (Ubuntu Eoan)
** No longer affects: neutron (Ubuntu Focal)
** Changed in: cloud-archive
Status: Confirmed => Incomplete
** Chang
@Jens: You are right with version numbers. I just added short note about it to
release-checklist doc in Neutron: https://review.opendev.org/702822
I hope it will help and we will remember about that in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I agree that this is kind of expected behaviour, but I also think that
it would be good if Neutron could adopt the policy to at least bump the
minor revision number on version number updates, that would make it more
obvious to deployers that special care is needed. It should also be
accompanied by
** Changed in: cloud-archive
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
networking disruption on upgrade from 14.0.0 to 14.0.3
To manage notificati
** Changed in: neutron
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
networking disruption on upgrade from 14.0.0 to 14.0.3
To manage notifications a
Hello:
As Felipe pointed out, the compatibility layer relies on the server
side. But making a stable upgrade should not trigger this problem of
course.
The mentioned patch [1] complies with the OVO versioning rules, allowing
version downgrade (in the server side).
Is there an order in the upgrad
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)
** Summary changed:
- neutron 2:14.0.3-0ubuntu1~cloud0 and 2:14.0.0-0ubuntu1.1~cloud0 not compatible
+ networking disruption on upgrade from 14.0.0 to 14.0.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
17 matches
Mail list logo
