OCPBUGS-73810: Handle agent UI driven install cluster install page properly #1837
Conversation
The transition from the cluster-install page to the operator page often fails, particularly for version 4.21 and later. Add a wait and retry to ensure that the cluster install has started properly.
bfournie
changed the title
|
@bfournie: The following test failed, say
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. |
|
From the iso-no-registry test at https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift-metal3_dev-scripts/1837/pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-compact-ipv4-iso-no-registry/2011538761690648576/artifacts/e2e-agent-compact-ipv4-iso-no-registry/agent-gather/artifacts/ we can see that that the screenshots now get past 01-cluster-details.png |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andfasano 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 |
openshift-ci
bot
added
the
approved
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
/unhold |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/lgtm |
openshift-merge-bot
bot
merged commit c68ed3f
into
openshift-metal3:master
2 participants
The transition from the cluster-install page to the operator page often fails, particularly for version 4.21 and later. Add a wait and retry to ensure that the cluster install has started properly.