Error applying IAM policy

[vfarcic]

I'm getting the following error message.

Error: Error applying IAM policy for service account 'projects/jx-20200617185112/serviceAccounts/jenkins-x-tekton@jx-20200617185112.iam.gserviceaccount.com': Error setting IAM policy for service account 'projects/jx-20200617185112/serviceAccounts/jenkins-x-tekton@jx-20200617185112.iam.gserviceaccount.com': 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]

@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]

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

[jenkins-x-bot]

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]

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]

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)