-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.12.0, 4.11.z
-
None
-
Moderate
-
None
-
False
-
Description of problem:
this bug is from https://bugzilla.redhat.com/show_bug.cgi?id=2100860#c6
1. enable user workload monitoring,
# oc -n openshift-monitoring get cm cluster-monitoring-config -oyaml apiVersion: v1 data: config.yaml: | enableUserWorkload: true kind: ConfigMap metadata: creationTimestamp: "2022-09-27T03:33:52Z" name: cluster-monitoring-config namespace: openshift-monitoring resourceVersion: "68798" uid: be0a4004-b474-443a-a364-c0435d3f99c4
enable dedicated user workload monitoring Alertmanager
# oc -n openshift-user-workload-monitoring get cm user-workload-monitoring-config -oyaml apiVersion: v1 data: config.yaml: | alertmanager: enabled: true kind: ConfigMap metadata: creationTimestamp: "2022-09-27T03:33:06Z" name: user-workload-monitoring-config namespace: openshift-user-workload-monitoring resourceVersion: "68723" uid: ea7617a8-f712-478a-aade-c04ff827e45a
2. Deploy an application + service monitor + alerting rule which fires always, samples see the attached file
3. Go to the OCP developer console and silence the user project alert, user project alert could be silenced from developer console, but the user project alert status is still Firing, not Silenced in administrator console
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-09-26-111919
How reproducible:
always
Steps to Reproduce:
1. see the description 2. 3.
Actual results:
user project alert could be silenced from developer console, but the user project alert status is still Firing, not Silenced on administrator console
Expected results:
user project alert status is Silenced on administrator console
Additional info:
