Bug 1226767 - New Virtual Machine window-> CPU Shares & CPU Pinning Topology should not be greyed out when usable
Summary: New Virtual Machine window-> CPU Shares & CPU Pinning Topology should not be ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Doron Fediuck
QA Contact: Shira Maximov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-01 04:09 UTC by Julie
Modified: 2016-07-05 07:38 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 07:38:10 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.0.0+
ylavi: planning_ack+
tnisan: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
CPU Shares & CPU Pinning Topology should not be greyed out when usable (67.32 KB, image/png)
2015-06-01 04:09 UTC, Julie 		no flags Details
cpu_pinning_topology (22.28 KB, image/png)
2016-03-08 09:59 UTC, Roy Golan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 56919 0 master MERGED webadmin: Synched Cpu Pinning label and textbox 2016-05-02 20:21:20 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.