Bug 1480988
| Summary: | View archive link for ops projects does not take to kibana-ops | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ruben Romero Montes <rromerom> | ||||||
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5.1 | CC: | anli, aos-bugs, jcantril, jliggitt, juzhao, pportant, rmeggins, sdodson, spadgett | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.6.z | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause: There was no configuration to distinguish which Kibana instance to use.
Consequence: User's were always routed to the same instance
Fix: Add an annotation to the operations namespace which has the kibana hostname
Result: User's are routed to the Kibana instance specified in the annotation if it exists on the project.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-10-25 13:04:36 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ruben Romero Montes
2017-08-13 11:10:11 UTC
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/bac757fc0e920768bf9a08924c77468cfe113e82 bug 1480988. Use project annotation to determine kibana url for ops namespaces Jeff Do the fixes are in elasticsearch-cloud-kubernetes-2.4.4.01_redhat_1-1.el7 and openshift-elasticsearch-plugin-2.4.4.13__redhat_1-1.el7 Created attachment 1326267 [details]
ops ui, no search result
Created attachment 1326268 [details]
logging 3.5 kibana-ops UI
ops projects take to kibana-ops UI now, but there is no search result Take default project pod "docker-registry-1-w24p1" for example Clicked the "View archive" link from web console, and browser navigated to kibana-ops UI. info was "Discover:"project.default.9479f0f2-9821-11e7-926c-fa163e21c504.* is not a configured pattern. Using the default index pattern: *.all"". After a while this info disappeared, and "No results found" shown in page, see the attached picture "ops ui, no search result". I think the root cause is there are not Available Fields under .all index. see the attached "logging 3.5 kibana-ops UI", logging 3.5 kibana-ops UI has Available Fields under .all index. The fact you dont see results is a separate issue from this which was you are not getting to the ops instance of Kibana. In regards to #13, that may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1473153 Wrong bug reference in #c14 @Scott, Is atomic-openshift-3.6 package ready? It needs atomic-openshift-3.6 package to fix this defect. It redirect to ops kibana with atomic-openshift-master-3.6.173.0.49. So move to verified. Note: The ops-kibana print the following warning message. that is as expected. Discover: "project.default.2e270631-ad78-11e7-8dba-fa163e8efe63.*" is not a configured pattern. Using the default index pattern: ".operations.*" 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:3049 |