Bug 1326817 - Impossible to edit HE VM CPU number because it show only number of sockets that you defined at deploy time
Summary: Impossible to edit HE VM CPU number because it show only number of sockets th...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine
Version: 3.6.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Roy Golan
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks: 1304387
TreeView+ depends on / blocked
 
Reported: 2016-04-13 13:14 UTC by Artyom
Modified: 2017-05-11 09:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-13 16:02:21 UTC
oVirt Team: SLA
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
screenshot (67.89 KB, image/png)
2016-04-13 13:14 UTC, Artyom
no flags Details

Description Artyom 2016-04-13 13:14:17 UTC
Created attachment 1146848 [details]
screenshot

Description of problem:
Impossible to edit HE VM CPU number because it shows only number of sockets that you defined at deploy time

Version-Release number of selected component (if applicable):
rhevm-3.6.5.3-0.1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy HE and add storage domain to engine to auto-import it
2. Open HE VM update window via webadmin and change number of CPU's
3.

Actual results:
The engine does not give to change number of CPU's because HE VM list of sockets that engine show equal to one that you define at deploy time(see screenshot)

Expected results:
The engine must show list of sockets that include greater values, like for regular VM(1..12)

Additional info:

Comment 1 Martin Sivák 2016-04-13 15:37:19 UTC
Uh, but it behaves like this for me with normal VMs also. You first edit the total number of vCPUs and only after that you can select the topology iirc.

Did you try using REST btw?

Comment 2 Artyom 2016-04-13 16:02:21 UTC
It is my mistake host only has 2 CPU's, I checked it on the host with 4 CPU's and it worked fine.


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