Skip to content

kms.api-client.snippets_test.TestKMSSnippets: test_symmetric_encrypt_decrypt failed #3555

Closed

Description

@flaky-bot

This test failed!

To configure my behavior, see the Build Cop Bot documentation.

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


commit: 1e072f2
buildURL: Build Status, Sponge
status: failed

Activity

  1. added
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Apr 25, 2020
  2. tmatsuo commented on Apr 25, 2020

    @tmatsuo
    Contributor

    encrypt_symmetric failed with google.api_core.exceptions.FailedPrecondition: 400 projects/python-docs-samples-tests/locations/global/keyRings/kms-samples/cryptoKeys/symmetric/cryptoKeyVersions/1 is not enabled, current state is: DESTROY_SCHEDULED.

  3. assigned and unassigned on Apr 25, 2020
  4. flaky-bot commented on Apr 26, 2020

    @flaky-bot
    Author

    commit: 2b74710
    buildURL: Build Status, Sponge
    status: failed

  5. flaky-bot commented on Apr 26, 2020

    @flaky-bot
    Author

    commit: 2b74710
    buildURL: Build Status, Sponge
    status: failed

  6. added a commit that references this issue on Apr 27, 2020
    019abbf
  7. added a commit that references this issue on Apr 28, 2020
    d56abf2
  8. flaky-bot commented on Apr 30, 2020

    @flaky-bot
    Author

    Looks like this issue is flaky. 😟

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

    A human should fix and close this.


    commit: 49fbc9c
    buildURL: Build Status, Sponge
    status: failed

  9. flaky-bot commented on Apr 30, 2020

    @flaky-bot
    Author

    Looks like this issue is flaky. 😟

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

    A human should fix and close this.


    commit: 49fbc9c
    buildURL: Build Status, Sponge
    status: failed

  10. tmatsuo commented on May 1, 2020

    @tmatsuo
    Contributor

    This should be fixed by adding a role to the service account.

  11. added a commit that references this issue on Nov 14, 2022
    f8136e0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions