Details
-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.12.0, 4.11.z
-
None
-
False
-
Description
Description of problem:
this is the issue of following up for OCPBUGS-1790, forgot to file bug then
NOTE: but the user project alert status is still Firing, not Silenced in administrator console, will file a 4.11 bug after the code for this bug is merged to 4.11 payload
enable UWM and dedicated UWM Alertmanager
1. enable UWM
apiVersion: v1 kind: ConfigMap metadata: name: cluster-monitoring-config namespace: openshift-monitoring data: config.yaml: | enableUserWorkload: true
2. edit openshift-user-workload-monitoring/user-workload-monitoring-config configmap to enable dedicated UWM Alertmanager
apiVersion: v1
kind: ConfigMap
metadata:
name: user-workload-monitoring-config
namespace: openshift-user-workload-monitoring
data:
config.yaml: |
alertmanager:
enabled: true
should see alertmanager pod under openshift-user-workload-monitoring
$ oc -n openshift-user-workload-monitoring get pod
NAME READY STATUS RESTARTS AGE
alertmanager-user-workload-0 6/6 Running 0 2m35s
alertmanager-user-workload-1 6/6 Running 0 2m35s
prometheus-operator-78774d88c8-l2jxh 2/2 Running 0 38m
prometheus-user-workload-0 6/6 Running 0 38m
prometheus-user-workload-1 6/6 Running 0 38m
thanos-ruler-user-workload-0 3/3 Running 0 2m33s
thanos-ruler-user-workload-1 3/3 Running 0 2m37s
Deploy an application + service monitor + alerting rule which fires always, example see the attached file prometheus-example-app.yaml, then go to the OCP dev console and silence the alert. in this example, user project alert TestAlert is silenced on dev console, but still Firing on admin console
Version-Release number of selected component (if applicable):
4.11.0-0.nightly-2022-12-26-210225
How reproducible:
always
Steps to Reproduce:
1. see the descriptions 2. 3.
Actual results:
user project alert TestAlert is silenced on dev console, but still Firing on admin console
Expected results:
should be silenced on admin console too
Additional info:
