Bug 1421563 - [Intservice_public_324]kibana route unaccessible after logging deployment
Summary: [Intservice_public_324]kibana route unaccessible after logging deployment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: ewolinet
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks: 1420219
TreeView+ depends on / blocked
 
Reported: 2017-02-13 05:44 UTC by Xia Zhao
Modified: 2017-07-24 14:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-04-12 19:01:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ES log (16.01 KB, text/plain)
2017-02-13 05:44 UTC, Xia Zhao
no flags Details
kibana_proxy container log (577 bytes, text/plain)
2017-02-13 05:45 UTC, Xia Zhao
no flags Details
kibana container log (3.92 KB, text/plain)
2017-02-13 05:45 UTC, Xia Zhao
no flags Details
ansible full logs (918.95 KB, text/plain)
2017-02-13 06:15 UTC, Xia Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0903 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-04-12 22:45:42 UTC

Description Xia Zhao 2017-02-13 05:44:02 UTC
Created attachment 1249747 [details]
ES log

Description of problem:
Deploy logging 3.5.0 stacks with ansible scripts. After EFK pods are all running, when ES is in green status, kibana route not accesible with error 

"Server not found

Firefox can't find the server at {{openshift.common.public_hostname}}."

The redirect URL after visiting the kibana route is:

https://{{openshift.common.public_hostname}}:8443/oauth/authorize?response_type=code&redirect_uri=https%3A%2F%2Fkibana.${sub-domain}%2Fauth%2Fopenshift%2Fcallback&scope=user%3Ainfo%20user%3Acheck-access%20user%3Alist-projects&client_id=kibana-proxy

Version-Release number of selected component (if applicable):
The latest ansible scripts in https://github.com/openshift/openshift-ansible

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging 3.5.0 stacks with ansible

The inventory file:
[oo_first_master]
$master ansible_user=root ansible_ssh_user=root ansible_ssh_private_key_file="~/libra.pem" openshift_public_hostname=$master

[oo_first_master:vars]
deployment_type=openshift-enterprise
openshift_release=v3.5.0
openshift_logging_install_logging=true

openshift_logging_kibana_hostname=kibana.$subdomain
openshift_logging_kibana_ops_hostname=kibana-ops.$subdomain
public_master_url=https://$master:8443

openshift_logging_image_prefix=$registry/openshift3/
openshift_logging_image_version=3.5.0

openshift_logging_namespace=logging
openshift_logging_fluentd_use_journal=true

2.Wait until EFK pods are all running, and ES in green status
3.Visit the kibana route

Actual results:
kibana route unaccessible

Expected results:
kibana route should be accessible

Additional info:
Ansible execution log attached
Elasticsearch & kibana container logs attached

Comment 1 Xia Zhao 2017-02-13 05:45:25 UTC
Created attachment 1249748 [details]
kibana_proxy container log

Comment 2 Xia Zhao 2017-02-13 05:45:48 UTC
Created attachment 1249749 [details]
kibana container log

Comment 3 Xia Zhao 2017-02-13 06:15:26 UTC
Created attachment 1249752 [details]
ansible full logs

Comment 4 Xia Zhao 2017-02-15 03:26:56 UTC
This issue blocks about 60% tests which need to visit logging UI for checking result.

Comment 8 Xia Zhao 2017-02-16 03:23:43 UTC
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.

Comment 10 Xia Zhao 2017-02-20 05:08:45 UTC
Set to verified according to comment #8

Comment 12 errata-xmlrpc 2017-04-12 19:01:52 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-2017:0903


Note You need to log in before you can comment on or make changes to this bug.