Failing test(s): TestAccRedisInstance_updateReadReplicasMode - "New subnetwork IP range (10.79.0.0/28) overlaps with an active peer network"

[SarahFrench]

Failure rates

• 11% since 2023-11-01

Impacted tests

• TestAccRedisInstance_updateReadReplicasMode

Affected Resource(s)

• google_redis_instance

Nightly build test history

• TestAccRedisInstance_updateReadReplicasMode

Message(s)

------- Stdout: -------
=== RUN   TestAccRedisInstance_updateReadReplicasMode
=== PAUSE TestAccRedisInstance_updateReadReplicasMode
=== CONT  TestAccRedisInstance_updateReadReplicasMode
    vcr_utils.go:152: Step 3/5 error: Error running apply: exit status 1
        Error: Error waiting for Updating Instance: Error code 9, message: New subnetwork IP range (10.79.0.0/28) overlaps with an active peer network (redis-peer-594424405950).
          with google_redis_instance.test,
          on terraform_plugin_test.tf line 2, in resource "google_redis_instance" "test":
           2: resource "google_redis_instance" "test" {
    testing_new.go:84: Error running post-test destroy, there may be dangling resources: exit status 1
        Error: Instance cannot be destroyed
          on terraform_plugin_test.tf line 2:
           2: resource "google_redis_instance" "test" {
        Resource google_redis_instance.test has lifecycle.prevent_destroy set, but
        the plan calls for this resource to be destroyed. To avoid this error and
        continue with the plan, either disable lifecycle.prevent_destroy or reduce
        the scope of the plan using the -target flag.
--- FAIL: TestAccRedisInstance_updateReadReplicasMode (382.61s)
FAIL

b/318812869

[himanikh]

I don't have access to the account to debug more but looks like the subnet range 10.79.0.0/28 is already being used. Switching to a new subnet or cleaning up whatever is blocking the 10.79.0.0/28 range would help.