New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-4.12] OCPBUGS-14664: Shorten SNO installation duration by releasing CVO lease #7235
[release-4.12] OCPBUGS-14664: Shorten SNO installation duration by releasing CVO lease #7235
Conversation
… what the script is currently doing * Update sleep durations * Use [*] and not [0] in the jsonpath when checking the kube-apiserver-operator status because the pod may not exists yet * Remove /opt/openshift at the end of the installation, it was added during openshift#6649 and it should get cleaned up once the installation is complete * Check if api is available while waiting for kube-apiserver-operator ready status
…O 6 minutes to acquire the leader lease This is a workaround for the above issue, this code delete the cvo lease that was created during bootstrapping, allowing cvo to start faster without waiting for the lease to end.
@openshift-cherrypick-robot: Jira Issue OCPBUGS-10391 has been cloned as Jira Issue OCPBUGS-14664. Will retitle bug to link to clone. In response to this:
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/test-infra repository. |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-14664, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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/test-infra repository. |
@openshift-cherrypick-robot: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
/jira refresh |
@eranco74: This pull request references Jira Issue OCPBUGS-14664, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (ohochman@redhat.com), skipping review request. In response to this:
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/test-infra repository. |
@patrickdillon @r4f4 PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: r4f4 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/assign @gpei |
/label cherry-pick-approved |
/label backport-risk-assessed |
e3aeaf8
into
openshift:release-4.12
@openshift-cherrypick-robot: Jira Issue OCPBUGS-14664: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-14664 has been moved to the MODIFIED state. In response to this:
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/test-infra repository. |
Fix included in accepted release 4.12.0-0.nightly-2023-06-12-195509 |
This is an automated cherry-pick of #6757
/assign eranco74