Bug 800805 - [ovirt-engine-core] Can not run VM that was created from imported template
Summary: [ovirt-engine-core] Can not run VM that was created from imported template
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 10:13 UTC by Kiril Nesenko
Modified: 2014-07-11 00:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-12 10:42:58 UTC
oVirt Team: ---

Attachments (Terms of Use)
logs (9.61 KB, application/x-bzip)
2012-03-07 10:13 UTC, Kiril Nesenko 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.