-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.13.0, 4.12.z, 4.11.z, 4.10.z
-
-
-
Low
-
No
-
MON Sprint 234
-
1
-
False
-
This is a clone of issue OCPBUGS-10690. The following is the description of the original issue:
—
Description of problem:
according to PR: https://github.com/openshift/cluster-monitoring-operator/pull/1824, startupProbe for UWM prometheus/platform prometheus should be 1 hour, but startupProbe for UWM prometheus is still 15m after enabled UWM, platform promethues does not have issue, startupProbe is increased to 1 hour
$ oc -n openshift-user-workload-monitoring get pod prometheus-user-workload-0 -oyaml | grep startupProbe -A20
startupProbe:
exec:
command:
- sh
- -c
- if [ -x "$(command -v curl)" ]; then exec curl --fail http://localhost:9090/-/ready;
elif [ -x "$(command -v wget)" ]; then exec wget -q -O /dev/null http://localhost:9090/-/ready;
else exit 1; fi
failureThreshold: 60
periodSeconds: 15
successThreshold: 1
timeoutSeconds: 3
...
$ oc -n openshift-monitoring get pod prometheus-k8s-0 -oyaml | grep startupProbe -A20
startupProbe:
exec:
command:
- sh
- -c
- if [ -x "$(command -v curl)" ]; then exec curl --fail http://localhost:9090/-/ready;
elif [ -x "$(command -v wget)" ]; then exec wget -q -O /dev/null http://localhost:9090/-/ready;
else exit 1; fi
failureThreshold: 240
periodSeconds: 15
successThreshold: 1
timeoutSeconds: 3
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-03-19-052243
How reproducible:
always
Steps to Reproduce:
1. enable UWM, check startupProbe for UWM prometheus/platform prometheus 2. 3.
Actual results:
startupProbe for UWM prometheus is still 15m
Expected results:
startupProbe for UWM prometheus should be 1 hour
Additional info:
since startupProbe for platform prometheus is increased to 1 hour, and no similar bug for UWM prometheus, won't fix the issue is OK.
- blocks
-
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
