Hmm I wonder whether this is due to the co-location of ceph-osd with
nova-compute; which order did you perform the upgrade in? switching
openstack-origin on the nova-compute node will trigger a package upgrade
for all packages on the machine, including ceph.
ceph-osd can be more selective, so the upgrade process will only upgrade
ceph packages during the rolling upgrade process.
So normal order would have to be ceph-osd first, and then nova-compute.
Also, looking at the code, the ceph-mon and ceph-osd charms will not
support charm driven upgrades from proposed pockets - the map of
supported paths is as follows:
# A dict of valid ceph upgrade paths. Mapping is old -> new
upgrade_paths = {
'cloud:trusty-juno': 'cloud:trusty-kilo',
'cloud:trusty-kilo': 'cloud:trusty-liberty',
'cloud:trusty-liberty': 'cloud:trusty-mitaka',
}
So setting anything other than values in that map will not trigger any upgrade
code in the charm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
Upgrading ceph-osd from Kilo to Mitaka "misses" /var/lib/ceph
ownership change
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1611082/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
