[release-5.0] NO-ISSUE: Use --wait=false for namespace deletion in RF teardowns

[agullon]

Summary

Backport of #7305 to release-5.0.

• Use --wait=false in the Remove Namespace RF keyword so oc delete namespace returns immediately instead of blocking until all finalizers are processed.

Root cause: On ARM with dual-stack, OVN reconciliation after a network config change (dual-stack → single-stack) saturates the CPU. When suite teardown fires oc delete namespace during this window, the namespace garbage collection — competing with OVN for CPU — exceeds the 5-minute RF process timeout in Run With Kubeconfig. The killed oc process returns rc=1, the Should Be Equal As Integers assertion fails, and all passing tests are retroactively marked as suite teardown failures.

Fix: --wait=false marks the namespace for deletion and returns immediately. The API server continues cleanup asynchronously. This is safe because:

• All 13 callers of Remove Namespace use it in teardown contexts where no subsequent test depends on the namespace being fully gone
• Test VMs are torn down after the suite completes, so any in-progress namespace deletion is irrelevant

Observed in: e2e-aws-tests-bootc-release-arm-el9, scenario el98-lrel@dual-stack-configuration1 — all 4 dual-stack tests passed but were retroactively marked failed due to suite teardown timeout.

Test plan

• Verify no caller of Remove Namespace depends on synchronous namespace deletion
• Confirm dual-stack suite teardown completes without timeout on ARM

🤖 Generated with Claude Code

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@agullon: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Backport of #7305 to release-5.0.

• Use --wait=false in the Remove Namespace RF keyword so oc delete namespace returns immediately instead of blocking until all finalizers are processed.

Root cause: On ARM with dual-stack, OVN reconciliation after a network config change (dual-stack → single-stack) saturates the CPU. When suite teardown fires oc delete namespace during this window, the namespace garbage collection — competing with OVN for CPU — exceeds the 5-minute RF process timeout in Run With Kubeconfig. The killed oc process returns rc=1, the Should Be Equal As Integers assertion fails, and all passing tests are retroactively marked as suite teardown failures.

Fix: --wait=false marks the namespace for deletion and returns immediately. The API server continues cleanup asynchronously. This is safe because:

• All 13 callers of Remove Namespace use it in teardown contexts where no subsequent test depends on the namespace being fully gone
• Test VMs are torn down after the suite completes, so any in-progress namespace deletion is irrelevant

Observed in: e2e-aws-tests-bootc-release-arm-el9, scenario el98-lrel@dual-stack-configuration1 — all 4 dual-stack tests passed but were retroactively marked failed due to suite teardown timeout.

Test plan

• Verify no caller of Remove Namespace depends on synchronous namespace deletion
• Confirm dual-stack suite teardown completes without timeout on ARM

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 62371fd1-1203-43a6-a83c-a2e821761818

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [agullon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@agullon: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[agullon]

Consolidated into #7327