Bug 1674346
| Summary: | 403 error for grafana/prometheus route | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||||||
| Component: | Monitoring | Assignee: | Frederic Branczyk <fbranczy> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 4.1.0 | CC: | juzhao, mloibl, surbania | ||||||||
| Target Milestone: | --- | Keywords: | Regression | ||||||||
| Target Release: | 4.1.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-06-04 10:42:43 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Junqi Zhao
2019-02-11 04:32:50 UTC
There is not such issue for prometheus and alertmanager routes grafana UI could be accessed now, see attached picture $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-12-005016 True False 1h Cluster version is 4.0.0-0.nightly-2019-02-12-005016 Images: NAME PULL SPEC cluster-monitoring-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:51c040a9e285083d1f31083ac48479edce1552e53ff2bb8b3f91c62718b99fb2 grafana quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:788cb9461d4b38c4a8ef5cdac7cbdf46befea56c20f310ec4bf0c127428b908e k8s-prometheus-adapter quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:2986bc4db9ea270dc77aa1d896e3f76c98dc7bf90f1b4217e8c577a5aa6c1447 kube-rbac-proxy quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ee82c2882ccddc2605dc92f35b3cc2b2fb5ef76e4b5a5abd9c246b9a0f988d9b kube-state-metrics quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ed6b9bea8c80d114b4adbaf27c2dd08f1d04957d0c6aa5afb22830616a7d2642 oauth-proxy quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:59aa49bd4992ea5a792eb178a4de32743040ff12299e507f669a241b0a0f6ae4 prom-label-proxy quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:2cc3449b501b7a769cb5e60759a59bc57bcc46f03ad75875ac3efa59bb98782e prometheus quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ab4c12ab38d078ed4c9f98a72e7ec4e20c3230d2606dbcd31f5bdf41626b7c35 prometheus-alertmanager quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9d545f54ba476d1efe9c3209f0aec5b39c83e4098c2c8a44694301ce0d029d24 prometheus-config-reloader quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:58f065cb228dce82a21224df06062c99332972a2129ad6b40f778f840d469f84 prometheus-node-exporter quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9fb8fbb8e955e8b3e2174e32063e40fc6762afd02c5c63b117ffcbd8cca10812 prometheus-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b3a6a9b30150beae1235ea52e45dc302883bda35213b204aeab98165216ad8f9 telemeter quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7c736368f8135cafa3f806c8953edf6d4e33dac13a3de5ba413b37067b41af54 Created attachment 1533990 [details]
grafana UI could be accessed
> grafana UI could be accessed now, see attached picture
Thereby this bug is resolved?
I am not aware of any bug-fixes on our side that would relate to this.
yes,grafana UI could be accessed, not sure what is the cause re-open it, 403 error for grafana/prometheus route, alertmanager route works well $ oc version oc v4.0.0-0.171.0 kubernetes v1.12.4+a532756e37 features: Basic-Auth GSSAPI Kerberos SPNEGO $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-14-160606 True False 3h36m Cluster version is 4.0.0-0.nightly-2019-02-14-160606 Created attachment 1535042 [details]
403 error for prometheus route
errors maybe related to oauth-proxy # oc -n openshift-monitoring logs prometheus-k8s-0 -c prometheus-proxy 2019/02/15 03:21:14 oauthproxy.go:764: 10.128.2.11:33376 invalid Authorization header Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJvcGVuc2hpZnQtbW9uaXRvcmluZyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJ0ZWxlbWV0ZXItY2xpZW50LXRva2VuLWcydGN2Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6InRlbGVtZXRlci1jbGllbnQiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiI2NGJlYjQ2NC0zMGM1LTExZTktOTBmZS0wYWQ4ODUwMmMwZTAiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6b3BlbnNoaWZ0LW1vbml0b3Jpbmc6dGVsZW1ldGVyLWNsaWVudCJ9.cqOleEo5LcMqQwULcJmAIql-pulA4Ntm3_0FZwaufZniUphgQpjg6aBxEBa33AX9f2b8l5tIN4zjh3kBVMxFJ5nHEgRu6T9zQuDToRZdDgcHkUsgJjwsliWvznQfIfq8v1-40ca0azLkNZ3Wc4hn72JMKzh-P0aNYYSpJFEntJZCKdV4DDGHFf2IWpZOcET2vYZpjBoMu4FetqufnTs9dqA2ec2xO6KZzgNmxcsRVVd3PAGj0wwe5GT00YAVPKK_qvkpV-hjPpPrNxpuynLw2JLL0kheB6TjvQwp4-ZzqA-Bd44ZYJNDxGnbOvRSEJxsdvZA9Uhpga89VPO7K2x7qA grafana and prometheus routes could be accessed with # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-17-182259 True False 3h17m Cluster version is 4.0.0-0.nightly-2019-02-17-182259 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:0758 |