Did you ever find an answer? Have the same issue, stuck in podman compatibility purgatory with Centos 7 and octopus containers. Cephadm quincy wont even run on centos 7, says not supported. Closest thing I can find to a solution is to save the bare metal ceph configuration on the node, upgrade it to centos 8 stream, then restore the configuration. After all hosts done, then upgrade to quincy and then transition to cephadm. Unfortunately, I already converted one cluster to cephadm on octopus. -Brent -----Original Message----- From: Gary Molenkamp <molenkam@xxxxxx> Sent: Tuesday, May 24, 2022 11:03 AM To: ceph-users@xxxxxxx Subject: Upgrade paths beyond octopus on Centos7 Good morning, I'm looking into viable upgrade paths on my cephadm based octopus deployment running on Centos7. Given the podman support matrix for cephadm, how did others successful move to Pacific under a Rhel8 based OS? I am looking to use rocky moving forward, but the latest 8.6 uses podman 4.0 which does not seem to be supported for either Octopus (Podman < 2.2) or Pacific (Podman > 2.0-3.0). I was hoping to upgrade the host OS first before moving from Octopus to Pacific to limit the risks, so I'm trying to find a container solution the works for supporting the older Octopus and a future update to Pacific. Perhaps I should I switch back to docker based containers until the podman compatibility issues stabilize? Thanks Gary -- Gary Molenkamp Science Technology Services Systems/Cloud Administrator University of Western Ontario molenkam@xxxxxx http://sts.sci.uwo.ca (519) 661-2111 x86882 (519) 661-3566 _______________________________________________ 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
 |