search

canonical / charmed-openstack-upgrader

Automatic upgrade tool for Charmed Openstack
https://canonical-charmed-openstack-upgrader.readthedocs-hosted.com/en/stable/
Apache License 2.0
4 stars 12 forks source link

Upgrade ussuri -> victoria blocked if ceph is quincy #459

Open samuelallan72 opened 1 week ago

samuelallan72 commented 1 week ago

quincy is the highest recognised version by COU (COU does not support upgrading ceph from quincy -> reef).

However this causes a problem when there is an openstack deployment on ussuri, but ceph is on quincy. COU can plan an upgrade from ussuri to victoria, but then errors out because it cannot upgrade ceph:

2024-06-27 06:04:27 [cou.cli] [WARNING] Cannot generate plan for 'ceph-mon'
        The 'ceph-mon' application is using channel 'quincy/stable'. Channels supported during this transition: 'octopus/stable', 'octopus/stable'. Manual intervention is required.
Cannot generate plan for 'ceph-radosgw'
        The 'ceph-radosgw' application is using channel 'quincy/stable'. Channels supported during this transition: 'octopus/stable', 'octopus/stable'. Manual intervention is required.
Cannot generate plan for 'ceph-osd'
        The 'ceph-osd' application is using channel 'quincy/stable'. Channels supported during this transition: 'octopus/stable', 'octopus/stable'. Manual intervention is required.

In this case I guess COU should see that ceph is the highest supported version and skip it? Maybe openstack can be upgraded separately to ceph?

samuelallan72 commented 1 week ago

It seems that this isn't so much a bug as lacking explanation in the error message - see #461 .

I'm not sure if this is intended behaviour or not for COU though, so I'll leave the bug report open for now. It seems to me that if ceph is already upgraded, then COU should work on upgrading the rest of the cloud.

However it's also worth noting that in this case, the ceph workload was in fact octopus, even though quincy/stable charms were deployed.