-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18.z
-
None
-
None
-
False
-
This is a clone of issue OCPBUGS-43943. The following is the description of the original issue:
—
Description of problem:
TestNodePoolReplaceUpgrade e2e test on openstack is expereiencing common failures like this https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/4515/pull-ci-openshift-hypershift-main-e2e-openstack/1849445285156098048 After investigating this failure it looks like the imageRollout on openstack is completed instantly and it gives the noedpool very little time between the node becoming ready and the nodepool status version being set. The short amount of time causes a failure on this check https://github.com/openshift/hypershift/blob/6f6a78b7ff2932087b47609c5a16436bad5aeb1c/test/e2e/nodepool_upgrade_test.go#L166
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Flaky test
Steps to Reproduce:
1. Run the openstack e2e 2. 3.
Actual results:
TestNodePoolReplaceUpgrade fails
Expected results:
TestNodePoolReplaceUpgrade passes
Additional info:
- clones
-
OCPBUGS-43943 TestNodePoolReplaceUpgrade failure on openstack
- ON_QA
- is blocked by
-
OCPBUGS-43943 TestNodePoolReplaceUpgrade failure on openstack
- ON_QA