Bug 866985 – Cloned VM can't be placed on chosen storage domain

Bug 866985 - Cloned VM can't be placed on chosen storage domain

Summary:	Cloned VM can't be placed on chosen storage domain

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine-restapi (Show other bugs)
Sub Component:
Version:	3.1.0
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Pasternak
QA Contact:	Oded Ramraz
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-10-16 09:38 EDT by Petr Dufek
Modified:	2014-01-12 19:38 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-10-16 09:52:36 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
logs (944.63 KB, application/x-gzip) 2012-10-16 09:38 EDT, Petr Dufek	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Petr Dufek 2012-10-16 09:38:04 EDT

Created attachment 628162 [details]
logs

Description of problem:
When creating VM (clone VM from snapshot), final storage domain is stated. But VM is created then on different storage domain.

Version-Release number of selected component (if applicable):
rhevm-3.1.0-20.el6ev.noarch

How reproducible:
- send CREATE on rhevm/api/vms with body like:
<vm>
  :
  <snapshots>
    <snapshot id="..">
    :
  </snapshots>
  <storage_domain id="">
  :
  </storage_domain>
</vm>
  
Actual results:
VM on data_sd storage domain

Expected results:
VM on data_sd2 storage domain

Additional info:

Comment 1 Michael Pasternak 2012-10-16 09:52:36 EDT

Petr,

your syntax is wrong, storage domain set via disk

<vm>
<disks>
  <disk>
    <storage_domains>
      <storage_domain id=xxx>

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