-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Approved
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
A few [OCPFeatureGate:MachineConfigNodes] tests are timing out with the new Kubernetes 1.33. Here are a few examples (you may need to open the build log and search for [OCPFeatureGate:MachineConfigNodes): https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-kubernetes-2314-ci-4.20-e2e-aws-ovn-techpreview-serial/1937808306517053440 https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-kubernetes-2314-ci-4.20-e2e-aws-ovn-techpreview-serial/1937590758836015104 https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-kubernetes-2314-ci-4.20-e2e-aws-ovn-techpreview-serial/1937453041783410688 Slack thread: https://redhat-internal.slack.com/archives/C08KA82J2JF/p1750872747496629
Version-Release number of selected component (if applicable):
How reproducible:
This is consistently happening in CI jobs. I was able to reproduce it with a cluster-bot cluster, but that's not always the case.
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- is depended on by
-
MCO-1655 Update MCO dependencies to Kubernetes 1.33
-
- Release Pending
-