Image registry had similar problems on AWS and it was resolved by tagging the S3 resources such that the Installer cleans them up, a similar solution is needed for GCP.
Moving to the installer for now - if installer needs the image registry operator to name/tag the bucket in a specific way this can be reassigned.
This could be CI specific timeout.
This should be resolved by https://github.com/openshift/installer/pull/2589, CI time-outs aside.
Verify this bug with payload registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-11-17-224250. ./openshift-install destroy cluster --dir=/home/jenkins/workspace/Remove VMs/cucushift/workdir/install-dir --log-level=debug level=debug msg="OpenShift Installer v4.3.0" level=debug msg="Built from commit 55ac3aca9578c038278d7ab24037849e3b9f8296" ... level=debug msg="Listing storage buckets" level=debug msg="Found bucket: gpei-f-7h9gp-image-registry-us-central1-gnxbjtgwaqqqvoyebtbqoo" level=debug msg="Listing objects for storage bucket gpei-f-7h9gp-image-registry-us-central1-gnxbjtgwaqqqvoyebtbqoo" level=debug msg="Deleting storate bucket gpei-f-7h9gp-image-registry-us-central1-gnxbjtgwaqqqvoyebtbqoo" level=info msg="Deleted bucket gpei-f-7h9gp-image-registry-us-central1-gnxbjtgwaqqqvoyebtbqoo"
Verified with payload 4.4.0-0.nightly-2019-12-20-210709 The storage buckets are deleted while cluster is destroying. And multiple dashes in the cluster name are replaced with one dash. level=debug msg="Listing storage buckets" level=debug msg="Found bucket: y-y-y-96ng4-image-registry-us-central1-ridrjrmdgpxiyvduoxiansn" level=debug msg="Listing objects for storage bucket y-y-y-96ng4-image-registry-us-central1-ridrjrmdgpxiyvduoxiansn" level=debug msg="Deleting storate bucket y-y-y-96ng4-image-registry-us-central1-ridrjrmdgpxiyvduoxiansn" level=info msg="Deleted bucket y-y-y-96ng4-image-registry-us-central1-ridrjrmdgpxiyvduoxiansn"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581