Bug 1579127
| Summary: | [free-int]Prometheus should be upgraded | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Hawkular | Assignee: | Paul Gier <pgier> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.10.0 | CC: | aos-bugs, yufchang |
| Target Milestone: | --- | Keywords: | OnlineStarter, Reopened |
| Target Release: | 3.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-11 07:20:00 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: | |||
I upgraded prometheus in the free-int cluster, and it appears to be ok, however, there seems to be a problem with the router so I'm not able to verify that prometheus is working correctly. Please change to ON_QA, image version is v3.10 and prometheus works well
image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.10
image: registry.reg-aws.openshift.com:443/openshift3/prometheus:v3.10
image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alert-buffer:v3.10
image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alertmanager:v3.10
Looks like the router issue has been fixed, changing to ON_QA image tag should be upgraded to v3.11, it is still v3.10 image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.10 image: registry.reg-aws.openshift.com:443/openshift3/prometheus:v3.10 image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alert-buffer:v3.10 image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alertmanager:v3.10 env: OpenShift Master:v3.11.0-0.10.0 Kubernetes Master:v1.11.0+d4cacc0 OpenShift Web Console:v3.11.0-0.10.0 I've updated the images to v3.11. In the future, please create a new issue instead of reopening if the previous issue was already verified and closed. Thanks! Image tag is v3.11 now, and metrics works well image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.11 image: registry.reg-aws.openshift.com:443/openshift3/prometheus:v3.11 image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alert-buffer:v3.11 image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alertmanager:v3.11 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-2018:2652 |
Description of problem: free-int cluster, prometheus should be upgarded from v3.9 to v3.10, now its vesion is still v3.9 image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.9 imagePullPolicy: Always image: registry.reg-aws.openshift.com:443/openshift3/prometheus:v3.9 imagePullPolicy: Always image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.9 imagePullPolicy: Always image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alert-buffer:v3.9 imagePullPolicy: Always image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.9 imagePullPolicy: Always image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alertmanager:v3.9 imagePullPolicy: Always imagePullSecrets: - image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alert-buffer:v3.9 imageID: "" image: registry.reg-aws.openshift.com:443/openshift3/prometheus-alertmanager:v3.9 imageID: docker-pullable://registry.reg-aws.openshift.com:443/openshift3/prometheus-alertmanager@sha256:f569b040c2f2061978ae5eba3860b153da1275bfb56ad5fb0a0b96e11c9dad4e image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.9 imageID: docker-pullable://registry.reg-aws.openshift.com:443/openshift3/oauth-proxy@sha256:2b989870a5cd775827cc1fc2c12efea1ad3c4e0c226239b066e556b6b69def5b image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.9 imageID: docker-pullable://registry.reg-aws.openshift.com:443/openshift3/oauth-proxy@sha256:2b989870a5cd775827cc1fc2c12efea1ad3c4e0c226239b066e556b6b69def5b image: registry.reg-aws.openshift.com:443/openshift3/oauth-proxy:v3.9 imageID: docker-pullable://registry.reg-aws.openshift.com:443/openshift3/oauth-proxy@sha256:2b989870a5cd775827cc1fc2c12efea1ad3c4e0c226239b066e556b6b69def5b image: registry.reg-aws.openshift.com:443/openshift3/prometheus:v3.9 imageID: docker-pullable://registry.reg-aws.openshift.com:443/openshift3/prometheus@sha256:f2ce1d70f7b680ea0543d8d637e489643dc6a1d3767f7eab9d06d8852537eefa Version-Release number of selected component (if applicable): oc vesion oc v3.10.0-0.47.0 kubernetes v1.10.0+b81c8f8 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: Always Steps to Reproduce: 1. Check prometheus version in free-int cluster 2. 3. Actual results: prometheus version is still v3.9 Expected results: prometheus should be upgarded from v3.9 to v3.10 Additional info: