Skip to content

Define install lease for openshift-org-azure#76230

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
danilo-gemoli:feat/boskos/openshift-org-azure-install-lease
Mar 13, 2026
Merged

Define install lease for openshift-org-azure#76230
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
danilo-gemoli:feat/boskos/openshift-org-azure-install-lease

Conversation

@danilo-gemoli
Copy link
Contributor

@danilo-gemoli danilo-gemoli commented Mar 13, 2026

Those leases should be acquired right before the $ openshift-install create cluster command executes, and then released asynchronously after 15/20m.

32 is an arbitrary value, we will tune it along the way.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 13, 2026
@openshift-ci openshift-ci bot requested review from droslean and smg247 March 13, 2026 11:46
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 13, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@danilo-gemoli: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danilo-gemoli, Prucek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

@danilo-gemoli: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions 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.

@openshift-merge-bot openshift-merge-bot bot merged commit cdce4a9 into openshift:main Mar 13, 2026
11 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

@danilo-gemoli: Updated the resources configmap in namespace ci at cluster app.ci using the following files:

  • key boskos.yaml using file core-services/prow/02_config/_boskos.yaml
Details

In response to this:

Those leases should be acquired right before the $ openshift-install create cluster command executes, and then released asynchronously after 15/20m.

32 is an arbitrary value, we will tune it along the way.

Instructions 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants