-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.15
-
No
-
1
-
uShift Sprint 246, uShift Sprint 247
-
2
-
False
-
-
The microshift-cleanup-data script now stops and deletes all the pods, both MicroShift core and user services.
-
Release Note Not Required
-
In Progress
Description of problem:
microshift-cleanup-data does not remove all Pods - only MicroShift's ones which might lead to dangling K8s containers without K8s. If MicroShift is being cleaned up (i.e. etcd database removed), then these Pods should also be removed.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Only microshift Pods are removed
Expected results:
All pods are removed
Additional info:
- clones
-
OCPBUGS-24689 MicroShift's cleanup script should stop and delete all (including user's) Pods
- Closed
- depends on
-
OCPBUGS-24689 MicroShift's cleanup script should stop and delete all (including user's) Pods
- Closed
- links to
-
RHEA-2023:7200 Red Hat build of MicroShift 4.15 bug fix and enhancement update