Bug 2068538

Summary:	Crashloop back-off popover visual spacing defects
Product:	OpenShift Container Platform	Reporter:	Steve Goodwin <sgoodwin>
Component:	Management Console	Assignee:	Steve Goodwin <sgoodwin>
Status:	CLOSED ERRATA	QA Contact:	Xiyun Zhao <xiyuzhao>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	aos-bugs, jhadvig, mehall, yapei
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Mac OS
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2060930	Environment:
Last Closed:	2022-08-10 11:02:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Steve Goodwin 2022-03-25 16:49:56 UTC

The UI of the popover has margin and padding issues. Two paragraphs run together and the actions at the bottom of the popover are too close to one another.

Comment 4 Xiyun Zhao 2022-04-08 14:20:40 UTC

This bug has been verified on payload 4.11.0-0.nightly-2022-04-07-053433

Verification Step
1. Follow the steps which provide on the description of the bug
2. Navigate to Developer perspective, click on the Pod name
3. On the right panel, click on the CrashLoopBackOff status in the table
4. Resize the window, Check if the layout has correct alignment and spacing
5. Click the pod name, click 'CrashLoopBackOff' on Status on Pod details page
6. Resize the window, Check if the layout has correct alignment and spacing

Result:
1,4,6. Attached expected and fixed result for more details, now all layout has correct alignment and spacing in the pops up dialog windows after click message of  'CrashLoopBackOff'

Comment 8 errata-xmlrpc 2022-08-10 11:02: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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069