Open gabrielcocenza opened 5 months ago
After rebooting a ceph-osd machine (not necessary) and restarting the services using sudo systemctl restart ceph.target
, ceph-osd versions got updated like in the payload:
{
"mon": {
"ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 2,
"ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 1
},
"mgr": {
"ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 2,
"ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 1
},
"osd": {
"ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 18
},
"mds": {},
"rgw": {
"ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 2,
"ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 1
},
"overall": {
"ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 2,
"ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 5,
"ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 20
}
}
rgw
had the same issue as osd
Hi, also was affected by this one during Octopus -> Pacific upgrade of ceph-osd
during the last step of Victoria -> Wallaby upgrade. Reported ceph-osd charm LP2068151 bug also, as it is not clear why charm hasn't done any restarts.
For some unknown reason, after upgrading all ceph-osds to
pacific
on partner cloud, ceph-mon still says that osd's are onoctopus
.E.g:
This is problematic because it pass the
set_require_osd_release_option
once that therequire-osd-release
is also onoctopus
and this will let the cloud continue upgrading. I guess the right thing is to halt the execution if we see that there is more than one ceph version in the cloud.