Skip to content

chore(compute-v1): stop FirewallsSmokeTest teardown flakes with GCE Enforcer - #36719

Open
torreypayne wants to merge 1 commit into
mainfrom
chore/compute-v1-firewall-teardown
Open

torreypayne wants to merge 1 commit into
mainfrom
chore/compute-v1-firewall-teardown

Conversation

@torreypayne

Copy link
Copy Markdown
Member

Register the firewall name for teardown immediately after insert (before waiting on the operation) and ignore expected GCE Enforcer deletion conflicts during cleanup.

In helical-zone-771, GCE Enforcer removes API-created firewall rules shortly after creation regardless of source_ranges. That caused FirewallsSmokeTest#teardown to fail with Google::Cloud::InvalidArgumentError ("is not ready") when its delete overlapped the enforcer's, or to skip cleanup if @client_ops.wait raised first.

  • Keeps source_ranges unchanged (GCE Enforcer deletes non-GKE/non-AEF ingress rules regardless of range).
  • Rescues only NotFoundError and InvalidArgumentError matching "is not ready", re-raising everything else.
  • Validated locally against helical-zone-771 (FirewallsSmokeTest + simulated concurrent delete race) and unit tests on Ruby 3.2 and 4.0.

Tracking bug: http://b/568798581

@torreypayne
torreypayne requested review from a team and yoshi-approver as code owners November 13, 2026 23:31
@torreypayne
torreypayne requested a review from quartzmo November 13, 2026 23:53

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant