Bug 1404224 - In Edit VM the advanced parameters in the console tab are not aligned
Summary: In Edit VM the advanced parameters in the console tab are not aligned
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 12:16 UTC by Shira Maximov
Modified: 2020-04-01 14:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-01 14:45:37 UTC
oVirt Team: Virt
tjelinek: ovirt-future?
tjelinek: planning_ack?
tjelinek: devel_ack?
tjelinek: testing_ack?

Attachments (Terms of Use)
print screen (226.22 KB, image/png)
2016-12-13 12:16 UTC, Shira Maximov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Shira Maximov 2016-12-13 12:16:07 UTC 
Created attachment 1231175 [details]
print screen

Description of problem:
In The edit VM, inside the the console tab, the advanced parameters have only one field : Disable strict user checking, this field is not aligned with the advanced parameters title.

also the warning message is confusing because it refers to several values when there is only one value is the advanced parameters   
"It is recommended to keep the default values in the fields below unchanged." 
(should change to: value in fields)

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.0.6.3-0.1.el7ev


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yaniv Kaul 2017-11-16 14:13:17 UTC 
We should remove this from the 'Advanced Parameters'...
Comment 2 Michal Skrivanek 2020-03-19 15:41:45 UTC 
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
Comment 3 Michal Skrivanek 2020-04-01 14:45:37 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Comment 4 Michal Skrivanek 2020-04-01 14:49:59 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Note You need to log in before you can comment on or make changes to this bug.