Bug 1779329 - [GCP] openshift-install destroy cluster can leak buckets
Summary: [GCP] openshift-install destroy cluster can leak buckets
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.3.0
Assignee: Jeremiah Stuever
QA Contact: Yang Yang
URL:
Whiteboard:
Depends On: 1764812
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-03 18:53 UTC by Scott Dodson
Modified: 2020-01-23 11:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1764812
Environment:
Last Closed: 2020-01-23 11:17:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 2744 0 'None' closed [release-4.3] Bug 1779329: pkg/destroy/gcp/bucket.go: join multipe dashes when looking for cluster bucket prefix 2020-05-06 02:19:53 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:18:04 UTC

Comment 2 Yang Yang 2019-12-10 03:50:22 UTC 
Verified it on GCP with payload 4.3.0-0.nightly-2019-12-09-035405. 
The storage buckets are deleted while cluster is destroying. And multiple dashes in the cluster name are replaced with one dash.

# openshift-install destroy cluster --dir=test --log-level=debug

DEBUG Listing storage buckets                      
DEBUG Found bucket: y-y-y-vb24r-image-registry-us-central1-cbxnbtrvtrfthbjfrsppkqf 
DEBUG Listing objects for storage bucket y-y-y-vb24r-image-registry-us-central1-cbxnbtrvtrfthbjfrsppkqf 
DEBUG Deleting storate bucket y-y-y-vb24r-image-registry-us-central1-cbxnbtrvtrfthbjfrsppkqf 
INFO Deleted bucket y-y-y-vb24r-image-registry-us-central1-cbxnbtrvtrfthbjfrsppkqf
Comment 4 errata-xmlrpc 2020-01-23 11:17:46 UTC 
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:0062
Note You need to log in before you can comment on or make changes to this bug.