• Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 2.12.0
    • None
    • QE-Task
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      I noticed leftovers from automation jobs, we have to document understand and handle cleanup better. 

      At the moment things I noticed on OCP:

      1. Namespaces starting with "auto-", some are stuck in terminating some are not.
      2. Failed/running migration plans - should be archived/deleted
      3. VMs, rare but popup
      4. Pods, should vanish if we archive/delete migration plans
      5. PVC  some bound/some stuck in terminating state

      Things I noticed on Vmware:

      1. VMs starting with "auto-" prefix
      2. 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:

      1. 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. 

              tshefi@redhat.com Tzach Shefi
              tshefi@redhat.com Tzach Shefi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: