Failing test(s): TestAccComputeBackend* with Security Policy

[SarahFrench]

Failure rates

• TestAccComputeBackendService_withSecurityPolicy: 63% since 2023-12-01

As of 2024-02-23:

• TestAccComputeBackendBucket_backendBucketSecurityPolicyExample Beta: 29.5% (36 / 122)
• TestAccComputeBackendBucket_backendBucketSecurityPolicyExample GA: 16.3% (20/123)
• TestAccComputeBackendService_withSecurityPolicy GA: 29.8% (27 / 124)

Impacted tests

• TestAccComputeBackendService_withSecurityPolicy
• TestAccComputeBackendBucket_backendBucketSecurityPolicyExample
• TestAccComputeBackendBucket_withSecurityPolicy

Affected Resource(s)

• google_compute_backend_service
• google_compute_backend_bucket

Nightly build test history

• TestAccComputeBackendService_withSecurityPolicy
• TestAccComputeBackendBucket_backendBucketSecurityPolicyExample GA
• TestAccComputeBackendBucket_backendBucketSecurityPolicyExample Beta

Message(s)

------- Stdout: -------
=== RUN   TestAccComputeBackendService_withSecurityPolicy
=== PAUSE TestAccComputeBackendService_withSecurityPolicy
=== CONT  TestAccComputeBackendService_withSecurityPolicy
    vcr_utils.go:152: Step 1/4 error: Error running apply: exit status 1
        Error: Error waiting for Creating SecurityPolicy "tf-test-f6ykgicod2": timeout while waiting for state to become 'DONE' (last state: 'RUNNING', timeout: 8m0s)
          with google_compute_security_policy.edgePolicy,
          on terraform_plugin_test.tf line 21, in resource "google_compute_security_policy" "edgePolicy":
          21: resource "google_compute_security_policy" "edgePolicy" {
    testing_new.go:84: Error running post-test destroy, there may be dangling resources: exit status 1
        Error: Error waiting for Deleting SecurityPolicy: timeout while waiting for state to become 'DONE' (last state: 'RUNNING', timeout: 8m0s)
--- FAIL: TestAccComputeBackendService_withSecurityPolicy (965.80s)
FAIL

b/315874492

[rileykarson]

This resource may just need a default timeout bump, the defaults are much higher nowadays (it was 20m or 30m) so we're setting it lower.

[melinath]

This is still failing; it's just taking longer to fail now.

[rileykarson]

This failed recently, and curiously, I can't query the operations- they seem to no longer exist. Weird. They are still timing out on inserts at 20m.

[melinath]

Reopening this - @NickElliot could you check in again next week to see if the test is passing consistently?

[NickElliot]

success rate remains unchanged