Bug 1832268

Summary: Pod ring label shows incorrect text for failed pod
Product: OpenShift Container Platform Reporter: Aritra Roy <ariroy>
Component: Dev ConsoleAssignee: Aritra Roy <ariroy>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:35:22 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 Flags
pod ring label for failed pod none

Description Aritra Roy 2020-05-06 12:37:50 UTC
Created attachment 1685700 [details]
pod ring label for failed pod

Description of problem:
podring label displays incorrect text for failed pod ( title: "0", subtitle: "scaling to 1")

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

How reproducible:

Steps to Reproduce:
1.Visit the +Add page
2.select From Git from the options
3.use a git url with the intention to produce failed podd e.g. "https://github.com/jboss-openshift/openshift-quickstarts" produces pods with "CrashLoopBackOff" failure.
4.fill in other fields of the import from git form with usual/preferred values and click on Create

Actual results:
Pod ring label text displays title: "0", subtitle: "scaling to 1"

Expected results:
Pod ring label text should display title: "1", subtitle: "pod"

Additional info:

Comment 4 Gajanan More 2020-05-22 11:34:15 UTC
I have validated the bug on:
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 5 errata-xmlrpc 2020-07-13 17:35:22 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.