Bug 1912523

Summary: Standalone pod status not updating in topology graph
Product: OpenShift Container Platform Reporter: Jeff Phillips <jephilli>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: Debsmita Santra <dsantra>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, dsantra, nmukherj
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:49:41 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 Jeff Phillips 2021-01-04 16:25:17 UTC 
Description of problem:

The stand alone pod workloads do not update the pod status in the topology graph.

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


How reproducible:

always

Steps to Reproduce:

Issue 1:
1. Navigate to the topology graph view
2. Externally, add a stand alone pod
3. Click on the stand alone pod to show the details view and then the Details tab

Issue 2:
1. Create at least two deployments
2. Select a Deployment to open the sidebar
3. Switch to another Deployment

Actual results:

Issue 1:
The stand alone pod is shown, pod ring status stays as 'pending'
The details for the pod is shown and its status updates to 'running'

Issue 2:
The pod list is not updated, continuing to show pods for the first deployment

Expected results:

Issue 1:
The stand alone pod is shown, pod ring status updates to 'running'
The details for the pod is shown and its status updates to 'running'

Issue 2:
The correct pods are shown for the selected Deployment when switching between Deployments

Additional info:
Comment 3 Debsmita Santra 2021-01-15 15:44:38 UTC 
verified on build 4.7.0-0.nightly-2021-01-14-211319
Comment 6 errata-xmlrpc 2021-02-24 15:49:41 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: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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-2020:5633