MGMT-13941: Don't wait for console if disabled - #5022
Conversation
|
@jhernand: This pull request references Jira Issue OCPBUGS-8335, 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. |
|
@tsorya please review. |
|
[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 |
There was a problem hiding this comment.
Just in matter of running less code though it can be less readable.
if isConsoleMonitored && !b.clusterApi.IsOperatorAvailable(&cluster, operators.OperatorConsole.Name)
There was a problem hiding this comment.
I think it is actually a little bit wrong. In case we don't have console why we need to run this logic?
This code returns
&models.Credentials{ Username: DefaultUser, Password: string(password), ConsoleURL: common.GetConsoleUrl(cluster.Name, cluster.BaseDNSDomain), }
and console url is part of it but console is not enabled so what those creds should be used for?
I am not sure we need this part in case there is no console
There was a problem hiding this comment.
The password is used to create the "kubeadmincreds" secret. The console URL is returned by the API and I assume it is used by the UI. I don't see it used in any other place in this project.
I am updating the code so that the ConsoleURL field is only populated when the console is enabled. Please check again.
29fc87e to
4c783e4
Compare
|
Seems cool, any option to add test for it? |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5022 +/- ##
==========================================
+ Coverage 67.31% 70.98% +3.66%
==========================================
Files 204 214 +10
Lines 30830 34835 +4005
==========================================
+ Hits 20754 24728 +3974
+ Misses 8238 8214 -24
- Partials 1838 1893 +55
|
4c783e4 to
911061c
Compare
Currently the cluster deployment controller waits for the console to be available before marking the cluster deployment as completed. This fails when the console capability is disabled. To avoid that this patch changes the controller so that it doesn't wait when the console is disabled. Related: https://issues.redhat.com/browse/OCPBUGS-8335 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
911061c to
94abbc1
Compare
Added two tests to verify the new behavior. |
|
@tsorya in the latest version of the patch I added two tests to verify the new behavior. Does that look good? |
|
/lgtm |
|
@jhernand: An error was encountered searching for bug MGMT-13941 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 401:
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
|
@jhernand: The referenced Jira(s) [MGMT-13941] could not be located, all automatically applied jira labels will be removed. 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. |
|
@jhernand: This pull request references MGMT-13941 which is a valid jira issue. 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 |
1 similar comment
|
/test e2e-agent-compact |
Currently the cluster deployment controller waits for the console to be available before marking the cluster deployment as completed. This fails when the console capability is disabled. To avoid that this patch changes the controller so that it doesn't wait when the console is disabled. Note that this is a clone of MGMT-13941 (which in turn is a clone of OCPBUGS-8335) for ACM 2.7. Related: https://issues.redhat.com/browse/OCPBUGS-8335 Related: https://issues.redhat.com/browse/MGMT-13941 Related: openshift#5022 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
|
/hold Revision 94abbc1 was retested 3 times: holding |
|
/override ci/prow/e2e-agent-compact |
|
@jhernand: Overrode contexts on behalf of jhernand: ci/prow/e2e-agent-compact 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. |
|
/unhold |
|
@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. |
Currently the cluster deployment controller waits for the console to be available before marking the cluster deployment as completed. This fails when the console capability is disabled. To avoid that this patch changes the controller so that it doesn't wait when the console is disabled. Note that this is a clone of MGMT-13941 (which in turn is a clone of OCPBUGS-8335) for ACM 2.7. Related: https://issues.redhat.com/browse/OCPBUGS-8335 Related: https://issues.redhat.com/browse/MGMT-13941 Related: #5022 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
Currently the cluster deployment controller waits for the console to be available before marking the cluster deployment as completed. This fails when the console capability is disabled. To avoid that this patch changes the controller so that it doesn't wait when the console is disabled. Note that this is a clone of MGMT-14096 (which in turn is a clone of OCPBUGS-8335) for ACM 2.6. Related: https://issues.redhat.com/browse/OCPBUGS-8335 Related: https://issues.redhat.com/browse/MGMT-14096 Related: openshift#5022 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
Currently the cluster deployment controller waits for the console to be available before marking the cluster deployment as completed. This fails when the console capability is disabled. To avoid that this patch changes the controller so that it doesn't wait when the console is disabled. Note that this is a clone of MGMT-14096 (which in turn is a clone of OCPBUGS-8335) for ACM 2.6. Related: https://issues.redhat.com/browse/OCPBUGS-8335 Related: https://issues.redhat.com/browse/MGMT-14096 Related: #5022 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
Currently the cluster deployment controller waits for the console to be available before marking the cluster deployment as completed. This fails when the console capability is disabled. To avoid that this patch changes the controller so that it doesn't wait when the console is disabled.
Related: https://issues.redhat.com/browse/OCPBUGS-8335
Related: https://issues.redhat.com/browse/MGMT-13941
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs, README, etc)Reviewers Checklist