There have been bugs in the past where things have gotten "stuck". Usually I'd say check the REFRESHED column in the output of `ceph orch ps`. It should refresh the daemons on each host roughly every 10 minutes, so if you see some value much larger than that, things are probably actually stuck. If they are, the first thing to try is usually a mgr failover (`ceph mgr fail`). Are you using a special RGW image different from the other ceph daemons in the cluster? The typical case is that all the ceph daemons use the same image and then get updated using the `ceph orch upgrade start ...` command. On Fri, Mar 1, 2024 at 4:26 AM wodel youchi <wodel.youchi@xxxxxxxxx> wrote: > Hi, > > I have finished the conversion from ceph-ansible to cephadm yesterday. > Everything seemed to be working until this morning, I wanted to redeploy > rgw service to specify the network to be used. > > So I deleted the rgw services with ceph orch rm, then I prepared a yml file > with the new conf. I applied the file and the new rgw service was started > but it was launched with an external image, so I wanted to redeploy using > my local image so I did a redeploy ... and then nothing happened, I get the > rescheduled message but nothing happened, then I restarted one of the > controllers, the orchestrator doesn't seem to be aware that some service > have restarted??? > > PS : I don't fully master the cephadm command line and use. > > Regards. > _______________________________________________ > 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
 |