-
Bug
-
Resolution: Unresolved
-
Normal
-
openshift-4.19
-
None
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
NEW
-
NEW
-
-
-
Sprint 270
-
Moderate
Env:
- OCP4.19 without monitoring-console-plugin changes with PF-6 yet
- Log into ocp
- Install ACM and configure it
- Install COO1.1 and add monitoring uiplugin
- Go To ACM > Observe > Alerting
- Create a Silence alert with alertname != blabla (turn on Negative matcher)
- Save it -> You will see it listed in the Silences list page
- Remove monitoring uiplugin
- Go To COO CSV and replace 2 entries for monitoring-console-plugin: quay.io/rh-ee-emurasak/monitoring-console-plugin:latest
- Save and Reload (some times)
- Add again monitoring uiplugin
- Go To ACM > Observe > Alerting
- Check Silences list page
Actual result: It is blank
The same happened when I created silence already in PF-6.
- Thinking about upgrade scenario that users would have some alerts, silences created without cluster label and upgrade to COO1.1+
- Even new silences with COO1.1+ created without cluster label, that in the past was created successfully even if it wouldn't work good in ACM perspective, but not breaking Silences list page. Thinking if there is any bug in the UI to work like before, or if there is a restriction on PF-6, whenever we create a silence alert in ACM perspective, to have cluster label to be filled by default...