Bug 1839505

Summary: WebAdmin UI - remove unregistered entities from attached storage domain - confirmation dialog box text not aligned
Product: [oVirt] ovirt-engine Reporter: Ilan Zuckerman <izuckerm>
Component: BLL.StorageAssignee: Ahmad Khiet <akhiet>
Status: CLOSED CURRENTRELEASE QA Contact: Evelina Shames <eshames>
Severity: low Docs Contact:
Priority: low    
Version: 4.4.1CC: bugs, eshenitz, mtessun, sfishbai, tnisan
Target Milestone: ovirt-4.4.2Flags: pm-rhel: ovirt-4.4+
mtessun: planning_ack+
sfishbai: testing_ack+
Target Release: 4.4.2.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-22 10:22:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dialog box none

Description Ilan Zuckerman 2020-05-24 12:59:16 UTC
Created attachment 1691541 [details]
dialog box

Description of problem:
The following RFE added an option to remove unregistered entities from SD:
https://bugzilla.redhat.com/show_bug.cgi?id=1733932

But the confirmation dialog box text looks unaligned and misplaced.
See attached image

Version-Release number of selected component (if applicable):
rhv-4.4.1-1

How reproducible:
100

Steps to Reproduce:
1. Create a DC with 2 storage domains (sd1, sd2)
2. Create a VM with disks on SD1
3. Create a template from the VM in step 2
4. Create a floating disk based on SD1
5. Deactivate SD1
6. Detach SD1 without format it
7. Import SD1 back to the DC
8. Under Storage -> Domains -> SD1 -> import VM/Template/Disk select to remove the unregistered entities.
9. observe the confirmation dialog box

Actual results:
The text on the dialog box is not aligned and misplaced.

Expected results:
Should be fine

Comment 1 Lukas Svaty 2020-09-22 10:22:08 UTC
CLOSING low QE severity 4.4.2 issuees with NEXT_RELESE. If you believe these bugs indeed require QE Verification feel free to reopen.