Bug 1920898

Summary: [4.6.z]"500 Internal Error" for prometheus route in https_proxy cluster
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Damien Grisonnet <dgrisonn>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6.zCC: alegrand, anpicker, aos-bugs, dgrisonn, erooth, kakkoyun, kiyyappa, lcosic, mfojtik, pkrupa, surbania, wduan
Target Milestone: ---Keywords: Regression
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1920901 (view as bug list) Environment:
Last Closed: 2021-03-30 17:03:12 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:
Bug Depends On: 1926876    
Bug Blocks:    
Description Flags
prometheus UI none

Comment 6 Damien Grisonnet 2021-03-01 13:41:59 UTC
*** Bug 1933499 has been marked as a duplicate of this bug. ***

Comment 9 Junqi Zhao 2021-03-22 02:46:34 UTC
tested with 4.6.0-0.nightly-2021-03-21-131139 https_proxy cluster, can login prometheus route correctly, no issue
# oc -n openshift-monitoring get pod prometheus-k8s-0 -oyaml
    name: prometheus
    - mountPath: /etc/pki/ca-trust/extracted/pem/
      name: prometheus-trusted-ca-bundle
      readOnly: true
    name: prometheus-proxy
    - mountPath: /etc/pki/ca-trust/extracted/pem/
      name: prometheus-trusted-ca-bundle
      readOnly: true

Comment 10 Junqi Zhao 2021-03-22 02:47:21 UTC
Created attachment 1765120 [details]
prometheus UI

Comment 13 errata-xmlrpc 2021-03-30 17:03:12 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 (OpenShift Container Platform 4.6.23 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.