Bug 1787006 - Show correct status of pod in pod donut
Summary: Show correct status of pod in pod donut
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.5.0
Assignee: Vikram Raj
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-30 09:47 UTC by Yadan Pei
Modified: 2020-07-13 17:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:13:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
PodDonutText (404.74 KB, image/png)
2019-12-30 09:47 UTC, Yadan Pei
no flags Details
4.5 pod donut (183.33 KB, image/png)
2020-06-23 14:26 UTC, cvogt
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:13:16 UTC

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


Note You need to log in before you can comment on or make changes to this bug.