Bug 1880134 - GCP destroy leaves members in project IAM policy
Summary: GCP destroy leaves members in project IAM policy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.5.z
Assignee: Abhinav Dahiya
QA Contact: To Hung Sze
URL:
Whiteboard:
Depends On: 1880132
Blocks: 1880202
TreeView+ depends on / blocked
 
Reported: 2020-09-17 18:22 UTC by Abhinav Dahiya
Modified: 2020-09-30 14:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1880132
Environment:
Last Closed: 2020-09-30 14:07:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3760 0 None None None 2020-09-30 14:08:15 UTC

Description Abhinav Dahiya 2020-09-17 18:22:03 UTC
+++ This bug was initially created as a clone of Bug #1880132 +++

Description of problem:

GCP destroy leaves members in project IAM policy. This is because deleted service accounts end up converting the member in IAM policy to deleted:serviceAccount:{emailid}?uid={}

and the installer skips this member. I think there is a delay in service account deleted to the member getting modified and there fore the installer might clean up some of the ones that didn't get converted yet. This race definitely leaks in CI

How reproducible:

Steps to Reproduce:
1. Create cluster on GCP
2. Destroy the cluster
3. Check if all the member entries from project IAM policy has cleaned up.

Comment 5 To Hung Sze 2020-09-23 23:59:39 UTC
Used Flexy to install and destroy a cluster (114146) 4.5.0-0.nightly-2020-09-20-185910.
Don't see any left over IAM on GCP.
Closing.

Comment 7 errata-xmlrpc 2020-09-30 14:07:51 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 (OpenShift Container Platform 4.5.13 bug fix 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/RHBA-2020:3760


Note You need to log in before you can comment on or make changes to this bug.