-
Notifications
You must be signed in to change notification settings - Fork 724
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
1-org: Getting resource ancestry or parent failed: user does not have the correct permissions #1308
Comments
In the Observed Behavior section, the same error shows up for every resource type under Debug logs, which makes me suspect that Auth is misconfigured. I'm not able to reproduce in our CI pipelines, which successfully pass the plan and validate stages in from tf-wrapper.sh. Is this a persistent blocker, or transient? |
The
The role
Cloud you please check if the Service Account has the correct roles? |
@eeaton It's a persistent blocker. |
Hi all, I think I may be able to shed some light on the problem here. I've just had almost the exact same thing happen while adding a new project in this stage, and after a few hours of banging my head against it I managed to resolve it. The issue occurred for me when there had been a previously failed apply (I ran out of Project Quota). I was using the After getting the quota expanded I attempted to re-run the GitHub pipeline and received this same type of error, directed at the Eventually I noticed that the Hopefully this detail will aid in finding the root cause! 🤞 |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
TL;DR
When running
./tf-wrapper.sh plan_validate_all
as part of the Github tf-pull-request after creating PR, the following error is raised:Expected behavior
No errors
Observed behavior
Command and full output (loosely obfuscated):
Terraform Configuration
Terraform Version
Additional information
As mentioned in (provided link from error message)[https://cloud.google.com/docs/terraform/policy-validation/troubleshooting#ProjectCallerForbidden], I added
--verbosity=debug
to find the identity used during thegcloud beta terraform vet
call in thetf-wrapper.sh
script.Problem is that in Github will obfuscate that kind of thing and I end up with:
I then ran (what I believe is) the same
gcloud beta terraform vet
command using the[email protected]
but I get the same error.I noticed 2 (much) earlier issues somewhat related to this permission issue: #620 and #546
The text was updated successfully, but these errors were encountered: