Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1579127 - [free-int]Prometheus should be upgraded
[free-int]Prometheus should be upgraded
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular (Show other bugs)
3.10.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: Paul Gier
Junqi Zhao
: OnlineStarter, Reopened
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2018-05-16 23:06 EDT by Junqi Zhao
Modified: 2018-10-11 03:20 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:20:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:20 EDT

  None (edit)
Description Junqi Zhao 2018-05-16 23:06:19 EDT 
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:
Comment 1 Paul Gier 2018-05-17 18:23:56 EDT 
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.
Comment 2 Junqi Zhao 2018-05-18 04:53:35 EDT 
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
Comment 3 Paul Gier 2018-05-18 11:07:40 EDT 
Looks like the router issue has been fixed, changing to ON_QA
Comment 4 Junqi Zhao 2018-05-21 20:07:30 EDT 
Set it to VERIFIED as per Comment 2
Comment 5 Junqi Zhao 2018-08-07 04:56:09 EDT 
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
Comment 6 Paul Gier 2018-08-07 15:40:49 EDT 
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!
Comment 7 Junqi Zhao 2018-08-08 21:05:10 EDT 
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
Comment 9 errata-xmlrpc 2018-10-11 03:20:00 EDT 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.