Bug 1935585 - prometheus liveness probes cause issues while replaying WAL
Summary: prometheus liveness probes cause issues while replaying WAL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.7.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1935582
Blocks: 1935586
TreeView+ depends on / blocked
 
Reported: 2021-03-05 08:35 UTC by Sergiusz Urbaniak
Modified: 2021-03-16 08:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1935582
: 1935586 (view as bug list)
Environment:
Last Closed: 2021-03-16 08:42:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:0749 0 None None None 2021-03-16 08:43:10 UTC

Comment 3 Junqi Zhao 2021-03-08 02:25:39 UTC 
openshift 4.7 uses prometheus-operator 0.44.1 now
# oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-03-06-183610   True        False         134m    Cluster version is 4.7.0-0.nightly-2021-03-06-183610

# oc -n openshift-monitoring logs prometheus-operator-8554b7698-4lpwj -c prometheus-operator
level=info ts=2021-03-08T00:12:12.809115041Z caller=main.go:235 msg="Starting Prometheus Operator" version="(version=0.44.1, branch=rhaos-4.7-rhel-8, revision=be8918a)"
Comment 6 errata-xmlrpc 2021-03-16 08:42:49 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 (OpenShift Container Platform 4.7.2 bug fix 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/RHBA-2021:0749
Note You need to log in before you can comment on or make changes to this bug.