-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.10.0
-
None
-
None
-
False
-
Description of problem:
openshift-install destroy unable to delete PVC disks in GCP if cluster identifier is longer than 22 characters Version: $ openshift-install version $ ./openshift-install 4.8.18 built from commit bd366e3cdcf892e1bddd841c702738f5254a0188 release image quay.io/openshift-release-dev/ocp-release@sha256:321aae3d3748c589bc2011062cee9fd14e106f258807dc2d84ced3f7461160ea Platform: GCP Installation Type: IPI What happened? #When run the openshift-install destroy cluster command, it is observed that PVC disks are not getting deleted, if the metadata.name is more than 22 characters. Always at least include the `.openshift_install.log` What did you expect to happen? All resources should get deleted successfully with openshift-installer destroy command. How to reproduce it (as minimally and precisely as possible)? $ Setup IPI GCP cluster $ Provide cluster name with 22 chars. $ Use standard (default) storage class, create pvc and pv. $ Once done, destroy the cluster $ Check on the backend platform if the storage disk for PVC is getting deleted or not. Anything else we need to know? We deployed an OpenShift 4 cluster in GCP, the `.metadata.name` field in the install config was gcpuser-a.ocp.redhat. The installer adds a unique identifier to the name for the InfraID, in our case, it resulted in `gcpusc1-a-ops-xpaas-nkp6w`. After the cluster was provisioned, we created a PVC. The corresponding Google cloud disk followed the name `gcpuser-a.ocp.redhat-nk-pvc-<UID>`. Because the disk name did not exactly match the InfraID, when we ran the openshift-install destroy for this cluster, none of the disks for PVCs were deleted.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: