>From what I can see with the most recent cephadm binary on pacific, unless you have the CEPHADM_IMAGE env variable set, it does a `podman images --filter label=ceph=True --filter dangling=false` (or docker) and takes the first image in the list. It seems to be getting sorted by creation time by default. If you want to guarantee what you get, you can run `cephadm --image <image-name> shell` and it will try to use the image specified. You could also try that env variable (although I haven't tried that in a very long time if I'm honest, so hopefully it works correctly). If nothing else, just seeing the output of that podman command and removing images that appear before the 16.2.15 one on the list should work. On Tue, Apr 2, 2024 at 5:03 PM J-P Methot <jp.methot@xxxxxxxxxxxxxxxxx> wrote: > Hi, > > We are still running ceph Pacific with cephadm and we have run into a > peculiar issue. When we run the `cephadm shell` command on monitor1, the > container we get runs ceph 16.2.9. However, when we run the same command > on monitor2, the container runs 16.2.15, which is the current version of > the cluster. Why does it do that and is there a way to force it to > 16.2.15 on monitor1? > > Please note that both monitors have the same configuration. Cephadm has > been pulled from GitHub for both monitors instead of the package > manager's version. > > -- > Jean-Philippe Méthot > Senior Openstack system administrator > Administrateur système Openstack sénior > PlanetHoster inc. > _______________________________________________ > 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
 |