OK further fact discovery from my testing. I have a 6 machine cluster deployed - three machines host mon,mgr and three machines host osd.
Upgrading the mon,mgr cluster first followed by the three osd machine using do-release-upgrade and allowing the tool to reboot the machine at the end resulted in an upgraded and functioning cluster. I also validated that the process of upgrading the packages does not stop or restart the daemons - so they will run on the 14.2.x series from eoan until either they are restarted OR the do-release-upgrade tool is permitted to reboot the box. I appreciate that the reporters of this bug are deploying all daemons on all three machines which is different to what I have tested - I'll look at that next. However it should be possible to complete the do-release-upgrade to the point of requesting a reboot - don't - drop to the CLI and get all machines to this point and then: restart the mons across all three machines restart the mgrs across all three machines restart the osds across all three machines validating health between each step. I'm going to test this now. This is inline with the upstream documented process for upgrading a ceph cluster: https://docs.ceph.com/docs/master/releases/octopus/#upgrading-from- mimic-or-nautilus After this has been completed a reboot of each machine will be required to complete the release upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874939 Title: ceph-osd can't connect after upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1874939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
