-
Bug
-
Resolution: Unresolved
-
Major
-
4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
2
-
Important
-
None
-
None
-
Proposed
-
MCO Sprint 276
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The following tests are failling on each run with a "Some Pods are not ready in NS openshift-machine-config-operator" error: -[sig-mco][Suite:openshift/machine-config-operator/disruptive][OCPFeatureGate:OnClusterBuild][Serial][Disruptive] MCO ocb PolarionID:83140-A MachineOSConfig with custom containerfile definition can be successfully applied - [sig-mco][Suite:openshift/machine-config-operator/disruptive][OCPFeatureGate:OnClusterBuild][Serial][Disruptive] MCO ocb PolarionID:83141-A valid MachineOSConfig leads to a successful MachineOSBuild and cleanup of its associated resources - [sig-mco][Suite:openshift/machine-config-operator/disruptive][OCPFeatureGate:OnClusterBuild][Serial][Disruptive] MCO ocb PolarionID:77781-A successfully built MachineOSConfig can be re-build
Version-Release number of selected component (if applicable):
4.20.0
How reproducible:
100% of the times
Steps to Reproduce:
1.Deploy an AWS/GCP cluster
2.Run our OTE test suite
3.Wait for the tests to fail
Actual results:
Those 3 tests failling with the given error.
Expected results:
All tests should pass.
Additional info:
This failure happens because in https://github.com/openshift/machine-config-operator/pull/5200 we did not consider the OTE suite and it wasn't fixed to take into consideration that now the build pod uses an init container to build the image. As the init container takes more than 4 minutes to run the assertion fails as its pod is not ready in less than 4 minutes.
