Hello Ceph Community, We are looking for guidance regarding our existing Ceph cluster. Our cluster was deployed using ceph-ansible and is currently running the Squid development release (v19.3.0). We are planning to adopt the cluster into cephadm using the cephadm-adopt playbook provided by ceph-ansible. Before proceeding, we would like to understand the recommended approach for changing our Ceph version from the Squid development release (v19.3.0) to the stable Squid release (v19.2.3). Cluster Details Deployment: ceph-ansible Current Version: Squid Development (v19.3.0) Health: HEALTH_OK Hosts: 4 MONs: 3 MGRs: 1 Active, 2 Standby OSDs: 15 (15 Up / 15 In) RGW: 1 daemon Pools: 15 Objects: ~1.64 million Usage: 17 TiB used, 9.2 TiB / 26 TiB avail We have the following questions: Is it possible to change from the Squid development version (v19.3.0) to the stable Squid release (v19.2.3)? Is this a supported approach, or is there a recommended alternative? Should we change to the stable release before adopting the cluster into cephadm, or is it better to perform the cephadm adoption first and then update the version? Are there any known limitations, prerequisites, or best practices we should be aware of before proceeding? Any guidance, recommendations, or references to relevant documentation would be greatly appreciated. Thanks & Regards, Kathirvel T Associate R&D Engineer mailto:manoj.kumar@zybisys.com kathirvel.t@zybisys.com https://www.zybisys.com https://in.linkedin.com/company/zybisys https://www.facebook.com/Zybisys/ https://www.instagram.com/ZyBiSys/ https://www.youtube.com/@zybisys https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."