OpenStack Magnum Charm

Bug #1990062
Comment #3

Comment 3 for bug 1990062

Revision history for this message

Alex Kavanagh (ajkavanagh) wrote on 2022-09-19: Re: [victoria/edge] openstack-upgrade action fails

Ok, firstly, thank you for testing the charms; it's something our automated tests haven't picked up, so that's really useful information, and something I'm going to look at to resolve.

It's confusing at the moment, because the migration from charmstore (jaas.ai) to charmhub (charmhub.io) is not quite complete (but is almost there). This means that not all the stable tracks in charmhub.io have been released. To recap:

* The charms in latest/stable are the 21.10 charms that support bionic-queens -> focal-xena
* The yoga/stable charms support focal-yoga, jammy-yoga, and an upgrade from focal-xena
* The xena/stable charms support focal-xena, and an upgrade from focal-wallaby.
* The wallaby/stable, victoria/stable and ussuri/stable track/risk combinations have not been released as they haven't quite finished their testing.

So if a charm doesn't have a stable risk against a track (e.g. victoria/stable) then it hasn't completed full testing.

So, if your OpenStack system is at focal-ussuri, (today) the best thing to do is to use the latest/stable charms to OpenStack upgrade to wallaby, and then:

* Switch to xena/stable and upgrade to xena.
* Switch to yoga/stable and upgrade to yoga.

The current latest/stable charms do support xena, and thus *should* get the system from ussuri to wallaby (via victoria) - but, please, if you do have a lab, do test this; it has been tested previously, but obviously, all systems are different and it's hard to say it will be flawless.

Also note, that the ceph charms (ceph-mon, -osd, -cephfs, etc), have a slightly different naming convention (quincy, pacific, nautilus, etc) and thus change from the 21.10 charms, and OVN also has differently named tracks. Please see https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html for more details.

If you ever want to just ask questions, etc, then please feel free to reach us as IRC: OFTC, channel #openstack-charms, or on the discourse.charmhub.io using the 'openstack' tag.

Ok, firstly, thank you for testing the charms; it's something our automated tests haven't picked up, so that's really useful information, and something I'm going to look at to resolve.

It's confusing at the moment, because the migration from charmstore (jaas.ai) to charmhub (charmhub.io) is not quite complete (but is almost there).  This means that not all the stable tracks in charmhub.io have been released.  To recap:

So if a charm doesn't have a stable risk against a track (e.g. victoria/stable) then it hasn't completed full testing.

So, if your OpenStack system is at focal-ussuri, (today) the best thing to do is to use the latest/stable charms to OpenStack upgrade to wallaby, and then:

* Switch to xena/stable and upgrade to xena.
* Switch to yoga/stable and upgrade to yoga.

Also note, that the ceph charms (ceph-mon, -osd, -cephfs, etc), have a slightly different naming convention (quincy, pacific, nautilus, etc) and thus change from the 21.10 charms, and OVN also has differently named tracks.  Please see https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html for more details.

If you ever want to just ask questions, etc, then please feel free to reach us as IRC: OFTC, channel #openstack-charms, or on the discourse.charmhub.io using the 'openstack' tag.