OCPBUGS-72547: Isolate and reduce parallelism for OrderedNamespaceDeletion tests.

[benluddy]

These tests directly exercise the namespace controller (in kube-controller-manager), which can fall behind due to a combination of master node CPU saturation and the ephemeral namespace churn generated during parallel E2E runs. We observe flakes (timeouts) when this occurs. The tests are sensitive to CPU saturation, but not causing CPU saturation, so the goal of this change is to improve the CI signal until such time as the incidence of CPU saturation events in CI is reduced.

With this change, it passes 10/10 on the 4.21 job that was the basis of the related component readiness issue (https://issues.redhat.com/browse/OCPBUGS-67016): #30661 (comment).

[openshift-ci-robot]

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: automatic mode

[openshift-ci-robot]

@benluddy: This pull request references Jira Issue OCPBUGS-72547, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

These tests directly exercise the namespace controller (in kube-controller-manager), which can fall behind due to a combination of master node CPU saturation and the ephemeral namespace churn generated during parallel E2E runs. We observe flakes (timeouts) when this occurs. The tests are sensitive to CPU saturation, but not causing CPU saturation, so the goal of this change is to improve the CI signal until such time as the incidence of CPU saturation events in CI is reduced.

With this change, it passes 10/10 on the 4.21 job that was the basis of the related component readiness issue (https://issues.redhat.com/browse/OCPBUGS-67016): #30661 (comment).

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: benluddy
Once this PR has been reviewed and has the lgtm label, please assign smg247 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[benluddy]

/cc @xueqzhan

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-ci]

@benluddy: 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.