Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1776951

Summary:	Pod tooltip shouldn't be Scaled to Zero when the build has not yet completed
Product:	OpenShift Container Platform	Reporter:	Sahil Budhwar <sbudhwar>
Component:	Dev Console	Assignee:	Sahil Budhwar <sbudhwar>
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.0	CC:	aos-bugs, cvogt, gamore, 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:
Clones:	1779487 (view as bug list)		Environment:
Last Closed:	2020-05-13 21:53:19 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 Sahil Budhwar 2019-11-26 16:12:22 UTC

As a user, if I add something by import from git, the topology view shows me that the build is running, but when I hover over the pod donut, it says "Scaled to 0". That's incorrect

Comment 1 Sahil Budhwar 2019-11-26 16:31:00 UTC


How reproducible:

Steps to Reproduce:
1. Create a new resource using git import form 
2. while the build is running then hovering over pod donut shows `Scaled To 0` which is incorrect and misleading that the user scaled the pods down


Actual results:


Expected results:
1. It should be showing `Scaling up` while hovering over the Pod Donut until the build is not finished


Additional info:

There is a fake pod created right now which shows up in Pods overview list on the resource tab. There shouldn't be any fake pod on the pod overview list.

Comment 3 Gajanan More 2020-03-03 12:42:32 UTC

I have validated this bug on
Build: 4.4.0-0.ci-2020-03-03-033811
Browser: Google Chrome Version 78.0.3904.108

Marking this as verified.

Comment 5 errata-xmlrpc 2020-05-13 21:53:19 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