Error updating apigee organization

[adrian-visoiu-db]

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 v0.13.2

Affected Resource(s)

• google_apigee_organization

Terraform Configuration Files

resource "google_apigee_organization" "apigee_internal_org" { analytics_region = var.analytics_region display_name = var.apigee_organization_name description = "Terraform-provisioned Apigee Internal" project_id = var.project runtime_database_encryption_key_name = var.google_kms_crypto_key authorized_network = var.network }

Apigee instance.

resource "google_apigee_instance" "apigee_internal_instance" { name = "${var.apigee_organization_name}-${var.apigee_instance_name}" location = var.primary_region org_id = google_apigee_organization.apigee_internal_org.id disk_encryption_key_name = var.google_kms_crypto_key peering_cidr_range = "SLASH_20" display_name = "${var.apigee_organization_name}-${var.apigee_instance_name}"

Debug Output

module.apigee_internal.google_apigee_organization.apigee_internal_org: Still modifying... [id=organizations/db-dev1-8wzd-apigee-i-1, 3m20s elapsed]

Error: Error waiting for Updating Organization: couldn't find resource (21 retries)

on modules/apigee-internal/main.tf line 2, in resource "google_apigee_organization" "apigee_internal_org": 2: resource "google_apigee_organization" "apigee_internal_org" {

Panic Output

Expected Behavior

Hi,

I am trying to create resources related to Apigee:

• Apigee Organization - was created successfully
• Apigee Instance - initial creation failed due to invalid name
• After changing the instance name in tf script - should have created the instance with appropiate name

I see the organization is created when calling GET https://apigee.googleapis.com/v1/organizations api ...{ "organization": "-apigee-i-1", "projectIds": [ "" ] }

Actual Behavior

After changing apigee instance in tf script I get the error mentioned in outputs: module.apigee_internal.google_apigee_organization.apigee_internal_org: Still modifying... [id=organizations/db-dev1-8wzd-apigee-i-1, 3m20s elapsed]

Error: Error waiting for Updating Organization: couldn't find resource (21 retries) on modules/apigee-internal/main.tf line 2, in resource "google_apigee_organization" "apigee_internal_org": 2: resource "google_apigee_organization" "apigee_internal_org" {

Steps to Reproduce

1. provide tf with valid apigee organization name and invalid apigee instance name -> only organization is created
2. provide with valid apigee organization name and valid apigee instance name -> timeout updating organization (can't find resource)

Important Factoids

References

• 0000

[adrian-visoiu-db]

Along with the Apigee Instance name there was a change in org name in the same time. First I’ve changed the org name from apigee-internal-org back to original apigee-internal – the script failed with the same error related to instance but I saw in /organizations API that the display name of the org was changed to apigee-internal.

Then I kept org name as reported by API (apigee-internal) and changed only the instance name to dev1-instance -> now the error related to org does not appear and the plan is not stalling.

[megan07]

Hi @adrian-visoiu-db ! Thanks for the update. Am I understanding that you solved the issue and it's working as expected? If so, are we able to close this issue? Thanks!

[megan07]

Hi @adrian-visoiu-db ! Is this still an issue?

[adrian-visoiu-db]

Hi @adrian-visoiu-db ! Is this still an issue?

Hi Megan, issue was solved as mentioned above, however it is up to you to consider investigating why having two resources A and B, B depending on A, having changes in both, B is not waiting for A's update and references an obsolete resource, to me it seems a problem with the tf planning.

[megan07]

@adrian-visoiu-db Thanks for the response! Would you mind adding some configurations here and what the plan looks like so that I can try and recreate it? Thanks!

[melinath]

b/270216759