Bug 2049810 - Clustersets do not appear in UI
Summary: Clustersets do not appear in UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: rhacm-2.3.6
Assignee: James Talton
QA Contact: dhuynh
Christopher Dawson
URL:
Whiteboard:
: 2049809 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-02 18:00 UTC by dhuynh
Modified: 2022-03-03 23:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-22 21:58:25 UTC
Target Upstream Version:
Embargoed:
dhuynh: Blocker+
dhuynh: rhacm-2.3.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 19641 0 None None None 2022-02-02 21:38:09 UTC
Red Hat Product Errata RHSA-2022:0595 0 None None None 2022-02-22 21:59:59 UTC

Description dhuynh 2022-02-02 18:00:58 UTC 
Description of problem:
Creating a new cluster set creates the cluster set resource but it does not appear in the console.

This was working in ACM 2.3.5, no longer working on 2.3.6 RC1.

Version-Release number of selected component (if applicable):
ACM 2.3.6 RC1

How reproducible:
Everytime

Steps to Reproduce:
1. Login to ACM, go to Clustersets page
2. Create new clusterset
3. Observe that the clusterset does not appear in the UI, but resource exists in the backend

Actual results:
Clustersets do not appear in UI

Expected results:
Clustersets appear

Additional info:
Comment 1 dhuynh 2022-02-02 18:01:33 UTC 
This appeared in 2.4.0 builds before. Perhaps a missing backport?
Comment 2 dhuynh 2022-02-02 21:22:02 UTC 
*** Bug 2049809 has been marked as a duplicate of this bug. ***
Comment 3 dhuynh 2022-02-04 19:40:10 UTC 
Fixed in 2.3.6RC2.
Comment 10 errata-xmlrpc 2022-02-22 21:58:25 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.3.6 security updates 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:0595
Note You need to log in before you can comment on or make changes to this bug.