Bug 1787006

Summary: Show correct status of pod in pod donut
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, cvogt, jokerman, nmukherj, spadgett, viraj, yapei
Target Milestone: ---   
Target Release: 4.5.0   
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: 2020-07-13 17:13:00 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
PodDonutText
none
4.5 pod donut none

Description Yadan Pei 2019-12-30 09:47:05 UTC 
Description of problem:
Before pods are running, it shows 0 of 1 pods on overview, but in Overview sidebar, it shows confusing text 'Scaled to 0, scaling to 1', also the same text on Resource overview pod donut

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-29-173422

How reproducible:
Always

Steps to Reproduce:
1. Create app from image(ruby) on console or CLI
2. Check workloads on project Workloads page, click on resource panel to open sidebar, monitor pod status in Overview sidebar
3. Goes to DC Overview page, check pods info in the pod donut

Actual results:
2-3. Before pods are started, it shows:
Scaled to 0
scaling to 1

Expected results:
2-3. Pods are being created, it should show 'scaling to 1'

Additional info:
Comment 1 Yadan Pei 2019-12-30 09:47:43 UTC 
Created attachment 1648558 [details]
PodDonutText
Comment 4 cvogt 2020-06-23 14:26:43 UTC 
Created attachment 1698466 [details]
4.5 pod donut

This issue looks to be resolved in 4.5. Please see attached screenshot.
Verified on 4.5.0-0.nightly-2020-06-05-214616
Comment 7 errata-xmlrpc 2020-07-13 17:13:00 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, 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/RHBA-2020:2409