-
Bug
-
Resolution: Done
-
Normal
-
4.18.z, 4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 275, OSDOCS Sprint 276
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In the following section, it is explained how to perform destruction of cluster:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/installing_on_openstack/uninstalling-cluster-openstack
However, if customers are using CI/CD automation to redeploy clusters and disks are not wiped out, it can leave some data in the disks that needs to be wiped, it would be great to add like a small reminder that wiping disks should be considered. Here's an example, no need to be included but just a simple reminder that wiping should be recommended depending on each storage type: https://access.redhat.com/solutions/7128657
If it is no wiped, the installer can fail in unexpected way and could be stuck. It could be related to this RFE as a warning/reminder until it is implemented:
Allow coreos-installer to wipe the disk if something like `coreos.inst.wipe=yes` is added to pxe bootline.
https://issues.redhat.com/browse/RFE-7862
- links to