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:
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?
I would rather say a regression introduced by the multi-pinning feature where a VM can be pinned to more than one host.
API or backend?
API - it looks the template up and maps its params to the new VM - it needs to map also this placement policy.
Verified on ovirt-engine-4.2.0-0.0.master.20170913112412.git2eb3c0a.el7.centos.noarch
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.