Bug 1879972

Summary: Web UI for application topology has wrong status updates
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Renato Puccini <rpuccini>
Component: App LifecycleAssignee: Feng Xiang <fxiang>
Status: CLOSED ERRATA QA Contact: Eveline Cai <ecai>
Severity: high Docs Contact: bswope <bswope>
Priority: unspecified    
Version: rhacm-2.0.zCC: gghezzo, xiangli
Target Milestone: ---Flags: gghezzo: rhacm-2.1+
Target Release: rhacm-2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhacm-2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-05 11:55:17 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:

Description Renato Puccini 2020-09-17 13:22:19 UTC 
Description of problem:
Navigating through topology view of an application deployed in 3 openshift clusters, the replicaset objects looses its status.

To see the object normal again, I just refreshed the browser (F5)

Also, the topology review refreshes and for a brief of time I see only the application object, tree is gone. Then a few seconds later, the tree is back.

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

How reproducible:
Deploy application on 3 different clusters.
Have the topology view open in the browser for more than 10 minutes (Notice this when preparing for a demo)

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 vbirsan 2020-09-17 13:31:30 UTC 
The fact that the topology loses nodes as it refreshes often indicates that the backend keeps updating the deployable annotations
Feng, can you please take a look
Comment 9 errata-xmlrpc 2020-11-05 11:55:17 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 (Red Hat Advanced Cluster Management for Kubernetes version 2.1 images), 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/RHEA-2020:4954