Bug 1880132
| Summary: | GCP destroy leaves members in project IAM policy | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Abhinav Dahiya <adahiya> | |
| Component: | Installer | Assignee: | Abhinav Dahiya <adahiya> | |
| Installer sub component: | openshift-installer | QA Contact: | To Hung Sze <tsze> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | urgent | |||
| Priority: | urgent | CC: | tsze, wking | |
| Version: | 4.6 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.6.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1880134 (view as bug list) | Environment: | ||
| Last Closed: | 2020-10-27 16:42:20 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1880134 | |||
don't see any IAM left behind today using 4.6.0-0.nightly-2020-09-21-081745 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.6 GA Images), 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:4196 |
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.