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): TestAccComputeTarget*Proxy* #14066

Assignees

Comments

@roaks3
Copy link
Collaborator

roaks3 commented Mar 22, 2023

Failure rates

  • 100% since 2023-03-09

Impacted tests

  • TestAccComputeTargetHttpsProxy_certificateMap
  • TestAccComputeTargetSslProxy_update

Affected Resource(s)

  • google_certificate_manager_dns_authorization

Nightly build test history

Message(s)

=== RUN   TestAccComputeTargetHttpsProxy_certificateMap
=== PAUSE TestAccComputeTargetHttpsProxy_certificateMap
=== CONT  TestAccComputeTargetHttpsProxy_certificateMap
    vcr_utils.go:140: Step 1/1 error: Error running apply: exit status 1
        
        Error: Error creating DnsAuthorization: googleapi: Error 400: Validation failed
        Details:
        [
          {
            "@type": "type.googleapis.com/google.rpc.PreconditionFailure",
            "violations": [
              {
                "description": "DNS authorization for the tuple (1067888929963, \"mysite.com\", DNS_AUTHORIZATION_FIXED_RECORD) already exists",
                "subject": "projects/1067888929963/locations/global/dnsAuthorizations/dnsauthorization-test-m09iyg8xt6",
                "type": "RESOURCE_INVALID"
              }
            ]
          }
        ]
        
          with google_certificate_manager_dns_authorization.instance,
          on terraform_plugin_test.tf line 50, in resource "google_certificate_manager_dns_authorization" "instance":
          50: resource "google_certificate_manager_dns_authorization" "instance" {
        
--- FAIL: TestAccComputeTargetHttpsProxy_certificateMap (114.64s)
FAIL
@roaks3
Copy link
Collaborator Author

roaks3 commented Mar 22, 2023

The leftover resources have been deleted, so this will likely start passing again. The PR will update the tests to use sweepable names, so that should help us avoid getting into this situation again.

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