Bug 1302585 - [webadmin] VM run once -> Initial run Indentation problem
Summary: [webadmin] VM run once -> Initial run Indentation problem
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.6.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On:
Blocks: 1298850
TreeView+ depends on / blocked
 
Reported: 2016-01-28 08:33 UTC by Ilanit Stein
Modified: 2022-07-05 13:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-16 09:29:10 UTC
oVirt Team: Virt
Embargoed:


Attachments (Terms of Use)
Windows_VM_run_once_initial_run screenshot (43.83 KB, image/png)
2016-01-28 08:33 UTC, Ilanit Stein
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1273476 0 medium CLOSED New VM dialog ui is inconsistent 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker RHV-46991 0 None None None 2022-07-05 13:38:55 UTC

Internal Links: 1273476

Description Ilanit Stein 2016-01-28 08:33:24 UTC
Created attachment 1119070 [details]
Windows_VM_run_once_initial_run screenshot

Description of problem:
For a windows VM, run once, with Floppy [sysprep] attached,
Inside Initial run tab,
All parameters listed, should have the same indentation (current screen shot attached). Same as these same fields are displayed in Edit VM->Initial run->Use sysrep.
Having these differences in the indention give a wrong impression, as if 
domain & its credentials fields, at the bottom, belong to sysprep located right above it, though it's not related. 

Version-Release number of selected component (if applicable):
rhevm 3.6.2-10

Comment 2 Michal Skrivanek 2016-03-16 09:29:10 UTC
Run Once dialog is a design nightmare. It shouldn't have been done like that in the first place. Cosmetic changes are not going to make it any better, more serious rewrite/replacement is preferred


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