-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
premerge
-
Moderate
-
Yes
-
MON Sprint 262
-
1
-
False
-
Description of problem:
tested
https://github.com/openshift/monitoring-plugin/pull/252
https://github.com/openshift/console/pull/14480
with cluster-bot
launch 4.18.0-0.nightly-2024-11-14-090045,openshift/monitoring-plugin#252,openshift/console#14480 aws
admin user login dev console, select openshift-monitoring project and go to "Observe -> Alerts" to silence one alert first, for example Watchdog alert, then go to Silences tab, click the checkbox for the silence, then click "Expire 1 silence" button in the header next to "Create silence" button, there is forbidden error shows. see the picture and screen recording:
https://drive.google.com/file/d/1GziqNsIKMvjyG3KDWlipUPEfmMVFZN_1/view?usp=drive_link
https://drive.google.com/file/d/1APNKkVjc1vGWq6WqbtwpVE241r3uO0yn/view?usp=drive_link
seems related to cluster policy
co-fetch.ts:132 consoleFetch failed for url /api/alertmanager-tenancy/api/v2/silence/1f5d9fdc-4d07-4093-8119-c4f3f8c138e1?namespace=undefined r: Access denied due to cluster policy.
NOTE: no such issue if we click "Expire silence" from the cog menu, no issue with 4.18.0-0.nightly-2024-11-14-090045 either
Version-Release number of selected component (if applicable):
tested with PRs
How reproducible:
always
Steps to Reproduce:
1. see the description
Actual results:
forbidden error
Expected results:
no error