csmbot
commented
1 year ago @EZandboer: Thank you for submitting this issue!
The issue is currently awaiting triage. Please make sure you have given us as much context as possible.
If the maintainers determine this is a relevant issue, they will remove the needs-triage label and assign an appropriate priority label.
We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.
EZandboer
bpjain2004
sharmilarama
Bug Description
After performing restores I can look at those restores using "dellctl restore get". As I want to demo this module I'd like to be able to delete the restores. Seems straight-forward by doing something like this:
dellctl restore delete -n applicatiion-mobility
This action DOES remove the restore from S3, and it removes the reference to the restore when using "dellctl restore get...".
However, 10-15 seconds after a successful deletion the reference returns when running "dellctl restore get...". I have been unable to truly delete the restores from the configuration.
Logs
root@k3s-001:~/yelb# dellctl restore get -n application-mobility NAME BACKUP STATUS CREATED COMPLETED restore-from-k3s-to-openshift-yelb-k3s-01 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-01-001 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-02 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-03 yelb-k3s-01 Completed 2023-02-23 09:06:53 -0500 EST NA root@k3s-001:~/yelb# dellctl restore delete restore-from-k3s-to-openshift-yelb-k3s-01-001 -n application-mobility Are you sure you want to continue (Y/N)? y INFO Request to delete restore "restore-from-k3s-to-openshift-yelb-k3s-01-001" submitted successfully. INFO The restore will be fully deleted after all associated data (restore files, velero restore) are removed. root@k3s-001:~/yelb# dellctl restore get -n application-mobility NAME BACKUP STATUS CREATED COMPLETED restore-from-k3s-to-openshift-yelb-k3s-01 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-02 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-03 yelb-k3s-01 Completed 2023-02-23 09:06:53 -0500 EST NA root@k3s-001:~/yelb# dellctl restore get -n application-mobility NAME BACKUP STATUS CREATED COMPLETED restore-from-k3s-to-openshift-yelb-k3s-01 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-01-001 yelb-k3s-01 Completed 2023-02-28 04:44:53 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-02 yelb-k3s-01 Completed 2023-02-21 06:15:58 -0500 EST NA restore-from-k3s-to-openshift-yelb-k3s-03 yelb-k3s-01 Completed 2023-02-23 09:06:53 -0500 EST NA root@k3s-001:~/yelb#Screenshots
No response
Additional Environment Information
Have been using K3 with UnityVSA and OpenShift 4.11 with PowerStore. Both environments show the exact same behavior.
Steps to Reproduce
first create a restore Second delete the restore (dellctl restore delete -n
Get the restores (dellctl restore get -n ) --> verify the restore is now gone
<wait for 15 seconds>
Get the restores again (dellctl restore get -n ) --> Take note that the restore has returned.
Expected Behavior
A deleted restore should be deleted permanently, not return after 15-20 seconds.
CSM Driver(s)
CSI driver for Unity 2.5 CSI driver for PowerStore 2.5
Installation Type
Both via Helm3: version.BuildInfo{Version:"v3.10.3", GitCommit:"835b7334cfe2e5e27870ab3ed4135f136eecc704", GitTreeState:"clean", GoVersion:"go1.18.9"}
Container Storage Modules Enabled
CSM application-mobility: dellemc/csm-application-mobility-controller:v0.2.0
Container Orchestrator
both Kubernetes v1.25.4+k3s1 and OpenShift v1.24.0+3882f8f
Operating System
For K3s: Debian GNU/Linux 10 (buster)