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

Bug 1333409

Summary:	Inconsistent behavior when creating VM from template that pinned to hosts via REST and via UI
Product:	[oVirt] ovirt-engine	Reporter:	Artyom <alukiano>
Component:	RestAPI	Assignee:	Jenny Tokar <jtokar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.5.1	CC:	bugs, dfediuck, mavital, tjelinek
Target Milestone:	ovirt-4.2.0	Keywords:	Triaged
Target Release:	4.2.0	Flags:	rule-engine: ovirt-4.2+ rule-engine: planning_ack+ rule-engine: devel_ack+ mavital: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:55:37 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:

Description Artyom 2016-05-05 12:38:19 UTC

Description of problem:
Inconsistent behavior when creating VM from template that pinned to hosts via REST and via UI

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

How reproducible:
Always

Steps to Reproduce:
1. Create template from VM that pinned to hosts
2. Create VM from template via REST and via UI
POST request:
<vm>
<name>test_vm</name>
<cluster id="clsuter_id"/>
<template id="template_with_pinning_id"/>
</vm>
3.

Actual results:
Create VM via UI: new VM pinned to hosts
Create VM via REST: new VM does not pin to hosts

Expected results:
I wait for consistent behavior, between REST and UI, or does not inherit pinning hosts from the template, or inherit it automatically also when creating VM from the template via REST API.

Additional info:

Comment 1 Juan Hernández 2016-05-05 14:55:14 UTC

May be a side effect of the fact that the backend no longer copies the template attributes itself? Do we need to copy CPU pinning explicitly like we do with other attributes?

Comment 2 Tomas Jelinek 2016-05-06 08:48:22 UTC

I would rather say a regression introduced by the multi-pinning feature where a VM can be pinned to more than one host.

Comment 3 Juan Hernández 2016-05-06 08:50:25 UTC

API or backend?

Comment 4 Tomas Jelinek 2016-05-06 11:41:31 UTC

API - it looks the template up and maps its params to the new VM - it needs to map also this placement policy.

Comment 5 Artyom 2017-09-17 07:34:48 UTC

Verified on ovirt-engine-4.2.0-0.0.master.20170913112412.git2eb3c0a.el7.centos.noarch

Comment 6 Sandro Bonazzola 2017-12-20 10:55:37 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.