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

Attaching multiple instances to the same ApigeeEnvironment will fail #11445

Closed
xuchenma opened this issue Apr 7, 2022 · 1 comment
Closed
Labels
persistent-bug Hard to diagnose or long lived bugs for which resolutions are more like feature work than bug work size/s
Milestone

Comments

@xuchenma
Copy link

xuchenma commented Apr 7, 2022

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

Terraform 0.12.29
Google Provider Version: 4.15.0

Affected Resource(s)

  • google_apigee_instance_attachment

Terraform Configuration Files

resource "google_apigee_instance_attachment" "dev-australia-southeast1" {
  instance_id  = "organizations/my-apigee-x-org/instances/australia-southeast1"
  environment  = "dev"
}

resource "google_apigee_instance_attachment" "dev-us-west1" {
  instance_id  = "organizations/my-apigee-x-org/instances/us-west1"
  environment  = "dev"
}

Expected Behavior

Successfully attach both instances.

Actual Behavior

...
2022-04-06T02:26:30.248Z [INFO] provider.terraform-provider-google_v4.16.0_x5: 2022/04/06 02:26:30 [DEBUG] Unlocking "organizations/my-apigee-x-org/instances/us-west1": timestamp=2022-04-06T02:26:30.248Z
2022-04-06T02:26:30.248Z [INFO] provider.terraform-provider-google_v4.16.0_x5: 2022/04/06 02:26:30 [DEBUG] Unlocked "organizations/my-apigee-x-org/instances/us-west1": timestamp=2022-04-06T02:26:30.248Z
[0m [1mgoogle_apigee_instance_attachment.dev-us-west1: Creation complete after 22s [id=organizations/my-apigee-x-org/instances/us-west1/attachments/dd9a81d9-80a2-4044-b6e5-f4ee1c874a55] [0m
[31m╷ [0m [0m
[31m│ [0m [0m [1m [31mError: [0m [0m [1mError creating InstanceAttachment: googleapi: Error 400: the resource is locked by another operation: 4dcff6d5-b825-4d26-a2f6-cbf4238fb07a
[31m│ [0m [0mDetails:
[31m│ [0m [0m[
[31m│ [0m [0m {
[31m│ [0m [0m "@type": "type.googleapis.com/google.rpc.RequestInfo",
[31m│ [0m [0m "requestId": "8212706593325358256"
[31m│ [0m [0m }
[31m│ [0m [0m] [0m
[31m│ [0m [0m
[31m│ [0m [0m [0m with google_apigee_instance_attachment.dev-australia-southeast1,
[31m│ [0m [0m on main.tf line 1, in resource "google_apigee_instance_attachment" "dev-australia-southeast1":
[31m│ [0m [0m 1: resource "google_apigee_instance_attachment" "dev-australia-southeast1" [4m{ [0m [0m
[31m│ [0m [0m
[31m╵ [0m [0m

Steps to Reproduce

  1. terraform apply

References

* #10525

@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 Sep 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
persistent-bug Hard to diagnose or long lived bugs for which resolutions are more like feature work than bug work size/s
Projects
None yet
Development

No branches or pull requests

3 participants