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.11] OCPBUGS-4530: Enable CVO unmanage overrides in bootstrap-in-place installations #6668
[release-4.11] OCPBUGS-4530: Enable CVO unmanage overrides in bootstrap-in-place installations #6668
Conversation
…tallations # Background openshift#5258 introduced a mechanism to tell CVO to not manage some cluster resources, as that management was creating races between bootkube and CVO. In openshift#5271, this mechanism was removed from bootstrap-in-place installations. The reason for the removal was because attempting to apply `original_cvo_overrides.patch` after the cluster-bootstrap podman container was done wasn't working, as in BIP by the time that that container is down, there's no longer a running kube-apiserver apply the patch on (unlike regular installations with a bootstrap node where the API server keeps running on the actual nodes). The justification for simply disabling the mechanism instead of finding a solution was based on an incorrect assumption that "CVO doesn't even run in BIP pre-pivot so there's no need to perform overrides anyway as there's no CVO to race with". # Issue Naturally, since CVO *is* actually running in the pre-pivot phase of bootstrap-in-place, not applying CVO overrides to disable the CVO management of bootkube-created resources led to the same races openshift#5258 was aiming to solve in bootstrap-in-place installations. One manifestation of that is OCPBUGS-4125. # Solution This commit re-introduces the mechanism that was originally introduced in openshift#5258 (and removed in openshift#5271). To solve the issue that motivated openshift#5271, this commit doesn't attempt to apply the `original_cvo_overrides.patch` in bootstrap-in-place pre-reboot, and instead will transfer `original_cvo_overrides.patch` through `master-update.fcc` to the post-pivot phase and the bootstrap-in-place post-reboot script will make sure to apply the patch after the API server is running again.
@omertuc: Jira Issue OCPBUGS-4506 has been cloned as Jira Issue OCPBUGS-4530. Retitling PR to link against new bug. 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. |
@omertuc: This pull request references Jira Issue OCPBUGS-4530, 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. |
@omertuc: No Bugzilla bug is referenced in the title of this pull 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. |
1 similar comment
@omertuc: No Bugzilla bug is referenced in the title of this pull 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. |
@omertuc: This pull request references Jira Issue OCPBUGS-4530, which is invalid:
Comment 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. |
/jira-refresh |
/jira refresh |
@patrickdillon: This pull request references Jira Issue OCPBUGS-4530, which is invalid:
Comment 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. |
/skip |
/label cherry-pick-approved |
/jira refresh |
@wking: This pull request references Jira Issue OCPBUGS-4530, which is invalid:
Comment 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. |
/jira refresh |
@chadcrum: This pull request references Jira Issue OCPBUGS-4530, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chadcrum, patrickdillon 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 |
@omertuc: 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. |
/test e2e-aws |
@omertuc: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-4530 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. |
/cherry-pick release-4.10 |
@omertuc: new pull request created: #6819 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. |
This is a manual cherry-pick of #6664