Bug 1371532 - Cannot change number of monitors for instance.
Summary: Cannot change number of monitors for instance.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.3
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 12:18 UTC by Andrei Stepanov
Modified: 2022-06-27 07:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-03 12:49:51 UTC
oVirt Team: Virt
sbonazzo: ovirt-4.3-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46506 0 None None None 2022-06-27 07:22:56 UTC

Description Andrei Stepanov 2016-08-30 12:18:07 UTC
Cannot change number of monitors for specific VM instance.

ovirt-engine-4.0.3-0.1.el7ev.noarch

1. Log in admin portal
2. At the top-right press "Configure" 
3. Select "Edit instance type"
4. Select existing instance profile or create a new one.
5. Press "Edit"
6. Select "Console" tab.
7. Set "video type" to qxl
8. Set "graphic type" to spice

Actual results: "number of monitors" is hardcoded to "1"

In my opinion, if the there is no way to change "Number of monitors", than there is no use to show it. Therefore, it can confuse a user.

Comment 1 Tomas Jelinek 2016-09-01 09:19:46 UTC
it is not actually hardcoded but depends on the selection of the "video type". For qxl it has to be enabled and for others disabled. It seems to work properly for VM, but for instance type is enabled only if the is qxl and the protocol is VNC. That definitely is a bug.

Comment 2 Tomas Jelinek 2016-09-19 08:53:02 UTC
The fix would touch a part of code which could break something else easily. I would hesitate to put this to z-stream, postponing to 4.1

Comment 3 Michal Skrivanek 2016-12-21 09:09:05 UTC
The bug was not addressed in time for 4.1. Postponing to 4.2

Comment 4 Tomas Jelinek 2017-06-15 07:52:19 UTC
Instance types are not widely used, postponing.

Comment 6 Ryan Barry 2019-01-03 12:49:51 UTC
This will not be addressed in a reasonable timeframe. Please re-open if it's still important.


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