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 404 failed #1573

Closed
flaky-bot bot opened this issue Jun 24, 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 Jun 24, 2023

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.


commit: 070ec96
buildURL: Build Status, Sponge
status: failed

Test output
The input did not match the regular expression /A Not Found error was returned while attempting to retrieve an accesstoken for the Compute Engine built-in service account. This may be because the Compute Engine instance does not have any permission scopes specified./. 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 Not Found error was returned while attempting to retrieve an accesstoken for the Compute Engine built-in service account. This may be because the Compute Engine instance does not have any permission scopes specified./. 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 runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Context.<anonymous> (build/test/test.compute.js:137:9)
    -> /workspace/test/test.compute.ts:169: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 Jun 24, 2023
@product-auto-label product-auto-label bot added the api: compute Issues related to the Compute Engine API. label Jun 24, 2023
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 29, 2023

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

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