Bug 1801295

Summary: The pod donut is showing two phrases when scaling up from 0
Product: OpenShift Container Platform Reporter: Aritra Roy <ariroy>
Component: Dev ConsoleAssignee: Aritra Roy <ariroy>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-13 21:57:30 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
pod_text for deployment scaling up from zero none

Description Aritra Roy 2020-02-10 15:07:50 UTC
Created attachment 1662164 [details]
pod_text for deployment scaling up from zero

Description of problem:
The pod donut is showing two phrases when scaling up from 0. It should show the # of pods plus the "scaling up phrase".

Version-Release number of selected component (if applicable):
4.4.0-0.ci-2020-02-09-194845

Steps to Reproduce:
1.Create a Deployment or DeploymentConfig from one of the import flows
2.check the Pod Count filter in topology

Actual results:
Pod text shows scaled to 0 and scaling to 1 during first scale up or any scale up from 0

Expected results:
At resting state, a pod should should show either of these:

    Autoscaled to 0
    Scaled to 0
    # of pods
When it's scaling up or down, it should say:
    Scaling to # (desired number of pods)

Comment 3 Ruchir Garg 2020-03-02 06:38:43 UTC
Bulk assigning all to Gajanan for verification.

Comment 4 Gajanan More 2020-03-03 09:14:08 UTC
Gajanan More has validated the bug (ODC-2566) on
Build: 4.4.0-0.ci-2020-03-03-033811
Browser: Google Chrome Version 78.0.3904.108

Comment 6 errata-xmlrpc 2020-05-13 21:57:30 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:0581