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

Deleting an age-based Bigtable GCPolicy hangs #10132

Closed
xiaobaitusi opened this issue Sep 22, 2021 · 7 comments
Closed

Deleting an age-based Bigtable GCPolicy hangs #10132

xiaobaitusi opened this issue Sep 22, 2021 · 7 comments

Comments

@xiaobaitusi
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

provider registry.terraform.io/hashicorp/google v3.85.0

Affected Resource(s)

  • google_bigtable_gc_policy

Terraform Configuration Files

resource "google_bigtable_gc_policy" "policy" {
  instance_name = "bigtableinstance-test"
  project       = "my-project"
  table         = "one"
  column_family = "onefam3"

  max_age {
    duration = "4h"
  }
}

Debug Output

...
2021-09-21T23:35:45.381-0700 [INFO]  plugin.terraform-provider-google_v3.85.0_x5: 2021/09/21 23:35:45 [DEBUG] Dismissed an error as retryable. Waiting for table to be in a valid state - rpc error: code = FailedPrecondition desc = Cannot relax pure age-based GC for a replicated family (onefam3). If you must relax the age constraint, unreplicate the instance and try again.: timestamp=2021-09-21T23:35:45.381-0700
2021-09-21T23:35:45.381-0700 [INFO]  plugin.terraform-provider-google_v3.85.0_x5: 2021/09/21 23:35:45 [TRACE] Waiting 10s before next try: timestamp=2021-09-21T23:35:45.381-0700
google_bigtable_gc_policy.policy: Still destroying... [id=age() > 2h, 19m50s elapsed]
2021-09-21T23:35:56.119-0700 [INFO]  plugin.terraform-provider-google_v3.85.0_x5: 2021/09/21 23:35:56 [DEBUG] Dismissed an error as retryable. Waiting for table to be in a valid state - rpc error: code = FailedPrecondition desc = Cannot relax pure age-based GC for a replicated family (onefam3). If you must relax the age constraint, unreplicate the instance and try again.: timestamp=2021-09-21T23:35:56.119-0700
2021-09-21T23:35:56.119-0700 [INFO]  plugin.terraform-provider-google_v3.85.0_x5: 2021/09/21 23:35:56 [TRACE] Waiting 10s before next try: timestamp=2021-09-21T23:35:56.119-0700
2021-09-21T23:36:00.723-0700 [INFO]  plugin.terraform-provider-google_v3.85.0_x5: 2021/09/21 23:36:00 [WARN] WaitForState timeout after 20m0s: timestamp=2021-09-21T23:36:00.722-0700

Panic Output

Expected Behavior

Terraform quickly returns an error similar to "Cannot relax pure age-based GC for a replicated family (onefam3). If you must relax the age constraint, unreplicate the instance and try again"

Actual Behavior

Terraform retries on the non-retryable error until 20 mins timeout

Steps to Reproduce

  1. Create a bigtable instance with two clusters.
  2. Create a bigtable table
  3. Create a age-based GC policy as mentioned above
  4. Delete the GC policy

Important Factoids

References

https://cloud.google.com/bigtable/docs/garbage-collection#changes

  • #0000
@xiaobaitusi
Copy link
Author

Any updates?

@kevinsi4508
Copy link
Contributor

We are working on the fix. Some errors are retryable, but not this one.

@kevinsi4508
Copy link
Contributor

kevinsi4508 commented Oct 10, 2022

The issue should be fixed with this PR: GoogleCloudPlatform/magic-modules#6612.

Please let us know if you continue to see the issue.

@kevinsi4508
Copy link
Contributor

I believe this issue should be closed now.

@melinath
Copy link
Collaborator

b/259277589

@melinath
Copy link
Collaborator

closing - it looks like the PR to resolve this issue was missing "Fixes {issue id}"

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants