Bug 2053279 - Application cluster status is not updated in UI after restoring
Summary: Application cluster status is not updated in UI after restoring
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: DR4Hub
Version: rhacm-2.4.z
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.4.3
Assignee: Sahar Ebrahimi
QA Contact: Thuy Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-10 20:42 UTC by Thuy Nguyen
Modified: 2022-04-20 23:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 23:47:32 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.4.z+


Attachments (Terms of Use)
App UI screen (143.78 KB, image/png)
2022-02-10 20:42 UTC, Thuy Nguyen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 19855 0 None None None 2022-02-10 21:43:17 UTC
Red Hat Product Errata RHSA-2022:1476 0 None None None 2022-04-20 23:47:44 UTC

Description Thuy Nguyen 2022-02-10 20:42:29 UTC
Created attachment 1860443 [details]
App UI screen

Description of problem: Application cluster status is not updated in UI after restoring

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


How reproducible: 


Steps to Reproduce:
1. Backup the primary hub having app and policy deployed/propagated onto spoke clusters
2. Shut down the primary hub
3. Restore the previous backups onto a secondary hub

Actual results:
Application cluster status show 'None'

Expected results:
The cluster status should show number of spoke clusters on which the application has been deployed

Additional info:

Comment 2 bot-tracker-sync 2022-04-12 19:59:43 UTC
G2Bsync 1097108063 comment 
 thuyn-581 Tue, 12 Apr 2022 19:04:11 UTC 
 G2BSync -
Validated on 2.4.3-RC2.

Comment 8 errata-xmlrpc 2022-04-20 23:47:32 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 (Moderate: Red Hat Advanced Cluster Management 2.4.3 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:1476


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