Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

create start instance tests: should create instance from custom image failed #720

Closed
flaky-bot bot opened this issue Apr 29, 2022 · 2 comments
Closed
Labels
api: compute Issues related to the googleapis/nodejs-compute API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. 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 Apr 29, 2022

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: 072a9bd
buildURL: Build Status, Sponge
status: failed

Test output
Command failed: node instances/create-start-instance/createInstanceFromCustomImage long-door-651 europe-central2-b gcloud-test--f1f042f1-51bc-480 https://www.googleapis.com/compute/v1/projects/debian-cloud/global/images/debian-10-buster-v20220406
The resource 'projects/long-door-651/zones/europe-central2-b/instances/gcloud-test--f1f042f1-51bc-480' already exists

Error: Command failed: node instances/create-start-instance/createInstanceFromCustomImage long-door-651 europe-central2-b gcloud-test--f1f042f1-51bc-480 https://www.googleapis.com/compute/v1/projects/debian-cloud/global/images/debian-10-buster-v20220406
The resource 'projects/long-door-651/zones/europe-central2-b/instances/gcloud-test--f1f042f1-51bc-480' already exists

at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (test/createStartInstance.test.js:31:28)
at Context.<anonymous> (test/createStartInstance.test.js:197:20)</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 Apr 29, 2022
@product-auto-label product-auto-label bot added the api: compute Issues related to the googleapis/nodejs-compute API. label Apr 29, 2022
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label May 2, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented May 2, 2022

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.


When run at the same commit (072a9bd), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@sofisl
Copy link
Contributor

sofisl commented May 3, 2022

I'm going to assume there was some type of outage, see:

#722
#721
#720

All have been passing since 5 days ago. Will let this reopen if necessary.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api: compute Issues related to the googleapis/nodejs-compute API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. 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

1 participant