Source does not trigger an upgrade
Bug #1879072 reported by
Chris Sanders
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Ceph-FS Charm |
Fix Released
|
High
|
Unassigned |
Bug Description
With a deployed bionic-stein bundle, I upgraded the cluster to bionic-train and the ceph-fs charm doesn't appear to trigger any upgrade at all. Mon/Osd upgraded as expected.
The code path in the charm seems to indicate there is no upgrade support at all, or it's in a layer and I just didn't find it. However https:/
Reproduce with:
https:/
After the deploy run through the upgrade steps from the above guide to get the cluster on 14.x series. Ceph-fs will still be on 13.x
Changed in charm-ceph-fs: | |
status: | Triaged → In Progress |
Changed in charm-ceph-fs: | |
milestone: | none → 20.08 |
Changed in charm-ceph-fs: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Chris, it does seem that the charm doesn't handle the 'source' config param apart from during the installation. i.e. not on config-changed (afaict). It looks like the charm will need an update.
Notes:
The charm also doesn't use charms.openstack and instead uses layer-apt. We should give serious consideration to switching it over to charms.openstack so we can access all of the default behavour of upgrades, managed upgrades, pause/resume, SSL, space support, etc.