Bug 2080567 - Number of cluster in violation in the table does not match other cluster numbers on the policy set details page
Summary: Number of cluster in violation in the table does not match other cluster numb...
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
high
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-30 06:17 UTC by Derek Ho
Modified: 2023-09-15 01:54 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:11:57 UTC
Target Upstream Version:
Embargoed:
dho: qe_test_coverage+
bot-tracker-sync: rhacm-2.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 22124 0 None None None 2022-04-30 10:51:34 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:12:08 UTC

Comment 1 bot-tracker-sync 2022-05-02 21:42:30 UTC 
G2Bsync 1115260471 comment 
 zlayne Mon, 02 May 2022 19:10:04 UTC 
 `G2Bsync` @drkho We believe the current implementation is expected. In context of the PolicySet there is only the one cluster from the PolicySet Placement. However, the Policy is placed by both the PolicySet placement and the Placement specific to the Policy. Therefore, the 2 cluster violations in the policy table is the expected result, as the the Policy is placed on 2 clusters. We don't believe the UI should hide legitimate Policy Placements that are not in context of the PolicySet.
Comment 3 bot-tracker-sync 2022-05-04 20:03:10 UTC 
G2Bsync 1117745903 comment 
 zlayne Wed, 04 May 2022 19:32:45 UTC 
 `G2Bsync` Fix has been merged. Please verify.
Comment 8 errata-xmlrpc 2022-06-09 02:11:57 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 9 Red Hat Bugzilla 2023-09-15 01:54:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days
Note You need to log in before you can comment on or make changes to this bug.