MGMT-12471: Don't wait for console if it is disabled - #4594
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhernand 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 |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4594 +/- ##
==========================================
+ Coverage 66.95% 67.03% +0.08%
==========================================
Files 200 200
Lines 28436 28179 -257
==========================================
- Hits 19040 18891 -149
+ Misses 7662 7590 -72
+ Partials 1734 1698 -36
|
|
/test edge-e2e-metal-assisted |
fc21688 to
c708295
Compare
|
@avishayt @mkowalski the bot assigned you as reviewers, I'd appreciate your input. |
c708295 to
24b5d95
Compare
|
/test edge-e2e-metal-assisted |
|
Dear reviewers (@avishayt and @mkowalski) I need your input to move this forward. |
|
Looks good to me but would prefer another set of eyes. |
24b5d95 to
113675e
Compare
|
/hold I having an issue when testing this manually, will unhold when I understand/fix it. |
113675e to
a5ff743
Compare
a5ff743 to
f1590bd
Compare
|
@eranco74 @tsorya while testing this I realized that capabilities are supported since 4.11, but the console capability is only supported since 4.12. I changed the patch accordingly. While testing with 4.11 I also detected that there is a potential crash in the controller. I am trying to address it here: openshift/assisted-installer#589. I think this is ready for review again. |
|
/unhold |
|
/lgtm |
Currently the service keeps for each cluster a list of the operators that it will wait for before considering the cluster installed. This list includes the console operator. But since version 4.11 that can be disabled via the `capabilities` section of the installer configuration file. For example: ```yaml capabilities: baselineCapabilitySet: None additionalEnabledCapabilities: - baremetal ``` That will configure the cluster so that only the `baremetal` optional capability will be installed, which effectively disables the `Console` capability. This patch changes the service so that it removes the console operator from that list when this kind of update is made to the installer configuration. Related: https://issues.redhat.com/browse/MGMT-12471 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
f1590bd to
a76bedf
Compare
|
/lgtm |
|
/lgtm |
|
@jhernand: all tests passed! 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. |
This is a backport of MGMT-12471 for ACM 2.7. It contains the changes in pull request openshift#4594. Currently the service keeps for each cluster a list of the operators that it will wait for before considering the cluster installed. This list includes the console operator. But since version 4.11 that can be disabled via the `capabilities` section of the installer configuration file. For example: ```yaml capabilities: baselineCapabilitySet: None additionalEnabledCapabilities: - baremetal ``` That will configure the cluster so that only the `baremetal` optional capability will be installed, which effectively disables the `Console` capability. This patch changes the service so that it removes the console operator from that list when this kind of update is made to the installer configuration. Related: https://issues.redhat.com/browse/MGMT-13664 Related: https://issues.redhat.com/browse/MGMT-12471 Related: openshift#4594 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com> Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
This is a backport of MGMT-12471 for ACM 2.6. It includes the changes from pull request openshift#4594. Currently the service keeps for each cluster a list of the operators that it will wait for before considering the cluster installed. This list includes the console operator. But since version 4.11 that can be disabled via the `capabilities` section of the installer configuration file. For example: ```yaml capabilities: baselineCapabilitySet: None additionalEnabledCapabilities: - baremetal ``` That will configure the cluster so that only the `baremetal` optional capability will be installed, which effectively disables the `Console` capability. This patch changes the service so that it removes the console operator from that list when this kind of update is made to the installer configuration. Related: https://issues.redhat.com/browse/MGMT-13657 Related: https://issues.redhat.com/browse/MGMT-12471 Related: openshift#4594 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
This is a backport of MGMT-12471 for ACM 2.6. It includes the changes from pull request #4594. Currently the service keeps for each cluster a list of the operators that it will wait for before considering the cluster installed. This list includes the console operator. But since version 4.11 that can be disabled via the `capabilities` section of the installer configuration file. For example: ```yaml capabilities: baselineCapabilitySet: None additionalEnabledCapabilities: - baremetal ``` That will configure the cluster so that only the `baremetal` optional capability will be installed, which effectively disables the `Console` capability. This patch changes the service so that it removes the console operator from that list when this kind of update is made to the installer configuration. Related: https://issues.redhat.com/browse/MGMT-13657 Related: https://issues.redhat.com/browse/MGMT-12471 Related: #4594 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
This is a backport of MGMT-12471 for ACM 2.7. It contains the changes in pull request #4594. Currently the service keeps for each cluster a list of the operators that it will wait for before considering the cluster installed. This list includes the console operator. But since version 4.11 that can be disabled via the `capabilities` section of the installer configuration file. For example: ```yaml capabilities: baselineCapabilitySet: None additionalEnabledCapabilities: - baremetal ``` That will configure the cluster so that only the `baremetal` optional capability will be installed, which effectively disables the `Console` capability. This patch changes the service so that it removes the console operator from that list when this kind of update is made to the installer configuration. Related: https://issues.redhat.com/browse/MGMT-13664 Related: https://issues.redhat.com/browse/MGMT-12471 Related: #4594 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Tested manually creating a cluster with the console disabled and waiting for the installation to complete.
Checklist
docs, README, etc)Reviewers Checklist