-
Notifications
You must be signed in to change notification settings - Fork 247
OCPBUGS-1482: Don't override schedulableMasters unnecessarily #4414
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
OCPBUGS-1482: Don't override schedulableMasters unnecessarily #4414
Conversation
When generating the Ignition files, the installer already sets schdulableMasters to true when there are no worker nodes (i.e. in the SNO and compact cluster topologies. (See openshift/installer#2004) Therefore it is unnecessary to override it here (though it may be preferred to avoid a warning log from the installer). Since openshift/installer#6247, attempting to override the schedulableMasters setting causes installation to fail, because there are two manifests of the same type and name that conflict. Since we don't need to set this override when the installer would already do it, avoid doing so and triggering the error when the value is determined by the number of hosts rather than explicitly set by the user. The conflict still needs to be resolved so that the user can enable schedulableMasters, but this at least allows the SNO and compact topologies to install OpenShift 4.12 again. This partially reverts commit c45f369.
|
@zaneb: This pull request references Jira Issue OCPBUGS-1482, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/test e2e-agent-compact |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4414 +/- ##
==========================================
- Coverage 66.71% 66.71% -0.01%
==========================================
Files 195 196 +1
Lines 27335 27355 +20
==========================================
+ Hits 18236 18249 +13
- Misses 7468 7475 +7
Partials 1631 1631
|
|
@zaneb: 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/test-infra repository. I understand the commands that are listed here. |
|
/uncc |
Is this the case for all versions we support? |
|
/test ? |
|
@carbonin: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
DetailsIn 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. |
Looks like the change to the installer is in 4.8 as openshift/installer@64f96df |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carbonin, zaneb 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 |
|
Let's make sure we handle this properly in a follow up. That said it doesn't seem like this will cause a problem and it will unblock the agent team so I'm good with merging. |
|
This is indeed referencing a bug, and it's an issue regarding the agent installer targeted to 4.12. IMO this shouldn't be an invalid bug. |
|
@zaneb: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-1482 has been moved to the MODIFIED state. DetailsIn 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#4414)" This reverts commit 5661d9c.
|
/cherry-pick release-ocm-2.6 |
|
@filanov: new pull request created: #4445 DetailsIn 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#4414)" This reverts commit 5661d9c. Let's go back to applying the schedulable masters patch when either SchedulableMastersForce or SchedulableMasters are set.
* MGMT-12435: Add a way to apply patches to core manifests Starting in 4.12 it's not possible to completely overwrite existing manifests, the way AI was doing it. Core manifests that need to be modified should be patched instead. This PR adds a logic to upload patches to the manifests api and then apply them. Note that the InfrastructureCR patching was not changed to us this new flow as this PR focuses only in adding this possibility and changing the SchedulableMasters flow. Future PRs will align the rest of the codebase. Signed-off-by: Flavio Percoco <[email protected]> * Defer delete of manifests dir in case of error Signed-off-by: Flavio Percoco <[email protected]> * Address review comments Signed-off-by: Flavio Percoco <[email protected]> * Revert "OCPBUGS-1482: Don't override schedulableMasters unnecessarily (#4414)" This reverts commit 5661d9c. Let's go back to applying the schedulable masters patch when either SchedulableMastersForce or SchedulableMasters are set. Signed-off-by: Flavio Percoco <[email protected]> Co-authored-by: Flavio Percoco <[email protected]>
…openshift#4414)" This reverts commit 5661d9c. Let's go back to applying the schedulable masters patch when either SchedulableMastersForce or SchedulableMasters are set.
…e manifests (#4636) * MGMT-12435: Add a way to apply patches to core manifests Starting in 4.12 it's not possible to completely overwrite existing manifests, the way AI was doing it. Core manifests that need to be modified should be patched instead. This PR adds a logic to upload patches to the manifests api and then apply them. Note that the InfrastructureCR patching was not changed to us this new flow as this PR focuses only in adding this possibility and changing the SchedulableMasters flow. Future PRs will align the rest of the codebase. Signed-off-by: Flavio Percoco <[email protected]> * Defer delete of manifests dir in case of error Signed-off-by: Flavio Percoco <[email protected]> * Address review comments Signed-off-by: Flavio Percoco <[email protected]> * Revert "OCPBUGS-1482: Don't override schedulableMasters unnecessarily (#4414)" This reverts commit 5661d9c. Let's go back to applying the schedulable masters patch when either SchedulableMastersForce or SchedulableMasters are set. Signed-off-by: Flavio Percoco <[email protected]> Co-authored-by: Flavio Percoco <[email protected]>
…openshift#4414)" This reverts commit 5661d9c. Let's go back to applying the schedulable masters patch when either SchedulableMastersForce or SchedulableMasters are set.
…able masters (#4653) * MGMT-12435: Add a way to apply patches to core manifests Starting in 4.12 it's not possible to completely overwrite existing manifests, the way AI was doing it. Core manifests that need to be modified should be patched instead. This PR adds a logic to upload patches to the manifests api and then apply them. Note that the InfrastructureCR patching was not changed to us this new flow as this PR focuses only in adding this possibility and changing the SchedulableMasters flow. Future PRs will align the rest of the codebase. Signed-off-by: Flavio Percoco <[email protected]> * Defer delete of manifests dir in case of error Signed-off-by: Flavio Percoco <[email protected]> * Address review comments Signed-off-by: Flavio Percoco <[email protected]> * Revert "OCPBUGS-1482: Don't override schedulableMasters unnecessarily (#4414)" This reverts commit 5661d9c. Let's go back to applying the schedulable masters patch when either SchedulableMastersForce or SchedulableMasters are set. Signed-off-by: Flavio Percoco <[email protected]> Co-authored-by: Flavio Percoco <[email protected]>
When generating the Ignition files, the installer already sets schdulableMasters to true when there are no worker nodes (i.e. in the SNO and compact cluster topologies. (See
openshift/installer#2004) Therefore it is unnecessary to override it here (though it may be preferred to avoid a warning log from the installer).
Since openshift/installer#6247, attempting to override the schedulableMasters setting causes installation to fail, because there are two manifests of the same type and name that conflict.
Since we don't need to set this override when the installer would already do it, avoid doing so and triggering the error when the value is determined by the number of hosts rather than explicitly set by the user.
The conflict still needs to be resolved so that the user can enable schedulableMasters, but this at least allows the SNO and compact topologies to install OpenShift 4.12 again.
This partially reverts commit c45f369.
List all the issues related to this PR
https://issues.redhat.com/browse/OCPBUGS-1482
What environments does this code impact?
How was this code tested?
Checklist
docs, README, etc)Reviewers Checklist