Bug 1226767

Summary: New Virtual Machine window-> CPU Shares & CPU Pinning Topology should not be greyed out when usable
Product: [oVirt] ovirt-engine Reporter: Julie <juwu>
Component: Frontend.WebAdminAssignee: Doron Fediuck <dfediuck>
Status: CLOSED CURRENTRELEASE QA Contact: Shira Maximov <mshira>
Severity: medium Docs Contact:
Priority: high    
Version: 3.5.1CC: bugs, dfediuck, gklein, istein, lsurette, mavital, mgoldboi, michal.skrivanek, rbalakri, rgolan, Rhev-m-bugs, sbonazzo, srevivo, tnisan, ykaul
Target Milestone: ovirt-4.0.0-betaFlags: rule-engine: ovirt-4.0.0+
ylavi: planning_ack+
tnisan: devel_ack+
mavital: testing_ack+
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 07:38:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
CPU Shares & CPU Pinning Topology should not be greyed out when usable
none
cpu_pinning_topology none

Description Julie 2015-06-01 04:09:36 UTC
Created attachment 1033112 [details]
CPU Shares & CPU Pinning Topology should not be greyed out when usable

Checked in version 3.5.1-0.4.el6ev
See attached screenshot. The two options (CPU Shares & CPU Pinning Topology) should not be greyed out when usable. 

Kind regards,
Julie

Comment 1 Sandro Bonazzola 2015-10-26 12:28:55 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 2 Red Hat Bugzilla Rules Engine 2015-12-02 00:14:59 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 3 Red Hat Bugzilla Rules Engine 2015-12-02 00:14:59 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 4 Roy Golan 2016-03-08 09:59:05 UTC
Created attachment 1134084 [details]
cpu_pinning_topology

Comment 5 Roy Golan 2016-03-08 10:00:08 UTC
Looks like only cpu pinning topology is grey. Probably low risk fix, not sure about the easiness, Tomer?

Comment 6 Tomer Saban 2016-03-27 08:45:28 UTC
Doesn't seems to be too complicated but when i'll get to it we will see. Currently working on something else.

Comment 8 Yaniv Lavi 2016-05-09 10:53:02 UTC
Moving to first RC, since things should not be targeted to second one at this point.

Comment 9 Shira Maximov 2016-05-23 10:19:49 UTC
verified on :
oVirt Engine Version: 4.0.0-0.0.master.20160515171411.git6759e3f.el7.centos

verification steps: 
Use CPU Shares & CPU Pinning Topology and check that they are not greyed out.

Comment 10 Sandro Bonazzola 2016-07-05 07:38:10 UTC
oVirt 4.0.0 has been released, closing current release.