Bug 1421563
| Summary: | [Intservice_public_324]kibana route unaccessible after logging deployment | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xia Zhao <xiazhao> | ||||||||||
| Component: | Installer | Assignee: | ewolinet | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Xia Zhao <xiazhao> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 3.5.0 | CC: | aos-bugs, ewolinet, jokerman, juzhao, mmccomas, pweil | ||||||||||
| 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:01:52 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: | |||||||||||||
| Bug Blocks: | 1420219 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Xia Zhao
2017-02-13 05:44:02 UTC
Created attachment 1249748 [details]
kibana_proxy container log
Created attachment 1249749 [details]
kibana container log
Created attachment 1249752 [details]
ansible full logs
This issue blocks about 60% tests which need to visit logging UI for checking result. Verified with the code in PR with branch https://github.com/ewolinetz/openshift-ansible/tree/logging_fix_kibana_routes, issue was fixed & kibana route accesible. Will set to verified once PR merged. Removing key word TestBlocker. Set to verified according to comment #8 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 |