"As a side note - even if there is a bug here (and it sounds like there might be) I would recommend placing the mon and mgr daemons in LXD containers ontop of the machines hosting the osd's"
Yes. I would strongly suggest doing this also. That is how Ceph now recommends it anyway. However, older installs are not usually set up this way. And there is no warning that if you aren't set up this way that do- release-upgrade will destroy the node. I would have been happy to make the change, I just didn't know it was necessary. Also, and not to complain, but if you are setting up this way, there is no reason for the monitor package to be installed outside of the container - and it should probably not be. This would suggest to me that ceph-mon should "conflict" with ceph-osd since they should never be installed in the same context/container/host. This would force a user to remove either the monitor or OSDs , preventing a reboot from destroying the node. In a perfect world, ceph-osd would notice that it is connecting to an old monitor and politely disconnect without destroying all it's OSDs. For now, however, I suggest some sort of stop-gap measure that prevents users from nuking their cluster without warning. -- 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
