Acquire install lease when provisioning a cluster 2#76958
Acquire install lease when provisioning a cluster 2#76958danilo-gemoli wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danilo-gemoli, jupierce 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 |
|
/pj-rehearse list |
|
@danilo-gemoli: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
A total of 29200 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-cri-o-cri-o-main-e2e-aws-ovn |
|
@danilo-gemoli: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@danilo-gemoli: 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. |
Continuation of #76238.
The
ipi-install-installcreates a cluster in a retry loop and, on iterationn, it destroys the cluster of the previous iterationn-1before proceeding any further.The
openshift-install destroy clustercommand should be made safe by acquiring an install lease as it has been done foropenshift-install create cluster.