Bug 2228555
| Summary: | blockpool stuck on deleting when referred to storage class | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Daniel Osypenko <dosypenk> |
| Component: | rook | Assignee: | Travis Nielsen <tnielsen> |
| Status: | NEW --- | QA Contact: | Neha Berry <nberry> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.13 | CC: | badhikar, bniver, ebenahar, muagarwa, odf-bz-bot, sostapov, tnielsen |
| Target Milestone: | --- | Flags: | dosypenk:
needinfo?
(badhikar) |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Daniel Osypenko
2023-08-02 16:07:55 UTC
current behavior also producing inconsistency between UI and cli interfaces
After this rejected deletion User can enter the pool page and see it's Status, metrics, etc similarly to any other pool but clicking on Actions dropdown btn user will see that Resource is being deleted.
Edit label, Edit annotations, Edit block pool actions from now are disabled.
From the cli user may continue patch cephblockpool:
oc patch cephblockpool cbp-test-04e89e5772d64e5c97ac468df6f7a3a -n openshift-storage --type=merge -p '{"metadata":{"labels":{"new-label":"label-value"}}}'
cephblockpool.ceph.rook.io/cbp-test-04e89e5772d64e5c97ac468df6f7a3a patched
What should be an actions of the user that accidentally tried to remove the pool and want to continue work with it, edit it via UI?
> current behavior also producing inconsistency between UI and cli interfaces The inconsistency is that the cli user can update the pool, but the UI cannot? It seems valid that the UI cannot update the deleted resource, but is a reasonable advanced scenario for a cli user to update the resource. > What should be an actions of the user that accidentally tried to remove the pool and want to continue work with it, edit it via UI? K8s doesn't allow undeleting a resource, so the only way to bring the resource back to a non-deleted state is to delete it and create it again with the same spec. There are instructions upstream for this: https://rook.io/docs/rook/latest/Troubleshooting/disaster-recovery/#restoring-crds-after-deletion That if we have customer issues with it downstream, we should get something similar in the downstream docs. Shall we close this? Sounds like expected behavior from ODF perspective. Were you able to recover? Hello Travis. Can not find documentation for OCP similar to https://rook.io/docs/rook/latest/Troubleshooting/disaster-recovery/#restoring-crds-after-deletion I also tried to restore blockpool by steps provided in this instruction and fail on step 6. `oc create -f cluster.yaml` I am not sure if it is applicable for OCP cluster. Do you think we can add such instruction to our documents? Restoring a deleted CR is really a risky operation, so at best it should be a KCS article and the support team should be involved in the restoration. You said the CephBlockPool was deleted, right? Then I wouldn't expect the cluster.yaml to be created again. The restore needs to only be for the specific CephBlockPool. That upstream document is intended to be an example that needs to be adjusted depending on which CR is being restored. |