[WIP] revert: Increase pod readiness timeout #29486
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sohankunkerkar The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6-techpreview |
|
@sohankunkerkar: trigger 3 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/2ff31c40-dcf3-11ef-947b-153d825f2505-0 |
|
/retest |
|
Let me know if there are any other tests that should be run against this PR. Once you're comfortable, I'll prepare this PR for merging. |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6-techpreview |
|
@sohankunkerkar: trigger 2 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/ee03bef0-dd80-11ef-872e-e9a60ba55597-0 |
|
/retest |
|
I don't think MicroShift even runs these tests. UDN is not available on MicroShift. |
@pmtk There are other tests that have passed. Do you have a list of the tests that should be passing in this case? |
|
@sohankunkerkar were there any UDN tests that flaked in the runs you performed on the PR? |
|
@kyrtapz This PR has been raised to understand if we are still hitting https://issues.redhat.com/browse/OCPBUGS-48362 |
|
Job Failure Risk Analysis for sha: 06e0ecf
|
|
/test |
|
@sohankunkerkar: The The following commands are available to trigger optional jobs: Use In 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 kubernetes-sigs/prow repository. |
|
/test ? |
|
@sohankunkerkar: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use In 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 kubernetes-sigs/prow repository. |
|
/retest |
|
/test e2e-vsphere-ovn-techpreview |
|
@sohankunkerkar: The specified target(s) for The following commands are available to trigger optional jobs: Use In 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 kubernetes-sigs/prow repository. |
|
PR needs rebase. 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. |
openshift-merge-robot
added
the
needs-rebase
|
@sohankunkerkar: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
We recently fixed the CRI-O-specific issue where we decoupled the CRI-O readiness check from the CNI plugin in watchdog support. We wanted to see if this helps alleviate the test and, in turn, remove the hack we set up for the pod readiness timeout.