-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[nova-compute / ovn-chassis] upgrade nova-compute failed during zed -> 2023.1 #494
Comments
This appears related to LP: #2068109 - same broken packages for apt, same workaround, and similarly the broken packages relate to a colocated charm. |
The workaround solution may break the configuration of nova-compute. We need to find some other solution. |
Problem DescriptionInitially, I deployed an OpenStack Zed cloud with Upgrade Process
ConclusionThis presents a chicken-and-egg problem: the The workaround can be running |
So far I'm with you.
Why exactly does What prevents you from upgrading |
Hi @fnordahl , thanks for you response first.
So these are the reasons we have this order:
The main reason cause this issue is because no matter the order of upgrading on the hypervisor node, it will have issue:
|
It is possible to upgrade the charm without upgrading its payload. Would that not solve the |
@fnordahl could you explain what this looks like practically - ie. if you were to do this manually? I'm curious because I'm not aware of any charm mechanism that synchronises updates between charms. |
I'm almost sure it won't be possible to resolve the issue because the (Or I misunderstand what you try to do here) |
As laid out in the documentation, it is expected to first upgrade charms and then upgrade the payload. There is nothing manual or special about this. So if you upgrade the charms first and then proceed with the payload upgrade, is this an issue? |
There is also an issue on work-around:
This error message from resume action:
|
Hi @fnordahl You mean for example we upgrade the all the charms without change any |
Yes. |
On this topic there is precedence in the charms to have subordinates make their principal aware of their packages: Not sure if it is required here though, it might be that just doing charm upgrade before payload upgrade will make the |
This is a packaging upgrade bug:
openvswitch-switch needs a versioned Breaks/Replaces in the antelope UCA to deal with this file moving, if that was the intent. |
Due to the packaging history (merging with Debian) I think the openvswitch-switch binary package needs:
as that's when the local-config.ovsschema file was added to the -switch package. @fnordahl are you OK to pickup a fix for this? |
Reproducer in a focal LXD container
|
For "charms upgrade" though, it's not always clear what this refers to, as there are a couple of options:
Also how does this work for subordinate charms; it's not possible to split upgrading the charm and the payload like the principal charms, because they don't have a separate |
@javacruft sure! Do you think this is a requirement all the way from tip of the packages, or is this a stable only package fix? |
Regardless of which of these methods are used, the base reality is that the charm code needs to be upgraded prior to the payload for it to understand the new payload.
Indeed, subordinate charms typically do not deal with package upgrades for this reason. The chassis charm has a Some subordinate charms with package upgrade requirements exchange this information with their principal as mentioned in #494 (comment), but again I don't think explicit exchange is required for this relationship. For |
Issue on launchpad: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2077406 |
@fnordahl thanks for your explanation 🙂 |
@jneo8 can you confirm if this bug is fixed? I see you confirmed that https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2077406 is resolved, but I'm not sure if that alone fixes this; there are many comments on this issue. |
Thanks for follow up Samuel. The fixed version Check on: https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/antelope_versions.html |
When COU refresh nova-compute from `zed/stable' to '2023.1/stable' during Jammy/Zed -> Jammy/2023.1 upgrade, the following substeps of 'Upgrade plan for units: nova-compute/0' failed
Environment: deployed with stsstack-bundle using
./generate-bundle.sh --name cou -r yoga -s jammy --ceph --run
Failed: Upgrade the unit: 'nova-compute/0' substep failed
Note
sudo apt --fix-broken install
on nova-compute/0 unit will fix this issueThe text was updated successfully, but these errors were encountered: