Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1525269

Summary: View archive link broken
Product: OpenShift Container Platform Reporter: Bob Kozdemba <bkozdemb>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.7.1CC: aos-bugs, bkozdemb, juzhao, rmeggins
Target Milestone: ---   
Target Release: 3.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-05 09:34:33 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: 1525815    
Bug Blocks:    
Attachments:
Description Flags
KibanaWarning
none
"view archive" link works well none

Description Bob Kozdemba 2017-12-12 22:48:23 UTC
Created attachment 1366988 [details]
KibanaWarning

Description of problem:
After selecting the "View Archive" link from the OCP console, the Kibana UI displays the following warning:
No default index pattern. You must select or create one to continue. 

Version-Release number of selected component (if applicable):
v3.7.9

How reproducible:
100%

Steps to Reproduce:
1. Install OCP w/logging
2. Login as a non-admin user, create a project and an application
3. Visit the "pod" dognut -> logs -> view archive

Actual results:

The following warning is displayed:

No default index pattern. You must select or create one to continue.

See attached screen shot.

Expected results:
Kibana page should display graph of application hits.

Additional info:
Logs at http://people.redhat.com/bkozdemb/efk-logs/

Comment 1 Rich Megginson 2017-12-12 23:20:22 UTC
The problem is that the openshift UI View Archive link wants to use the index name of "project.$name.$uuid.*" and this doesn't exist at the moment.  This could be a duplicate or related to https://bugzilla.redhat.com/show_bug.cgi?id=1523047 and https://bugzilla.redhat.com/show_bug.cgi?id=1519814

Comment 2 Jeff Cantrill 2017-12-13 14:54:40 UTC
Are you able to provide the full version of 3.7 you are running.  This could also be related to a recent security issue that introduced another bug that has since been resolved.

Comment 6 Jeff Cantrill 2017-12-13 19:28:26 UTC
This is an old version of the plugin that had a bug:

$ oc exec -c elasticsearch logging-es-data-master-juywb5oh-2-wndbk -- rpm -qva | grep elastic
elasticsearch-2.4.4-1.el7.noarch
openshift-elasticsearch-plugin-2.4.4.17__redhat_1-2.el7.noarch
elasticsearch-cloud-kubernetes-2.4.4.01_redhat_1-1.el7.noarch

and is resolved by:

openshift-elasticsearch-plugin-2.4.4.17__redhat_1-3.el7.noarch.rpm      

This will be resolved by logging-elasticsearch-docker-3.7.9-18 or better.

Comment 7 Junqi Zhao 2017-12-14 06:04:32 UTC
"View Archive" link is missing from OCP web console, see 
https://bugzilla.redhat.com/show_bug.cgi?id=1525815

Will verify this defect after BZ # 1525815 is fixed

But we can check logs by login from kibana route, user can see the project logs in kibana.
logging images version v3.7.14-5
#  oc exec -c elasticsearch logging-es-ops-data-master-de3pu7cg-1-prqxg -- rpm -qva | grep elastic
elasticsearch-2.4.4-1.el7.noarch
openshift-elasticsearch-plugin-2.4.4.17__redhat_1-3.el7.noarch
elasticsearch-cloud-kubernetes-2.4.4.01_redhat_1-1.el7.noarch

Comment 8 Jeff Cantrill 2017-12-14 13:53:11 UTC
#c7 is unrelated to this issue.

Comment 9 Junqi Zhao 2017-12-15 01:51:21 UTC
Tested with logging images version v3.7.14-5
"View Archive" link works well and can navigate to Kibana UI to show the pod logs.

See the attached picture.

Comment 10 Junqi Zhao 2017-12-15 01:51:49 UTC
Created attachment 1368223 [details]
"view archive" link works well

Comment 14 errata-xmlrpc 2018-04-05 09:34:33 UTC
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-2018:0636