[ceph-users] openstack rgw swift -- reef vs quincy

2023-09-16 Thread Shashi Dahal
Hi All, We have 3 openstack clusters, each with their own ceph. The openstack versions are identical( using openstack-ansible) and all rgw-keystone related configs are also the same. The only difference is the ceph version .. one is pacific, quincy while the other (new) one is reef. The

[ceph-users] Re: Make ceph orch daemons reboot safe

2023-09-16 Thread Boris
The other hosts are still online and the cluster only lost 1/3 of its services. > Am 16.09.2023 um 12:53 schrieb Eugen Block : > > I don’t have time to look into all the details, but I’m wondering how you > seem to be able to start mgr services with the orchestrator if all mgr > daemons

[ceph-users] Re: Make ceph orch daemons reboot safe

2023-09-16 Thread Eugen Block
I don’t have time to look into all the details, but I’m wondering how you seem to be able to start mgr services with the orchestrator if all mgr daemons are down. The orchestrator is a mgr module, so that’s a bit weird, isn’t it? Zitat von Boris Behrens : Hi Eugen, the test-test cluster

[ceph-users] Re: Make ceph orch daemons reboot safe

2023-09-16 Thread Boris Behrens
Hi Eugen, the test-test cluster where we started with simple ceph and the adoption when straight forward are working fine. But this test cluster was all over the place. We had an old running update via orchestrator which was still in the pipeline, the adoption process was stopped a year ago and

[ceph-users] Re: Make ceph orch daemons reboot safe

2023-09-16 Thread Eugen Block
That sounds a bit strange to me, because all clusters we adopted so far successfully converted the previous systemd-units into systemd units targeting the pods. This process also should have been logged (stdout, probably in the cephadm.log as well), resulting in "enabled" systemd units.