Bug 1655841
| Summary: | telemeter-client pod is not created | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Monitoring | Assignee: | lserven |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.1.0 | CC: | fbranczy, vrutkovs |
| Target Milestone: | --- | Keywords: | Regression, TestBlocker |
| 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:41:04 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: | |||
|
Description
Junqi Zhao
2018-12-04 04:19:52 UTC
Blocks telemeter testing Issue is fixed, could see telemeter-client pod now $ oc get pod -n openshift-monitoring | grep telemeter-client telemeter-client-747b776f55-pffrs 3/3 Running 0 2h images quay.io/openshift/origin-telemeter:v4.0 quay.io/openshift/origin-configmap-reload:v3.11 quay.io/coreos/kube-rbac-proxy:v0.4.0 Issue is reproduced again. re-open it. # oc -n openshift-monitoring get deployment | grep telemeter-client nothing returned and the following resources are not created. # oc -n openshift-monitoring get pod | grep telemeter-client # oc -n openshift-monitoring get configmap | grep telemeter-client-serving-certs-ca-bundle # oc -n openshift-monitoring get secret | grep telemeter-client # oc -n openshift-monitoring get ServiceMonitor | grep telemeter-client # oc -n openshift-monitoring get service | grep telemeter-client images used 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 docker.io/openshift/prometheus:v2.5.0 quay.io/coreos/configmap-reload:v0.0.1 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.25.0 quay.io/coreos/prometheus-operator:v0.25.0 quay.io/openshift/origin-cluster-monitoring-operator:v4.0 @Junqi I believe you closed this on Jira today. Can we close this here? Issue is fixed with # oc get clusterversion version -oyaml | grep payload payload: quay.io/openshift-release-dev/ocp-release@sha256:66cee7428ba0d3cb983bd2a437e576b2289e7fd5abafa70256200a5408b26644 cluster-monitoring-operator pod images: image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7b88121a3c893297c1be75261bae142b6312227c72bc72a0a64c68363a96601f $oc -n openshift-monitoring get pod | grep telemeter-client telemeter-client-69478fc49f-z88h2 3/3 Running 0 2h $oc -n openshift-monitoring get configmap | grep telemeter-client-serving-certs-ca-bundle telemeter-client-serving-certs-ca-bundle 1 2h $oc -n openshift-monitoring get secret | grep telemeter-client telemeter-client Opaque 6 2h telemeter-client-dockercfg-h65st kubernetes.io/dockercfg 1 2h telemeter-client-tls kubernetes.io/tls 2 2h telemeter-client-token-jj7jv kubernetes.io/service-account-token 3 2h telemeter-client-token-n7vtw kubernetes.io/service-account-token 3 2h $oc -n openshift-monitoring get ServiceMonitor | grep telemeter-client telemeter-client 2h $oc -n openshift-monitoring get service | grep telemeter-client telemeter-client ClusterIP None <none> 8443/TCP 2h 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 |