This repository was archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
This repository was archived by the owner on Jul 13, 2023. It is now read-only.
container samples - create cluster long running op: should create cluster and wait for completion, and see the cluster in list failed #589
Copy link
Copy link
Closed
Labels
api: containerIssues related to the googleapis/nodejs-cloud-container API.Issues related to the googleapis/nodejs-cloud-container API.flakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.samplesIssues that are directly related to samples.Issues that are directly related to samples.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
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: de62f0b
buildURL: Build Status, Sponge
status: failed
Test output
Command failed: node create_cluster.js nodejs-container-test-3d1e8db0 us-central1-a default-compute 3 INVALID_ARGUMENT: This operation will exceed max secondary ranges per subnetwork (30) for subnet "default-compute", consider reusing existing secondary ranges or use a different subnetwork.Error: Command failed: node create_cluster.js nodejs-container-test-3d1e8db0 us-central1-a default-compute
3 INVALID_ARGUMENT: This operation will exceed max secondary ranges per subnetwork (30) for subnet "default-compute", consider reusing existing secondary ranges or use a different subnetwork.at checkExecSyncError (child_process.js:635:11) at Object.execSync (child_process.js:671:15) at execSync (system-test/create_cluster.test.js:24:28) at Context.<anonymous> (system-test/create_cluster.test.js:58:16) at processImmediate (internal/timers.js:461:21)</pre></details>
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
api: containerIssues related to the googleapis/nodejs-cloud-container API.Issues related to the googleapis/nodejs-cloud-container API.flakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.samplesIssues that are directly related to samples.Issues that are directly related to samples.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.