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

Failing test(s): TestAccFirestoreField_firestoreFieldUpdateAddIndexExample #17392

Closed
melinath opened this issue Feb 24, 2024 · 2 comments · Fixed by GoogleCloudPlatform/magic-modules#9957, #17490 or hashicorp/terraform-provider-google-beta#7046

Comments

@melinath
Copy link
Collaborator

melinath commented Feb 24, 2024

Failure rates

  • 100% since 2024-01-22 (Technically since 2023-11-15, but that was initially due to a separate error.)

Impacted tests

  • TestAccFirestoreField_firestoreFieldUpdateAddIndexExample

Affected Resource(s)

  • google_firestore_field

Nightly build test history

Message(s)

testing_new.go:84: Error running post-test destroy, there may be dangling resources: googleapi: Error 403: Cloud Firestore API has not been used in project tf-testld8dsvlqop before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/firestore.googleapis.com/overview?project=tf-testld8dsvlqop then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.

b/326671122

@github-actions github-actions bot added forward/review In review; remove label to forward service/firestore-dataplane labels Feb 24, 2024
@melinath melinath removed the forward/review In review; remove label to forward label Feb 24, 2024
@SarahFrench
Copy link
Member

Note from triage: the problem here is that the test deletes all provisioned resources (including the project everything is contained in) and then runs the post destroy when the API is disabled. We could make the post destroy accept this error as expected, and not causing the test to fail.

Copy link

github-actions bot commented Apr 5, 2024

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 Apr 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.