Bug 1724341

Summary:	Access to the ES root url / from a project's pod on Openshift
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	agawand, anli, aos-bugs, aprajapa, hgomes, jcantril, rmeggins, sponnaga, vjaypurk
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The permissions between 3.10(es2.x) and 3.11(es5.x) were locked down so that non-admin users were unable to access the root endpoints Consequence: Non-admin users are unable to determine the es version by accessing the root endpoint Fix: Add permissions so everyone is able to see the es version Result: Access to the root endpoint is the same as from prior releases.	Story Points:	---
Clone Of:	1722959	Environment:
Last Closed:	2019-07-04 09:01:54 UTC	Type:	---
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:	1710868, 1722959
Bug Blocks:

Comment 2 Anping Li 2019-06-28 07:15:58 UTC

Using openshift/ose-logging-elasticsearch5:v4.1.4-201906271212, the user can fetch the elasticsearch status using /.

curl -s -k -o /dev/null -w "%{http_code}"  -H 'X-Forwarded-For: 127.0.0.1' -H "Authorization: Bearer oX9TWqgQ_c4pkCt7LLCjawPhJg-63GxjnDBBqQlCiFw" https://172.30.85.251:9200/
{
  "name" : "elasticsearch-cdm-ktsu8dd1-2",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "3RROtmBsQ8Wd6_YkNsCZhQ",
  "version" : {
    "number" : "5.6.13",
    "build_hash" : "921f2bd",
    "build_date" : "2018-11-16T16:58:29.974Z",
    "build_snapshot" : false,
    "lucene_version" : "6.6.1"
  },
  "tagline" : "You Know, for Search"
}

Comment 4 errata-xmlrpc 2019-07-04 09:01:54 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-2019:1635