Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error applying IAM policy #116

Open
vfarcic opened this issue Jun 17, 2020 · 5 comments
Open

Error applying IAM policy #116

vfarcic opened this issue Jun 17, 2020 · 5 comments

Comments

@vfarcic
Copy link

vfarcic commented Jun 17, 2020

I'm getting the following error message.

Error: Error applying IAM policy for service account 'projects/jx-20200617185112/serviceAccounts/[email protected]': Error setting IAM policy for service account 'projects/jx-20200617185112/serviceAccounts/[email protected]': googleapi: Error 400: Identity namespace does not exist (jx-20200617185112.svc.id.goog)., badRequest

I tried it twice on a fresh Google project with the same result. However, if I re-run terraform apply again, it works. I'm guessing its some kind of a race condition and it tries to create resources before its dependencies are created.

@rawlingsj
Copy link
Member

@garethjevans mentioned this could be related to timing and with Terraform 0.13.0 it should help, with testing #130 which includes the 0.13.0 upgrade we've not seen this failure. Will close this once the PR has merged.

@damianesteban
Copy link

#130 was merged but I just received the same error.

@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@timdrysdale
Copy link

timdrysdale commented May 17, 2022

Received the same error on fresh Google project with v1.10.11 (latest at time of trying). Previous workaround in OP still works (i.e. reissue terraform apply)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants