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): TestAccCompute* (Beta) ("Region X already has a Network Edge Security Service") #16745

Closed

Comments

@SarahFrench
Copy link
Member

SarahFrench commented Dec 8, 2023

Failure rates

  • 100% since 2023-11-10

Impacted tests

  • TestAccComputeInstanceNetworkIntefaceWithSecurityPolicy
  • TestAccComputeRegionSecurityPolicyRule_regionSecurityPolicyRuleNetworkMatchUpdate
  • TestAccComputeTargetInstance_withSecurityPolicy

Affected Resource(s)

  • google_compute_target_pool
  • google_compute_network_edge_security_service

Nightly build test history

Message(s)

Error: Error creating NetworkEdgeSecurityService: googleapi: Error 400: Invalid value for field 'resource.region': ''. Region us-west2 already has a Network Edge Security Service., invalid
@SarahFrench
Copy link
Member Author

I've tagged this as service/terraform as this issue is related to running tests in parallel in a single project. I think this can be addressed by ensuring tests run in different regions, and doesn't require service team involvement.

@shuyama1
Copy link
Collaborator

Cleaned up the dangling resources in the testing project and handwrite the sweeper to sweep resources in multiple regions (GoogleCloudPlatform/magic-modules#10216). Created #17835 to track support for sweeper in multi-region in mmv1 generator.

TestAccComputeInstanceNetworkIntefaceWithSecurityPolicy still failed consistently due to a different error. Created #17838 to track it.

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