Bug 2067062 - should update prometheus-operator resources version
Summary: should update prometheus-operator resources version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.11
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.11.0
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-23 07:23 UTC by Junqi Zhao
Modified: 2022-08-10 10:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:55:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1609 0 None open Bug 2067062: [bot] Automated dependencies version update 2022-03-23 09:46:57 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:56:28 UTC

Description Junqi Zhao 2022-03-23 07:23:05 UTC
Description of problem:
Prometheus Operator version now is 0.55.0, but the the related resouces version is still 0.54.1, we can fix it after we make the final decision on which prometheus-operator version would be used for 4.11

# oc -n openshift-monitoring get pod | grep prometheus-operator
prometheus-operator-5cb86ff95c-j8tn7           2/2     Running   0               7h58m

# oc -n openshift-monitoring get pod prometheus-operator-5cb86ff95c-j8tn7 --show-labels
NAME                                   READY   STATUS    RESTARTS   AGE   LABELS
prometheus-operator-5cb86ff95c-j8tn7   2/2     Running   0          8h    app.kubernetes.io/component=controller,app.kubernetes.io/managed-by=cluster-monitoring-operator,app.kubernetes.io/name=prometheus-operator,app.kubernetes.io/part-of=openshift-monitoring,app.kubernetes.io/version=0.54.1,pod-template-hash=5cb86ff95c

# oc -n openshift-monitoring logs -c prometheus-operator prometheus-operator-5cb86ff95c-j8tn7
level=info ts=2022-03-22T23:17:35.603944618Z caller=main.go:220 msg="Starting Prometheus Operator" version="(version=0.55.0, branch=rhaos-4.11-rhel-8, revision=5d799b9)"
..

# oc -n openshift-monitoring get deploy prometheus-operator -oyaml | head -n 50
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: "2022-03-22T23:17:21Z"
  generation: 1
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/managed-by: cluster-monitoring-operator
    app.kubernetes.io/name: prometheus-operator
    app.kubernetes.io/part-of: openshift-monitoring
    app.kubernetes.io/version: 0.54.1
  name: prometheus-operator
  namespace: openshift-monitoring
  resourceVersion: "8406"
  uid: 1c846924-813b-45d1-bea8-0afe2a63fe21
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app.kubernetes.io/component: controller
      app.kubernetes.io/name: prometheus-operator
      app.kubernetes.io/part-of: openshift-monitoring
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      annotations:
        kubectl.kubernetes.io/default-container: prometheus-operator
        target.workload.openshift.io/management: '{"effect": "PreferredDuringScheduling"}'
      creationTimestamp: null
      labels:
        app.kubernetes.io/component: controller
        app.kubernetes.io/managed-by: cluster-monitoring-operator
        app.kubernetes.io/name: prometheus-operator
        app.kubernetes.io/part-of: openshift-monitoring
        app.kubernetes.io/version: 0.54.1


Version-Release number of selected component (if applicable):
4.11.0-0.nightly-2022-03-20-160505

How reproducible:
always

Steps to Reproduce:
1. see the steps
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Junqi Zhao 2022-03-30 07:35:40 UTC
checked with 4.11.0-0.nightly-2022-03-29-152521, prometheus-operator resources version under openshift-monitoring/openshift-user-workload-monitoring are updated to 0.55.0

Comment 8 errata-xmlrpc 2022-08-10 10:55:33 UTC
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069


Note You need to log in before you can comment on or make changes to this bug.