Hide Forgot
Created attachment 1514307 [details] kubelet targets are down Description of problem: This bug is cloned from https://jira.coreos.com/browse/MON-498 File it again for QE team to track the monitoring issue in Bugzilla. Deploy cluster monitoring on AWS with new installer kubelet targets are down in /targets UI, this cause some metrics can not be shown on grafana UI, see the attached grafana_pod_resouce.png Error in /targets UI x509:certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "root-ca") Version-Release number of selected component (if applicable): docker.io/grafana/grafana:5.2.4 docker.io/openshift/oauth-proxy:v1.1.0 docker.io/openshift/prometheus-alertmanager:v0.15.2 docker.io/openshift/prometheus-node-exporter:v0.16.0 docker.io/openshift/prometheus:v2.5.0 quay.io/coreos/configmap-reload:v0.0.1 quay.io/coreos/k8s-prometheus-adapter-amd64:v0.4.0 quay.io/coreos/kube-rbac-proxy:v0.4.0 quay.io/coreos/kube-state-metrics:v1.4.0 quay.io/coreos/prom-label-proxy:v0.1.0 quay.io/coreos/prometheus-config-reloader:v0.26.0 quay.io/coreos/prometheus-operator:v0.26.0 quay.io/openshift/origin-configmap-reload:v3.11 quay.io/openshift/origin-telemeter:v4.0 registry.svc.ci.openshift.org/openshift/origin-v4.0-2018-12-14-003614@sha256:4b96754e4e429971ff85304a54a4f354fa644cef0e14d3aca0f18bdaad1e45d2 How reproducible: Always Steps to Reproduce: 1. Deploy cluster monitoring on AWS with new installer and check targets on /targets page 2. 3. Actual results: kubelet targets are down Expected results: kubelet targets should be up Additional info:
*** Bug 1659361 has been marked as a duplicate of this bug. ***
Issue is fixed with docker.io/grafana/grafana:5.2.4 docker.io/openshift/oauth-proxy:v1.1.0 docker.io/openshift/prometheus-alertmanager:v0.15.2 docker.io/openshift/prometheus-node-exporter:v0.16.0 docker.io/openshift/prometheus:v2.5.0 quay.io/coreos/configmap-reload:v0.0.1 quay.io/coreos/k8s-prometheus-adapter-amd64:v0.4.1 quay.io/coreos/kube-rbac-proxy:v0.4.0 quay.io/coreos/kube-state-metrics:v1.4.0 quay.io/coreos/prometheus-config-reloader:v0.26.0 quay.io/coreos/prometheus-operator:v0.26.0 quay.io/openshift/origin-configmap-reload:v3.11 quay.io/openshift/origin-telemeter:v4.0 registry.svc.ci.openshift.org/openshift/origin-v4.0-2018-12-19-004812@sha256:9ea6b852e7cdf29529d1a8d56cde5eacd8f40e9d2b806d0984e24a4c27df5567
Created attachment 1515810 [details] kubelet targets are up
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:2820