OCPBUGS-72547: Isolate and reduce parallelism for OrderedNamespaceDeletion tests. #30672
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
openshift-ci-robot
added
jira/valid-reference
openshift-merge-robot
added
the
needs-rebase
|
@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
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
benluddy
force-pushed
the
isolate-ordered-ns-deletion-4.22
branch
from
039042d to
7045327
Compare
openshift-merge-robot
removed
the
needs-rebase
|
/cc @xueqzhan |
|
Scheduling required tests: |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-techpreview 10 |
|
@benluddy: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/77bedc60-efc8-11f0-8565-9750edda196d-0 |
|
/lgtm and the tiniest little interval in the prow intervals view for OrderedNamespaceDeletion |
openshift-ci
bot
added
lgtm
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
/payload-abort |
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.
benluddy
force-pushed
the
isolate-ordered-ns-deletion-4.22
branch
from
7045327 to
050117b
Compare
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-techpreview 10 |
|
@benluddy: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/59d2dff0-efd5-11f0-8dcf-aa2d85cd268b-0 |
|
Scheduling required tests: |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-techpreview 10 |
|
@benluddy: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7d87e790-eff5-11f0-98ac-82570f69e3b6-0 |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-techpreview 10 |
|
@benluddy: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0c391920-f094-11f0-9b47-ee5a6abe51be-0 |
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, neisw The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label acknowledge-critical-fixes-only |
openshift-ci-robot
added
the
verified
|
@benluddy: This PR has been marked as verified by DetailsIn response to this:
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
bot
added
the
acknowledge-critical-fixes-only
|
@benluddy: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@benluddy: Jira Issue Verification Checks: Jira Issue OCPBUGS-72547 Jira Issue OCPBUGS-72547 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
4 participants
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).