Bug 1425312
| Summary: | The redirect URL of Kibana route takes wrong port number when logging in Kibana | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Installer | Assignee: | ewolinet |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.5.0 | CC: | aos-bugs, jcantril, jokerman, juzhao, mmccomas, pweil, rmeggins, sudo |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-12 19:02:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1431935 | ||
| Bug Blocks: | |||
| Attachments: | |||
|
Description
Junqi Zhao
2017-02-21 07:39:33 UTC
Created attachment 1255997 [details]
master-config.yaml
Created attachment 1255998 [details]
fully ansible running log
From https://github.com/openshift/openshift-ansible/tree/master/roles/openshift_logging find the following message openshift_logging_master_public_url: The public facing URL for the Kubernetes master, this is used for Authentication redirection. Defaults to 'https://{{openshift.common.public_hostname}}:8443'. Maybe this defect is relate to it, ansible will always use default port 8443 as port number, it is not a variable. Verified with the latest openshift-ansible playbooks, ansible still use 8443 port instead of 443 port, although 'PLAY RECAP' showed the whole work failed, but all pods are generated successfully and kibana UI could be accessed if we change the port from 8443 to 443
Attached the fully ansilbe running log, Failed at 'Verify API Server' and it retried for 120 times, I think the retry number is too big, and from the message, it aslo used 8443 port
FAILED - RETRYING: HANDLER: openshift_logging : Verify API Server (120 retries left).Result was: {
"attempts": 1,
"changed": false,
"cmd": [
"curl",
"--silent",
"--tlsv1.2",
"--cacert",
"/etc/origin/master/ca-bundle.crt",
"https://ip-172-18-1-11.ec2.internal:8443/healthz/ready"
],
"delta": "0:00:00.010390",
"end": "2017-02-22 00:43:54.082867",
"failed": true,
"invocation": {
"module_args": {
"_raw_params": "curl --silent --tlsv1.2 --cacert /etc/origin/master/ca-bundle.crt https://ip-172-18-1-11.ec2.internal:8443/healthz/ready",
"_uses_shell": false,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"warn": false
},
"module_name": "command"
},
"rc": 7,
"retries": 121,
"start": "2017-02-22 00:43:54.072477",
"warnings": []
}
Created attachment 1256345 [details]
ansible log shows it still use 8443 port
Jason, Looking through the log there is some issue in the fact gathering where the api_url switches from: "api_port": "443", "api_url": "https://ip-172-18-1-11.ec2.internal", to: "api_port": "8443", "api_url": "https://ip-172-18-1-11.ec2.internal:8443", where the former is reported as the correct one. Thoughts? It's failed to upgrade from Logging 3.4.1 to 3.5.0, same reason as this defect, it wrongly used 8443 port instead of 443 port, and Kibana UI shows "Application is not available" error, see the snapshot Created attachment 1257159 [details]
"Application is not available" error in Kibana after upgrading logging from 3.4.1 to 3.5.0
I believe this was fixed in https://github.com/openshift/openshift-ansible/pull/3438/ Jeff, this bz was moved back to ASSIGNED but the openshift-ansible PR was merged - does that mean the openshift-ansible PR did not fix the problem? Rich, I'm trying to figure out why https://bugzilla.redhat.com/show_bug.cgi?id=1425312#c7 is happening still. @ewolinet, Verified with your fix, test passed, kibana can take the right port number now. Close this defect according to Comment 15 Tested on AWS, this issue was reproduced. Version-Release number of selected component: openshift-ansible-3.5.28-1.git.0.103513e.el7.noarch Note: openshift-ansible and playbooks are yum installed. according to your fix https://github.com/openshift/openshift-ansible/pull/3550 file 'roles/openshift_logging/meta/main.yaml' should be dependencies: - role: lib_openshift - role: openshift_master_facts but it still wrong in openshift-ansible-playbooks-3.5.28-1.git.0.103513e.el7.noarch dependencies: - role: lib_openshift - role: openshift_master_facts - role: openshift_facts (In reply to Junqi Zhao from comment #18) > file 'roles/openshift_logging/meta/main.yaml' > should be > > dependencies: > - role: lib_openshift > - role: openshift_facts > but it still wrong in > openshift-ansible-playbooks-3.5.28-1.git.0.103513e.el7.noarch > dependencies: > - role: lib_openshift > - role: openshift_master_facts > - role: openshift_facts additional changes merged into openshift-ansible-3.5.31, ON_QA blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1431935, will verify it after BZ # 1431935 get fixed. The reference issue only appears to block because it has an invalid value. Please update the 'openshift_logging_es_pvc_pool' to contain a number followed by a letter (e.g 1G, 1m) Verified according to the fix of https://bugzilla.redhat.com/show_bug.cgi?id=1431935, this issue is fixed. I did not set openshift_logging_es_pvc_pool in inventory file, and we don't have such parameter in https://github.com/openshift/openshift-ansible/tree/release-1.5/roles/openshift_logging attached the inventory file Created attachment 1263166 [details]
ansible inventory file, not set openshift_logging_es_pvc_pool
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0903 Problem was that OAP_PUBLIC_MASTER_URL for the Kibana deployment config was wrong. |