Bug 1780142 - alertmanager-access role prevents cluster-monitoring-view grantees users to view fired alerts
Summary: alertmanager-access role prevents cluster-monitoring-view grantees users to v...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.3.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1780037
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-05 13:51 UTC by Sergiusz Urbaniak
Modified: 2020-01-23 11:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1780037
Environment:
Last Closed: 2020-01-23 11:17:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 581 0 'None' 'open' '[release-4.3] Bug 1780142: Undo creating alertmanager-access role' 2019-12-05 13:52:18 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:18:08 UTC

Description Sergiusz Urbaniak 2019-12-05 13:51:29 UTC
+++ This bug was initially created as a clone of Bug #1780037 +++

With introducing the alertmanager-access role (https://jira.coreos.com/browse/SREP-1983) we prevent users having the cluster-monitoring-view cluster role to view fired alerts/silences and any information that reads from alertmanager.

This change is too intrusive and too coarse-grained, so effectively PM (Christian Heidenreich) is voting for undoing that change for 4.3.

Comment 5 errata-xmlrpc 2020-01-23 11:17:47 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, 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/RHBA-2020:0062


Note You need to log in before you can comment on or make changes to this bug.