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

Spanner: should restore database from a backup using an encryption key failed #1553

Closed
flaky-bot bot opened this issue Jan 19, 2022 · 1 comment
Closed
Assignees
Labels
api: spanner Issues related to the googleapis/nodejs-spanner 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 Jan 19, 2022

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


commit: 9bdd28a
buildURL: Build Status, Sponge
status: failed

Test output
Command failed: node backups.js restoreBackupWithEncryptionKey test-instance-1642581595 test-database-1642581595-r-enc test-backup-1642581595-enc long-door-651 projects/long-door-651/locations/us-west1/keyRings/test-key-ring-node/cryptoKeys/test-key
backups.js restoreBackupWithEncryptionKey     

Restores a Cloud Spanner database from a backup with an encryption key.

Options:
--version Show version number [boolean]
--help Show help [boolean]

Error: 6 ALREADY_EXISTS: Database already exists: projects/long-door-651/instances/test-instance-1642581595/databases/test-database-1642581595-r-enc
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 /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:111:35
at Object.onReceiveStatus (/workspace/node_modules/grpc-gcp/build/src/index.js:73:29)
at InterceptingListenerImpl.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:106:23)
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: 6,
details: 'Database already exists: projects/long-door-651/instances/test-instance-1642581595/databases/test-database-1642581595-r-enc',
metadata: Metadata {
internalRepr: Map {
'google.rpc.resourceinfo-bin' => [Array],
'grpc-status-details-bin' => [Array],
'grpc-server-stats-bin' => [Array]
},
options: {}
}
}

Error: Command failed: node backups.js restoreBackupWithEncryptionKey test-instance-1642581595 test-database-1642581595-r-enc test-backup-1642581595-enc long-door-651 projects/long-door-651/locations/us-west1/keyRings/test-key-ring-node/cryptoKeys/test-key
backups.js restoreBackupWithEncryptionKey

Restores a Cloud Spanner database from a backup with an encryption key.

Options:
--version Show version number [boolean]
--help Show help [boolean]

Error: 6 ALREADY_EXISTS: Database already exists: projects/long-door-651/instances/test-instance-1642581595/databases/test-database-1642581595-r-enc
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 /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:111:35
at Object.onReceiveStatus (/workspace/node_modules/grpc-gcp/build/src/index.js:73:29)
at InterceptingListenerImpl.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:106:23)
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: 6,
details: 'Database already exists: projects/long-door-651/instances/test-instance-1642581595/databases/test-database-1642581595-r-enc',
metadata: Metadata {
internalRepr: Map {
'google.rpc.resourceinfo-bin' => [Array],
'grpc-status-details-bin' => [Array],
'grpc-server-stats-bin' => [Array]
},
options: {}
}
}

at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (system-test/spanner.test.js:24:28)
at Context.<anonymous> (system-test/spanner.test.js:1099: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 Jan 19, 2022
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/nodejs-spanner API. label Jan 19, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Jan 19, 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 (9bdd28a), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jan 19, 2022
gcf-owl-bot bot added a commit that referenced this issue Aug 26, 2022
fix: use google-gax v3.3.0
Source-Link: googleapis/synthtool@c73d112
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:b15a6f06cc06dcffa11e1bebdf1a74b6775a134aac24a0f86f51ddf728eb373e
gcf-merge-on-green bot pushed a commit that referenced this issue Sep 29, 2022
fix: use google-gax v3.3.0
Source-Link: googleapis/synthtool@c73d112
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:b15a6f06cc06dcffa11e1bebdf1a74b6775a134aac24a0f86f51ddf728eb373e
gcf-merge-on-green bot pushed a commit that referenced this issue Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the googleapis/nodejs-spanner 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