That may be the very one I was thinking of, though the OP seemed to be preserving the IP addresses, so I suspect containerization is in play. > On Sep 9, 2023, at 11:36 AM, Tyler Stachecki <stachecki.tyler@xxxxxxxxx> wrote: > > On Sat, Sep 9, 2023 at 10:48 AM Anthony D'Atri <anthony.datri@xxxxxxxxx> wrote: >> There was also at point an issue where clients wouldn’t get a runtime update of new mons. > > There's also 8+ year old unresolved bugs like this in OpenStack Cinder > that will bite you if the relocated mons have new IP addresses: > https://bugs.launchpad.net/nova/+bug/1452641 > > Tripling down on what others have said: would advise against > redeploying mons unless you need to... > > FYI: you can relocate the OSDs without having Ceph spew bits about by > setting noout, stopping the OSDs to be moved, physically moving the > underlying drive(s) to another host, running `ceph-volume lvm activate > --all` on the new host, and unsetting noout. > > Regards, > Tyler > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |