Bug 1876969

Summary: Topology view faults
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Mark Roberts <marrober>
Component: App LifecycleAssignee: fxiang
Status: CLOSED ERRATA QA Contact: Eveline Cai <ecai>
Severity: medium Docs Contact: bswope <bswope>
Priority: unspecified    
Version: rhacm-2.0CC: gghezzo, rjung, xiangli
Target Milestone: ---Flags: gghezzo: rhacm-2.1+
Target Release: rhacm-2.1   
Hardware: Unspecified   
OS: Linux   
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:
Attachments:
Description Flags
Image of errors. none

Description Mark Roberts 2020-09-08 15:38:13 UTC 
Created attachment 1714150 [details]
Image of errors.

Description of problem:

Topology view shows two different problems.

1. The deployed application on the managed cluster has four replicas. The deployment node in the topology diagram reports "Required Replicas: 1", but does show correctly the number of application pods in the "Cluster deployment status" information underneath the number of replicas.

2. Topology view flashes into view the route underneath the service but then the route disappears from view. Route is present on the managed node and can be used successfully.

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

ACM 2.0.2

How reproducible:

Easy to reproduce using assets here : https://github.com/marrober/layers-deployment.git

Steps to Reproduce:
1. Create the channel, subscription, application and placement rule and observe the topology view in ACM.
2.
3.

Actual results:

No route and incorrect number of replicas reported.


Expected results:

Display of route and the correct number of replicas reported.

Additional info:
Comment 1 Mark Roberts 2020-09-09 08:09:02 UTC 
After an RHPDS server stop and restart overnight the number of Required replicas on the details panel for the deployment object is now correct. 

It was wrong for several hours after initially setting the number of replicas on the YAML file and re-deploying the app even though four pods were visible.
Comment 2 Roke Jung 2020-10-05 21:35:05 UTC 
These problems are fixed in the coming ACM 2.1 release.
Comment 6 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