Hi Tyler, Maybe you didn't read the full message, but in the message you will notice that I'm doing exactly that, and the problem just occurred when I was doing the upgrade from Octopus to Pacific. I'm nowhere near Quincy yet. The original goal was to move from Nautilus to Quincy, but I have gone to Octopus (no problems) and now to Pacific (problems).
On Thu, Oct 26, 2023 at 3:36 PM Tyler Stachecki <stachecki.ty...@gmail.com> wrote: > > On Thu, Oct 26, 2023, 6:16 PM Jorge Garcia <jgar...@soe.ucsc.edu> wrote: > > > > from Centos 7 and Nautilus to > > Rocky 9 and Quincy. > > I hate to be the bearer of bad news here, but: > > https://docs.ceph.com/en/latest/releases/quincy/#upgrading-from-pre-octopus-releases-like-nautilus > > "You *must* first upgrade to Octopus (15.2.z) or Pacific (16.2.z) before > upgrading to Quincy." > > > Is this expected? What am I missing? Thanks for any pointers! > > Personally, what I would do in this situation is treat the 2 Quincy mons > as permanently failed, and recover from the Nautilus one that's still > working. That is: take a copy of the monmap, then purge the two Quincy mons > that were prematurely upgraded, and finally rebuild those same 2 mons with > Centos 7/Nautilus. > > Preferably, this is done in some kind of staging environment first for > validation as you do not want to mess with that last mon at this point. > > Cheers, > Tyler > _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
