-
Epic
-
Resolution: Done-Errata
-
Major
-
None
-
None
-
Support ManilaShare deletion
-
18
-
False
-
-
False
-
Committed
-
No Docs Impact
-
To Do
-
manila-operator-container-1.0.4-4
-
Proposed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
-
Enhancement
-
Done
-
-
When a ManilaShare backend is removed from the ManilaShare list (or the Meta Operator template Spec), all the generated resources need to be automatically deleted.
- MariaDBEntry in the database (via Job or a similar task)
- Avoid to terminate all the existing shares as we should isolate the update only to the impacted backend
Workaround without this solution
Set replicas: 0 to the pod in question; the pod will be cleaned up; but, the manila db entries will still exist. So you can "oc rsh" into any of the manila pods and execute "manila-manage service cleanup"
- links to
-
RHSA-2024:140345 RHOSO OpenStack Podified operator containers security update