Bug 1998377 - Filesystem table head is not full displayed in disk tab
Summary: Filesystem table head is not full displayed in disk tab
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Phillip Bailey
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-27 01:43 UTC by Guohua Ouyang
Modified: 2022-03-10 16:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:05:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of vm disk tab (160.01 KB, image/png)
2021-08-27 01:43 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10095 0 None open Bug 1998377: Fix file systems table styles 2021-09-17 01:19:00 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:06:11 UTC

Description Guohua Ouyang 2021-08-27 01:43:43 UTC
Created attachment 1818141 [details]
screenshot of vm disk tab

Description of problem:
Filesystem table head is not full displayed in disk tab

Version-Release number of selected component (if applicable):
ocp 4.9-fc.0

How reproducible:
100%

Steps to Reproduce:
1. Create a VM
2. Install qemu-guest-agent in the VM
3. Start the VM and go to disk tab

Actual results:


Expected results:


Additional info:

Comment 4 errata-xmlrpc 2022-03-10 16:05:54 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 (Moderate: OpenShift Container Platform 4.10.3 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:0056


Note You need to log in before you can comment on or make changes to this bug.