Hi Peter, I'm not a rook expert, but are you asking how to remove the rook action to delete a pool? Or is the pool already deleted from ceph itself? We "bare" ceph operators have multiple locks to avoid fat fingers like: ceph osd pool set cephfs_data nodelete 1 ceph config set mon mon_allow_pool_delete false # the default -- Dan On Fri, Sep 25, 2020 at 4:49 AM Peter Sarossy <peter.sarossy@xxxxxxxxx> wrote: > > Hit send too early... > > So I did find in the code that it's looking for the deletion timestamp, but > deleting this field in the CRD does not stop the deletion request either. > The deletionTimestamp reappears after committing the change. > https://github.com/rook/rook/blob/23108cc94afdebc8f4ab144130a270b1e4ffd94e/pkg/operator/ceph/pool/controller.go#L193 > > On Thu, Sep 24, 2020 at 10:40 PM Peter Sarossy <peter.sarossy@xxxxxxxxx> > wrote: > > > hey folks, > > > > I have managed to fat finger a config apply command and accidentally > > deleted the CRD for one of my pools. The operator went ahead and tried to > > purge it, but fortunately since it's used by CephFS it was unable to. > > > > Redeploying the exact same CRD does not make the operator stop trying to > > delete it though. > > > > Any hints on how to make the operator forget about the deletion request > > and leave it be? > > > > -- > > Cheers, > > Peter Sarossy > > Technical Program Manager > > Data Center Data Security - Google LLC. > > > > > -- > Cheers, > Peter Sarossy > Technical Program Manager > Data Center Data Security - Google LLC. > _______________________________________________ > 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
 |