Bug 1135976 – Edit pinned vm placement option clear vm cpu pinning options without any error message

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1135976 - Edit pinned vm placement option clear vm cpu pinning options without any error message

Summary:	Edit pinned vm placement option clear vm cpu pinning options without any erro...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	ovirt-engine
Classification:	oVirt
Component:	Frontend.WebAdmin (Show other bugs)
Sub Component:
Version:	---
Hardware:	x86_64 Linux

Priority	medium Severity high (vote)
Target Milestone:	ovirt-4.1.0-alpha
Target Release:	4.1.0.2
Assigned To:	Andrej Krejcir
QA Contact:	Artyom
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:	1419434
	Show dependency tree / graph

Reported:	2014-09-01 07:41 EDT by Artyom
Modified:	2017-02-06 01:57 EST (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	Previously, CPU pinning information could be silently lost. Now, a pop-up warning that CPU pinning information will be lost displays when a user saves a virtual machine. This means that the user is aware the CPU pinning information will be lost and has the choice to cancel the operation.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-02-01 09:37:45 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rule-engine: ovirt‑4.1+ rule-engine: planning_ack+ rgolan: devel_ack+ mavital: testing_ack+

Attachments	(Terms of Use)
screenshots (298.89 KB, application/octet-stream) 2014-09-01 07:41 EDT, Artyom	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	60919	master	MERGED	webadmin: Show warning if cpu topology will be lost	2016-08-30 03:53 EDT

Groups: None (edit)

Description Artyom 2014-09-01 07:41:53 EDT

Created attachment 933317 [details]
screenshots

Description of problem:
If I have pinned vm(pinned to host and not migratable) with cpu pinning options and change placement option, ui automatically will clear cpu pinning options without any error message.

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 pinned vm with cpu pinning
2. Change placement option and check cpu pinning
3.

Actual results:
UI clear automatically cpu pinning without inform user about it

Expected results:
Or show error message, that user will lost cpu pinning, or like in 3.4 light with red conflict options(if conflict options on different tabs it's useful to light tabs as well)

Additional info:
It's actual for most conflict parameters in UI edit window

Comment 1 Sandro Bonazzola 2015-01-21 11:05:43 EST

oVirt 3.5.1 has been released, re-targeting to 3.5.2 as marked as urgent / high severity

Comment 2 Sandro Bonazzola 2015-03-03 08:00:25 EST

Re-targeting to 3.5.3 since this bug has not been marked as blocker for 3.5.2 and we have already released 3.5.2 Release Candidate.

Comment 3 Roy Golan 2015-06-10 05:04:52 EDT

Too risky for 3.5.Z - re-targeting for 3.6

Einav - do you have an RFE on marking changes in other side tabs visible to the user?

Comment 4 Einav Cohen 2015-06-10 07:23:32 EDT

(In reply to Roy Golan from comment #3)
> Too risky for 3.5.Z - re-targeting for 3.6
> 
> Einav - do you have an RFE on marking changes in other side tabs visible to
> the user?

no - feel free to open one. thanks.

Comment 5 Red Hat Bugzilla Rules Engine 2015-10-19 06:52:58 EDT

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 6 Sandro Bonazzola 2015-10-26 08:33:25 EDT

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 7 Sandro Bonazzola 2015-11-05 03:17:30 EST

oVirt 3.6.0 has been released on November 4th, re-targeting to 3.6.1 since this bug has been marked as high severity

Comment 8 Eyal Edri 2015-12-17 08:51:45 EST

ovirt 3.6.1 is GA.
moving all open bugs to 3.6.2

Comment 9 Eyal Edri 2015-12-17 09:00:03 EST

ovirt 3.6.1 was GA'd, all open bugs should move to 3.6.2.

Comment 10 Sandro Bonazzola 2016-12-12 08:56:47 EST

The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 11 Artyom 2016-12-13 09:23:25 EST

Verified ovirt-engine-4.1.0-0.2.master.20161212172238.gitea103bd.el7.centos.noarch 

Error message
golden_env_mixed_virtio_0:
ACTION_TYPE_FAILED_VM_CANNOT_BE_PINNED_TO_CPU_WITH_UNDEFINED_HOST

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