Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1135982

Summary: Not possible to change vm 'Cores per Virtual Socket' and 'Virtual Sockets' until 'Total Virtual CPUs' changed
Product: [oVirt] ovirt-engine Reporter: Artyom <alukiano>
Component: Frontend.WebAdminAssignee: Marek Libra <mlibra>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, gklein, mgoldboi, michal.skrivanek, mlibra, rbalakri, rgolan, yeylon, ykaul
Target Milestone: ---Flags: ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-01 11:07:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Artyom 2014-09-01 12:01:29 UTC
Created attachment 933319 [details]
screenshot

Description of problem:
Not possible to change vm 'Cores per Virtual Socket' and 'Virtual Sockets' until 'Total Virtual CPUs' changed

Version-Release number of selected component (if applicable):
ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create new vm with 4 total cpu's(2 socket and 2 cores per socket)
2. Edit vm and try to change or 'Cores per Virtual Socket' or 'Virtual Sockets'
3.

Actual results:
You can't change it before you change parameter in 'Total Virtual CPUs' filed

Expected results:
You can freely change this parameters

Additional info:

Comment 1 Sandro Bonazzola 2015-01-21 16:08:25 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 11:01:36 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Sandro Bonazzola 2015-10-26 12:50:31 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 4 Sandro Bonazzola 2015-11-05 08:21:38 UTC
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high

Comment 5 Red Hat Bugzilla Rules Engine 2015-11-16 14:07:37 UTC
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset.
Please set the correct milestone or add the flag.

Comment 6 Michal Skrivanek 2016-01-29 15:23:07 UTC
please check and close if not relevant anymore

Comment 7 Marek Libra 2016-02-01 11:07:34 UTC
The described scenario works fine on recent master.