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

failed to list instance groups for project \"<project>": failed to extract zone from self-link \"regions/europe-west2\"}" #70

Closed
bwplotka opened this issue Aug 15, 2019 · 3 comments · Fixed by #74

Comments

@bwplotka
Copy link

Hi 👋

Thanks for the awesome project!

We are having periodic errors from our vault clients attempting to login via GCP:

PUT http://<IP>:8200/v1/auth/gcp/login\nCode: 400. Errors:\n\n* failed to list instance groups for project \"<project>\": failed to extract zone from self-link \"regions/europe-west2\"}"

It is flaky. Sometimes this call works, sometimes not.

We are using:

  • GCE VMs
  • vault 1.1.0 which is built with this auth-gcp plugin from commit 7d4c2101e7d0b61ec9fb0dc3c75d79920c6369c5

Plugin code did not change from that point of time.

If we are not wrong this endpoint is used (?) by compute/v1 plugin is using:
https://www.googleapis.com/compute/v1/projects/<project>/aggregated/instanceGroups

And it indeed returns both keys regions/xxx as well as zones/xxx in response.

Any clue what might be happening? (:

@improbable-ludwik
Copy link

I have a no-op refactor + test that demonstrates the issue via a unit test. I'll raise a PR, then look at proposing a fix.

@improbable-ludwik
Copy link

The suggested fix is trivial, as per here: improbable-ludwik#1

^ for your consideration @jefferai .

@willdeuschle
Copy link

This PR #74 did not fix the issue as the keys returned from the InstanceGroup.AggregatedList call look like regions/europe-west1 rather than /regions/europe-west1.

I'd like to merge #84 to fix this.

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

Successfully merging a pull request may close this issue.

3 participants