Bug 1866034
Summary: | "Scaled to 0" text appears to be too large for pod ring | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Samuel Padgett <spadgett> | ||||||
Component: | Dev Console | Assignee: | Jeff Phillips <jephilli> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 4.6 | CC: | aos-bugs, jephilli, nmukherj | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 4.6.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: |
Version: 4.6.0-0.nightly-2020-08-02-134243
Cluster ID: 6de0fe23-5d9b-4add-a336-1efc5fad0306
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:80.0) Gecko/20100101 Firefox/80.0
|
|||||||
Last Closed: | 2020-10-27 16:23:15 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: |
|
Created attachment 1712355 [details]
Screenshot of scaled to zero
I have validated the bugzilla on: Build: 4.6.0-0.nightly-2020-08-23-214712 Browser: Google Chrome Version 84.0.4147.89 Marking this as verified. 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. https://access.redhat.com/errata/RHBA-2020:4196 |
Created attachment 1710391 [details] Screenshot The "Scaled to 0" text for a deployment pod ring overlaps with the ring itself. I'm not sure if this is intentional or not, but it looked strange to my eye. Opening a bug in case this isn't intended. See attached screenshot.