Bug 1870805

Summary: Inconsistent pod donut text for knative service in topology and sidebar details
Product: OpenShift Container Platform Reporter: Jaivardhan Kumar <jakumar>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6CC: aos-bugs, cvogt, nmukherj
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:30:13 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:

Description Jaivardhan Kumar 2020-08-20 19:04:39 UTC
Description of problem: Inconsistent pod donut text for knative service in topology and sidebar details

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

How reproducible: Always

Steps to Reproduce:
1. Install Serverless operator
2. Go to dev Perspective -> Add -> container image 
3. Deploy any image as knative service and create

Actual results: In Topology view can see Donut status text is "Scaled to 0" however on sidebar it says "Autoscaled to 0"

Expected results:Donut status text for knative service should be consistent across and say "Autoscaled to 0"

Additional info:

Comment 1 Jaivardhan Kumar 2020-08-20 19:07:48 UTC

Comment 4 cvogt 2020-09-02 13:39:19 UTC
Browser: 84.0.522.61 (Official build) (64-bit)
Build: 4.6.0-0.nightly-2020-08-23-214712

After fix, knative Revisions now correctly show the `autoscaled to 0` label in the pod donut.

Comment 6 errata-xmlrpc 2020-10-27 16:30:13 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.