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

compute: should return a helpful message on request response.statusCode 403 failed #1606

Closed
flaky-bot bot opened this issue Jul 20, 2023 · 1 comment
Closed
Labels
api: compute Issues related to the Compute Engine API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Jul 20, 2023

Note: #1572 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.


commit: d8e5eb9
buildURL: Build Status, Sponge
status: failed

Test output
The input did not match the regular expression /A Forbidden error was returned while attempting to retrieve an access token for the Compute Engine built-in service account. This may be because the Compute Engine instance does not have the correct permission scopes specified. Could not refresh access token./. Input:

'FetchError: request to http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token failed, reason: Nock: No match for request {\n' +
' "method": "GET",\n' +
' "url": "http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token",\n' +
' "headers": {\n' +
' "metadata-flavor": [\n' +
' "Google"\n' +
' ],\n' +
' "accept": [\n' +
' "/"\n' +
' ],\n' +
' "user-agent": [\n' +
' "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)"\n' +
' ],\n' +
' "accept-encoding": [\n' +
' "gzip,deflate"\n' +
' ],\n' +
' "connection": [\n' +
' "close"\n' +
' ]\n' +
' }\n' +
'}'

AssertionError [ERR_ASSERTION]: The input did not match the regular expression /A Forbidden error was returned while attempting to retrieve an access token for the Compute Engine built-in service account. This may be because the Compute Engine instance does not have the correct permission scopes specified. Could not refresh access token./. Input:

'FetchError: request to http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token failed, reason: Nock: No match for request {\n' +
' "method": "GET",\n' +
' "url": "http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token",\n' +
' "headers": {\n' +
' "metadata-flavor": [\n' +
' "Google"\n' +
' ],\n' +
' "accept": [\n' +
' "/"\n' +
' ],\n' +
' "user-agent": [\n' +
' "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)"\n' +
' ],\n' +
' "accept-encoding": [\n' +
' "gzip,deflate"\n' +
' ],\n' +
' "connection": [\n' +
' "close"\n' +
' ]\n' +
' }\n' +
'}'

at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Context.<anonymous> (test/test.compute.ts:158:5)</pre></details>
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Jul 20, 2023
@product-auto-label product-auto-label bot added the api: compute Issues related to the Compute Engine API. label Jul 20, 2023
@flaky-bot
Copy link
Author

flaky-bot bot commented Jul 20, 2023

Test passed for commit 90ea4de (Build Status, Sponge)! Closing this issue.

@flaky-bot flaky-bot bot closed this as completed Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: compute Issues related to the Compute Engine API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

0 participants