-
Sub-task
-
Resolution: Unresolved
-
Undefined
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
I noticed leftovers from automation jobs, we have to document understand and handle cleanup better.
At the moment things I noticed on OCP:
- Namespaces starting with "auto-", some are stuck in terminating some are not.
- Failed/running migration plans - should be archived/deleted
- VMs, rare but popup
- Pods, should vanish if we archive/delete migration plans
- PVC some bound/some stuck in terminating state
Things I noticed on Vmware:
- VMs starting with "auto-" prefix
- On eco-iscsi-ds3 folders starting with "auto-" prefix, which contain only an RDM disk or a pointer to it, not full VM files.
Things I noticed on netapp:
- Well we have the issue of netapp's default 24 recycle bin, which we can't disable, but deleted PVCs remain on netapp for 24H before they are removed. I don't think we can do much about this as the 24H is a system wide configuration I can't drop avoid it. And our SVM well it typiclay has some 500+ volumes on it 1000 volumes is the limit, netapp/trident fail to create more volumes. Will hit us when we run lots of jobs. Check maybe we have to switch to trident's ontap-san-economy driver, a single netapp volumes holds a few PVCs, istead of ontap-san's netapp volume per each PVC.