Bug 2027613

Summary: Users can't silence alerts from the dev console
Product: OpenShift Container Platform Reporter: Simon Pasquier <spasquie>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: abhindas, cjerolim, gparente, jakumar, jritter, nmukherj, sdharma, s.heijmans, spathak, viraj
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 10:39:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2079985    
Attachments:
Description Flags
Network monitor from Firefox none

Description Simon Pasquier 2021-11-30 09:13:26 UTC
Created attachment 1844139 [details]
Network monitor from Firefox

Description of problem:
When logged in as a non-admin user, I can't silence alerts from the Dev Console.

Version-Release number of selected component (if applicable):
4.10 but the same issue may exist for previous versions.

How reproducible:
Always

Steps to Reproduce:
1. Login to the dev console as a non-admin user.
2. Follow the OCP documentation to deploy the example application including the service monitor and the rule (the user needs to be granted the monitoring-edit role). See https://docs.openshift.com/container-platform/4.9/monitoring/enabling-monitoring-for-user-defined-projects.html for details.
3. Go to the Observe > Alerts page and disable notifications during 30 minutes for the VersionAlert alert.

Actual results:
The alert notification seems to be disabled but on refresh, the notification is still enabled.

Expected results:
The notification is permanently disabled.

Additional info:
The console backend hits the wrong service which results in a 403 response code, it should use the tenancy-aware service.

Comment 15 spathak@redhat.com 2022-06-16 06:41:27 UTC
Verified on build version: 4.11.0-0.nightly-2022-06-15-161625
Browser version: Chrome 101

Comment 16 errata-xmlrpc 2022-08-10 10:39:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069