+++ This bug was initially created as a clone of Bug #1729297 +++ +++ This bug was initially created as a clone of Bug #1728856 +++ Description of problem: Updating to the latest version of the multi-tenant plugin blocks viewing by metrics unless you have cluster admin rights Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy logging 2. Set up an SA that can scrape metrics 3. curl -kv https://172.30.59.79/_prometheus/metrics -H"Authorization: Bearer $(oc serviceaccounts get-token metrics-test)" Actual results: 403 Expected results: 200 Additional info: https://github.com/openshift/origin-aggregated-logging/issues/1686
The sa prometheus-k8s can fetch metrics from es. sh-4.2# curl -k -H "Authorization: Bearer $token" -H "Content-type: application/json" https://172.30.119.95:60000/_prometheus/metrics # HELP es_index_segments_memory_bytes Memory used by segments # TYPE es_index_segments_memory_bytes gauge es_index_segments_memory_bytes{cluster="elasticsearch",type="points",index=".kibana",context="total",} 0.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="norms",index=".operations.2019.07.25",context="primaries",} 47552.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="indexwriter",index=".kibana",context="primaries",} 0.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="docvalues",index=".searchguard",context="primaries",} 636.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="termvectors",index=".kibana",context="total",} 0.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="versionmap",index=".operations.2019.07.25",context="total",} 63240.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="terms",index=".operations.2019.07.25",context="primaries",} 537727.0 es_index_segments_memory_bytes{cluster="elasticsearch",type="indexwriter",index=".kibana.647a750f1787408bf50088234ec0edd5a6a9b2ac
Also verified using registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.1.4-201906271212.
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:1866