Bug 2035454

Summary:	[IPI on Alibabacloud] the OSS bucket created during installation for image registry is not deleted after destroying the cluster
Product:	OpenShift Container Platform	Reporter:	Jianli Wei <jiwei>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED ERRATA	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.10	CC:	aos-bugs, brlu, bteng, gpei, mstaeble, xiameng, xiuwang
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-12 04:40:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jianli Wei 2021-12-24 05:56:24 UTC

Version:
$ openshift-install version
openshift-install 4.10.0-0.nightly-2021-12-23-193744
built from commit 94a3ed9cbe4db66dc50dab8b85d2abf40fb56426
release image registry.ci.openshift.org/ocp/release@sha256:c23a323ae7d5f788cc5f24d7281d745be6e1282b9f269e699530987be2b67e21
release architecture amd64

Platform: alibabacloud

Please specify:
* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)

What happened?
The OSS bucket created during installation for image registry is not deleted after destroying the cluster.

$ openshift-install destroy cluster --dir work --log-level info
INFO RAM roles deleted                             stage=RAM roles
INFO ECS instances deleted                         stage=ECS instances
INFO Private zones deleted                         stage=private zones
INFO SLB instances deleted                         stage=SLBs
INFO Security groups deleted                       stage=ECS security groups
INFO NAT gateways deleted                          stage=Nat gateways
INFO EIPs deleted                                  stage=EIPs
INFO VSwitches deleted                             stage=VSwitchs
INFO VPCs deleted                                  stage=VPCs
INFO Time elapsed: 1m58s
$
$ ossutil64 ls oss://jiwei-aa-km22m-image-registry-us-east-1-qpnbkwajjqempxqfohroen --endpoint oss-us-east-1.aliyuncs.com
Object Number is: 0

0.049043(s) elapsed
$

What did you expect to happen?
The OSS bucket should be automatically deleted after destroying the cluster. 

How to reproduce it (as minimally and precisely as possible)?
Always

Comment 2 mengxiaobing 2022-01-12 04:43:02 UTC

When the cluster is deleted, the Installer deletes the bucket.

Comment 3 XiuJuan Wang 2022-01-13 06:10:18 UTC

1. Launch cluster from pr.

$ ./ossutil64 ls oss://wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv
Object Number is: 0

0.460008(s) elapsed
$ ./ossutil64 ls oss://wxjali13-ct8h8-image-registry-us-west-1-swwlfhofqvolnhxganjxyc
Object Number is: 0

0.411011(s) elapsed

2. Push images to internal registry

3. Destroy the cluster
01-13 14:04:49.844  level=info msg=OSS bucket deleted bucketName=wxjali13-ct8h8-image-registry-us-west-1-swwlfhofqvolnhxganjxyc stage=OSS buckets
01-13 14:04:49.844  level=debug msg=Searching OSS bucket bucketName=wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv stage=OSS buckets
01-13 14:04:50.099  level=info msg=ECS instances deleted stage=ECS instances
01-13 14:04:50.099  level=debug msg=Searching RAM policy policyName=wxjali13-ct8h8-policy-worker stage=RAM roles
01-13 14:04:50.658  level=debug msg=Detaching policy for RAM role policyName=wxjali13-ct8h8-policy-worker principalName=wxjali13-ct8h8-role-worker.onaliyunservice.com stage=RAM roles
01-13 14:04:50.659  level=debug msg=Unbinding tags for OSS bucket bucketName=wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv stage=OSS buckets tags=[kubernetes.io/cluster/wxjali13-ct8h8]
01-13 14:04:52.021  level=debug msg=Searching OSS bucket objects bucketName=wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv stage=OSS buckets
01-13 14:04:52.277  level=debug msg=Deleting bucket objects bucketName=wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv objects=[docker/registry/v2/blobs/sha256/06/0661f10c38ccb1007a5937fd652f834283d016642264a0e031028979fcfb2dbf/data docker/registry/v2/blobs/sha256/11/1175096b4c5dfcdff7da64720ef32ce2e3a5b06e73e4a2f44173909dae848f89/data

4. Check the buckets
./ossutil64 ls oss://wxjali13-ct8h8-image-registry-us-west-1-swwlfhofqvolnhxganjxyc
Error: oss: service returned error: StatusCode=404, ErrorCode=NoSuchBucket, ErrorMessage="The specified bucket does not exist.", RequestId=61DFC1688083E7383199DC69, Bucket=wxjali13-ct8h8-image-registry-us-west-1-swwlfhofqvolnhxganjxyc, Object=
$ ./ossutil64 ls oss://wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv
Error: oss: service returned error: StatusCode=404, ErrorCode=NoSuchBucket, ErrorMessage="The specified bucket does not exist.", RequestId=61DFC16D2CAF3634372D6498, Bucket=wxjali13-ct8h8-image-registry-us-west-1-flechnmcbwyvoqiimvtwvv, Object=

Comment 9 errata-xmlrpc 2022-03-12 04:40:05 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056