Bug 2053279
| Summary: | Application cluster status is not updated in UI after restoring | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Thuy Nguyen <thnguyen> | ||||
| Component: | DR4Hub | Assignee: | Sahar Ebrahimi <sahare> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Thuy Nguyen <thnguyen> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rhacm-2.4.z | CC: | crizzo | ||||
| Target Milestone: | --- | Flags: | bot-tracker-sync:
rhacm-2.4.z+
|
||||
| Target Release: | rhacm-2.4.3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-04-20 23:47:32 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
G2Bsync 1097108063 comment thuyn-581 Tue, 12 Apr 2022 19:04:11 UTC G2BSync - Validated on 2.4.3-RC2. 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 |
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: