Bug 2072824 - The edit/delete policyset button should be greyed when using viewer check
Summary: The edit/delete policyset button should be greyed when using viewer check
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.5
Assignee: Kevin Cormier
QA Contact: Xiang Yin
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-07 03:20 UTC by yahliu
Modified: 2023-02-21 10:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 02:10:35 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 21508 0 None None None 2022-04-07 09:05:24 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:10:41 UTC

Comment 1 yahliu 2022-04-07 03:29:04 UTC 
Please also disable delete button when using editor to check policyset.
Comment 2 bot-tracker-sync 2022-04-08 19:24:56 UTC 
G2Bsync 1093087786 comment 
 zlayne Fri, 08 Apr 2022 16:57:02 UTC 
 `G2Bsync` Fix has been merged please verify.
Comment 3 yahliu 2022-04-13 07:48:12 UTC 
Verified on 2.5.0-DOWNSTREAM-2022-04-09-18-58-25
Comment 7 errata-xmlrpc 2022-06-09 02:10:35 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: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), 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:4956
Comment 8 Ketrina Foster 2023-02-21 10:32:06 UTC Comment hidden (spam)
Note You need to log in before you can comment on or make changes to this bug.