On Fri, May 22, 2020 at 11:25 AM Jay Ring <1874...@bugs.launchpad.net> wrote:
> "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" > > Yes, I believe this would work. > > However, that's not normally how I would do an upgrade. Normally, I > upgrade one machine, make sure it works, and then upgrade the next. I > have done it this way since I built the cluster back in Firefly. When I > did this time, and it destroyed every OSD on the node that I upgraded. > Although not best practice (upgrading machine at a time, rather than mons, mgrs and osd ingroups) when I tried this earlier today it did actually work - hence why I think I'm missing something about impacted deployments. My testing did a fresh deploy of eoan with nautilus and then upgraded to focal; maybe deployments which have been about for a while have different state on disk/characteristic which cause this issue. I'm endeavouring to get to a point where we understand *why* this happens in certain situations. tl;dr I need more details about impacted deployments to be able to debug this further. -- 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
