Bug 800805

Summary: [ovirt-engine-core] Can not run VM that was created from imported template
Product: [Retired] oVirt Reporter: Kiril Nesenko <knesenko>
Component: ovirt-engine-coreAssignee: lpeer <lpeer>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, dfediuck, iheim, michal.skrivanek, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-12 10:42:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
logs none

Description Kiril Nesenko 2012-03-07 10:13:25 UTC
Created attachment 568224 [details]
logs

Description of problem:
Can not run VM that was created from template

2012-03-07 10:47:49,741 WARN  [org.ovirt.engine.core.bll.RunVmOnceCommand] (http--0.0.0.0-8443-1) [27ba217b] CanDoAction of action RunVmOnce failed. Reasons:
VAR__ACTION__RUN,VAR__TYPE__VM,VM_CANNOT_RUN_FROM_DISK_WITHOUT_PLUGGED_DISK
2012-03-07 10:47:49,753 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (http--0.0.0.0-8443-1) Operation Failed: [Cannot run VM without
 at least one active disk.
Please activate a disk and rerun the VM.]



Version-Release number of selected component (if applicable):
ovirt-engine-backend-3.0.0_0001-3.git4364f1b.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Create a Vm from template and try to run it.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Kiril Nesenko 2012-03-07 10:43:44 UTC
Steps to reproduce:
1. Create a template and import it to another DC.
2. In that DC try to create a VM from that template and try to run it.

Comment 2 Itamar Heim 2012-12-12 10:42:58 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.