Description of problem: The issue I wanted to report here is already identified and fixed on upstream. report : https://github.com/prometheus/prometheus/issues/3506 bug fix: https://github.com/prometheus/prometheus/pull/3508 However, RH's image(package) didn't contain the fix yet. (latest package) https://access.redhat.com/downloads/content/prometheus/2.0.0-1.git0a74f98.el7/x86_64/fd431d51/package Version-Release number of selected component (if applicable): - prometheus-2.0.0-1.git0a74f98.el7.x86_64.rpm Expected results: - We would like to requst to import the fix into RH's prometheus as soon as possible, as OpenShift customers use prometheus with NFS.
We're working on the upgrade to prometheus 2.1.0 which includes the fixes mentioned, so this should be resolved.
Thank you. That is great. We will keep tracking this BZ until the fix is released.
Upstream PRs for upgrading prometheus in examples and installer: https://github.com/openshift/origin/pull/18727 https://github.com/openshift/openshift-ansible/pull/7258
The master and 3.9 branches of openshift have been updated to prometheus 2.2.1.
Tested with prometheus/images/v3.9.22-1,prometheus version in 2.2.1 now in prometheus 3.9 image, and passed our sanity testing other images prometheus-alert-buffer/images/v3.9.22-1 prometheus-alertmanager/images/v3.9.22-1 oauth-proxy/images/v3.9.22-1 # openshift version openshift v3.9.22 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.16
(In reply to Junqi Zhao from comment #6) > Tested with prometheus/images/v3.9.22-1,prometheus version in 2.2.1 now in change to Tested with prometheus/images/v3.9.22-1,prometheus version is 2.2.1 now in