Created attachment 1696756 [details] screenshot1
Created attachment 1696757 [details] screenshot2
Created attachment 1696758 [details] screenshot3
Created attachment 1696759 [details] screenshot4
Created attachment 1696760 [details] screenshot5
This bug was cloned from Bug 1819254 for dealing with Storage issues only. Please see the relevant attachements.
Hello, I found some issues during testing. Some of these might be by design, so let me know if they won't be fixed: - 'New Domain' dialog window has still a huge white space area when the custom options are folded. - 'New Quota' and 'Edit Quota' dialog has a lot of space underneath and the description field is too stretched to the right. Also, the usage visualization is not left aligned with other fields in the dialog. - 'Volume Snapshot - Cluster options' dialog does not have space before the first variable. - 'New Virtual Disk' dialog has also a lot of white space underneath the info part. Tested in: rhvm-branding-rhv-4.4.4-1.el8ev.noarch ovirt-engine-4.4.2.2-0.3.el8ev.noarch firefox-78.0.2-1.fc31.x86_64
Hello, These are the popup windows that has been changed: * New Data Center * Upload Image * New Quota I did not see that new storage domain popup has an extra space, also volume snapshot. can you please attach a screenshots of the storage related popup windows that need to be changed?
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
All the issues stated in the previous comments have been fixed. Verified in: rhvm-branding-rhv-4.4.5-1.el8ev.noarch ovirt-engine-4.4.3.3-0.19.el8ev.noarch firefox-80.0-1.fc31.x86_64
fixed in 4.4.2, verified in 4.4.3. Do you want to push it out to 4.4.3? If yes then just move the TM please
Thanks for noticing.
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.