Skip to content

Failing test(s): TestAccDNSRecordSet_routingPolicy #21770

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

Comments

@modular-magician
Copy link
Collaborator

modular-magician commented Mar 10, 2025

Impacted tests

TestAccDNSRecordSet_routingPolicy

Affected Resource(s)

google_dns_record_set

Failure rates

  • GA: 100%
  • Beta: 100%

Message(s)

=== RUN   TestAccDNSRecordSet_routingPolicy
=== PAUSE TestAccDNSRecordSet_routingPolicy
=== CONT  TestAccDNSRecordSet_routingPolicy
    resource_dns_record_set_test.go:292: Step 11/13 error: Error running apply: exit status 1
        
        Error: Error updating Subnetwork "projects/ci-test-project-nightly-ga/regions/us-central1/subnetworks/tf-test-proxy-subnet-dtfq3lcu77": googleapi: Error 400: Invalid resource usage: 'Patching is supported only for subnets with the purpose INTERNAL_HTTPS_LOAD_BALANCER to be changed to REGIONAL_MANAGED_PROXY, or from PEER_MIGRATION to PRIVATE.'., invalidResourceUsage
        
          with google_compute_subnetwork.proxy_subnet,
          on terraform_plugin_test.tf line 13, in resource "google_compute_subnetwork" "proxy_subnet":
          13: resource "google_compute_subnetwork" "proxy_subnet" {
        
--- FAIL: TestAccDNSRecordSet_routingPolicy (384.26s)
FAIL

Test Debug Log

b/401955357

@roaks3
Copy link
Collaborator

roaks3 commented Mar 27, 2025

As best I can tell, this was working initially, so perhaps a restriction on changing the purpose of the subnetwork was added. I don't this the test actually relies on that purpose changing, it looks like the tests were just chained together for convenience, so hopefully this can be fixed by moving the step out to its own test.

@hkundag
Copy link
Contributor

hkundag commented Mar 28, 2025

Agreed, we can either break up the test or make sure each individual test in the chain uses unique resource names to avoid collisions.

@nbodepudi
Copy link

Created pull request GoogleCloudPlatform/magic-modules#13711

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment