Bug 1872113

Summary: Persistent Volume Claims details page columns are in different layout with other details pages
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Yadan Pei <yapei>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 4.6CC: aos-bugs, jokerman, yapei
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:
Last Closed: 2020-10-27 16:32:10 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:
Description Flags
Correct PVC Details page layout none

Description Yadan Pei 2020-08-25 06:03:27 UTC 
Description of problem:
when a PVC is bound, console will show the capacity on PVC Details page, the donut chart make the details page layout is wrong, the columns are using 'col-md-4 col-xl-5' while on other pages 'col-sm-6'


Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-08-24-110601

How reproducible:
Always

Steps to Reproduce:
1. create PVC and make it bound

Actual results:
1. check PVC Details 

Expected results:
1. the details page show two columns, but the two columns are in wrong layout 

Additional info:
Comment 3 Yadan Pei 2020-08-27 07:02:13 UTC 
Created attachment 1712774 [details]
Correct PVC Details page layout

Now PVC Details page layout is correct

Verified on 4.6.0-0.nightly-2020-08-26-152137
Comment 5 errata-xmlrpc 2020-10-27 16:32:10 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.

https://access.redhat.com/errata/RHBA-2020:4196