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

[vault] newer version stopping cou plan/upgrade #472

Open honghan-wong opened 2 days ago

honghan-wong commented 2 days ago

When we are running cou on some clouds on ussuri, the vault charm is running on a later version 1.10.6.

The current cou is allow only vault version 1.7 on ussuri version.

Is it possible to have cou support some charms where a later version will not cause incompatible between openstack components?

Example is vault 1.10.6 doesn't introduce breaking change and should be able to support the upgrade between ussuri and yoga. If the vault is on a later version, cou might be able to skip the upgrade for vault.

jneo8 commented 2 days ago

A very quick option is to update cpu/utils/openstack_lookup.csv from your expectation. The {series}-upper_version should be the latest one if there are no breaking change.

A more general option is that we we provide --skip-apps argument for the user to skip the upgrade steps for some application. This may cause some issue if the some applications is no been upgraded but it's user's choose.

gabrielcocenza commented 2 days ago

One thing that it's not clear to me is why the vault is using 1.10. By the charm page seems that we don't have this option on channels. @honghan-wong what is the channel that the charm is using?

honghan-wong commented 14 hours ago

vault charm is using rev 54, channel latest/stable

vault                     1.10.6   active      3  vault                     latest/stable   54  no       Unit is ready (active: true, mlock: enabled)

We have met issue before on vault charm where the snap has refreshed the vault to a later version and triggered an alert from nrpe check mentioning version mismatch. To solve it, we have to restart the vault service and the charm will refreshed to the later version. And I believe this is one of the case, where the charm is on an older revision but vault has upgrade to a later version.

aieri commented 12 hours ago

@honghan-wong you're also using the latest/stable track, which is closed. The charm should be switched to track 1.7/stable. I don't know if you can downgrade the vault snap without breakages though.