instances: should list zones failed

[flaky-bot[bot]]

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

---

commit: 6669c370436ee80d8a453253312d685573a855a7 buildURL: Build Status, Sponge status: failed

Test output

Command failed: node instances.js run --instance gcloud-tests-e65e214c-9b5e-456 --cluster gcloud-tests-8cfb58ea-9263-426
instances.js run
Creates an Instance(type: PRODUCTION) and run basic instance-operations
Options:
--version   Show version number                                                                              [boolean]
--instance  Cloud Bigtable Instance ID
--cluster   Cloud Bigtable Cluster ID
--help      Show help                                                                                        [boolean]
Error: 5 NOT_FOUND: Instance projects/long-door-651/instances/gcloud-tests-e65e214c-9b5e-456 not found.
at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:180:52)
at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:182:78
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
code: 5,
details: 'Instance projects/long-door-651/instances/gcloud-tests-e65e214c-9b5e-456 not found.',
metadata: Metadata {
internalRepr: Map { 'grpc-server-stats-bin' => [Array] },
options: {}
},
note: 'Exception occurred in retry method that was not classified as transient'
}
Error: Command failed: node instances.js run --instance gcloud-tests-e65e214c-9b5e-456 --cluster gcloud-tests-8cfb58ea-9263-426
instances.js run
Creates an Instance(type: PRODUCTION) and run basic instance-operations
Options:
--version   Show version number                                                                              [boolean]
--instance  Cloud Bigtable Instance ID
--cluster   Cloud Bigtable Cluster ID
--help      Show help                                                                                        [boolean]
Error: 5 NOT_FOUND: Instance projects/long-door-651/instances/gcloud-tests-e65e214c-9b5e-456 not found.
at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:180:52)
at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:182:78
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
code: 5,
details: 'Instance projects/long-door-651/instances/gcloud-tests-e65e214c-9b5e-456 not found.',
metadata: Metadata {
internalRepr: Map { 'grpc-server-stats-bin' => [Array] },
options: {}
},
note: 'Exception occurred in retry method that was not classified as transient'
}
at checkExecSyncError (child_process.js:635:11)
at execSync (child_process.js:671:15)
at exec (test/instances.test.js:23:21)
at Context.<anonymous> (test/instances.test.js:46:20)
at processImmediate (internal/timers.js:461:21)</pre></details>

[flaky-bot[bot]]

Looks like this issue is flaky. :worried:

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

A human should fix and close this.

---

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

[danieljbruce]

Consider upgrading this priority since I saw another instance of it here:

https://source.cloud.google.com/results/invocations/dfaaf34f-9112-479d-bc98-595d63d318bf/targets/cloud-devrel%2Fclient-libraries%2Fnodejs%2Fpresubmit%2Fgoogleapis%2Fnodejs-bigtable%2Fnode12%2Fsamples-test/log

Could block automatic updates from getting through.

[danieljbruce]

It is a timeout issue despite the timeout increasing in length.

[danieljbruce]

Showed up over a year ago and if it shows up again a new issue will be opened.