Created attachment 1896361 [details] Log generated after running destroy cluster command Version: $ ./openshift-install 4.11.0-rc.1 built from commit b2e7be726e400022e71ef3b8bd01a2093e53bc5a release image quay.io/openshift-release-dev/ocp-release@sha256:09da7755ee797f142befb50795beda9a496b8a1b5e137224567b650b4daa8583 release architecture amd64 Platform: Google Cloud IPI We run interop test for Openshift and Ansible Tower projects. We are able to install Openshift cluster with the installer into the GCP environment, but after completing the test we cannot destroy the cluster in most cases. The destroy command failed with the Runtime error: slice bounds out of range [:22] with length 21. (see destroy.log attached) What did you expect to happen? Installer should be able to destroy the cluster. How to reproduce it (as minimally and precisely as possible)? # Create install-config.yaml file ``` --- fips: false metadata: name: "lp-7298" compute: - architecture: amd64 hyperthreading: Enabled name: worker platform: {} replicas: 2 ``` # Configure GCP authentication so the installer can communicate to the google cloud. # Run installer to install cluster into the GCP $ openshift-install create cluster --dir=. # After deployment is completer try to destroy the cluster $ openshift-install destroy cluster --dir=.
A patch fixing the issue has just been merged into the 4.11 branch. You should be able to destroy the cluster with an `openshift-installer` binary built from master. If that's not the case, please re-open. *** This bug has been marked as a duplicate of bug 2104906 ***