Hide Forgot
+++ This bug was initially created as a clone of Bug #1782583 +++ Description of problem: Based on https://cloud.google.com/resource-manager/reference/rest/Shared.Types/Binding The members values can be: ``` deleted:serviceAccount:{emailid}?uid={uniqueid}: An email address (plus unique identifier) representing a service account that has been recently deleted. For example, my-other-app@appspot.gserviceaccount.com?uid=123456789012345678901. If the service account is undeleted, this value reverts to serviceAccount:{emailid} and the undeleted service account retains the role in the binding. ``` this looks like a new addition to the API since the archive from Oct 26, 2019 doesn't have these value type. see https://web.archive.org/web/20181026092140/https://cloud.google.com/resource-manager/reference/rest/Shared.Types/Binding Also it doesn't look like the API is being consistent with the result as two consecutive requests are returning different responses :P ``` [7:08:11] ➜ installer git:(add_platform_owners) ✗ gcloud projects get-iam-policy openshift-gce-devel-ci --format json | grep "ci-op-4wlm9" "serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-openshift-m-w75nq@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-w@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-openshift-i-nnvgl@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-openshift-i-zh522@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-openshift-m-w75nq@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-openshift-i-zh522@openshift-gce-devel-ci.iam.gserviceaccount.com", "serviceAccount:ci-op-4wlm9-w@openshift-gce-devel-ci.iam.gserviceaccount.com", [7:08:23] ➜ installer git:(add_platform_owners) ✗ gcloud projects get-iam-policy openshift-gce-devel-ci --format json | grep "ci-op-4wlm9" "deleted:serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=111636284758116941377", "deleted:serviceAccount:ci-op-4wlm9-openshift-m-w75nq@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=115542993089051207368", "deleted:serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=111636284758116941377", "deleted:serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=111636284758116941377", "deleted:serviceAccount:ci-op-4wlm9-w@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=106651455962694555805", "deleted:serviceAccount:ci-op-4wlm9-openshift-i-nnvgl@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=113695655870612204124", "deleted:serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=111636284758116941377", "deleted:serviceAccount:ci-op-4wlm9-openshift-i-zh522@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=103715387178859573892", "deleted:serviceAccount:ci-op-4wlm9-openshift-m-w75nq@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=115542993089051207368", "deleted:serviceAccount:ci-op-4wlm9-m@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=111636284758116941377", "deleted:serviceAccount:ci-op-4wlm9-openshift-i-zh522@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=103715387178859573892", "deleted:serviceAccount:ci-op-4wlm9-w@openshift-gce-devel-ci.iam.gserviceaccount.com?uid=106651455962694555805", ``` The installer destroy skips over these `deleted:` prefixed bindings.
Verified with payload release:4.3.0-0.nightly-2019-12-13-032731. No service accounts can be found after cluster destroy. Steps of verification as below: 1. Get the service accounts after the cluster setup # gcloud projects get-iam-policy openshift-qe --format json | grep "yyupi3" "serviceAccount:yyupi3-sng9s-m@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-openshift-m-tbwwn@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-m@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-m@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-w@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-openshift-i-lghj2@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-m@openshift-qe.iam.gserviceaccount.com", "serviceAccount:yyupi3-sng9s-openshift-i-2jg8c@openshift-qe.iam.gserviceaccount.com", "serviceAccount:yyupi3-sng9s-openshift-m-tbwwn@openshift-qe.iam.gserviceaccount.com" "serviceAccount:yyupi3-sng9s-m@openshift-qe.iam.gserviceaccount.com", "serviceAccount:yyupi3-sng9s-openshift-i-2jg8c@openshift-qe.iam.gserviceaccount.com", "serviceAccount:yyupi3-sng9s-w@openshift-qe.iam.gserviceaccount.com" 2. Get the service accounts after the cluster is destroyed # gcloud projects get-iam-policy openshift-qe --format json | grep "yyupi3" No output
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