cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Angus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-8065) Reinstall VM fails to restart instance in VMware
Date Mon, 12 Jan 2015 16:15:34 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Angus updated CLOUDSTACK-8065:
-----------------------------------
    Description: 
Error:
Unable to start VM with specified idUnable to start a VM due to insufficient capacity
Is returned when reinstalling a VM to original template state.

original disk is deleted, but upon startup the host tries to use the deleted disk instead
of the new disk.
Delete virtual machine  -  ROOT-366  -  Completed
Reconfigure virtual machine  -  CPBM1  -  File []/vmfs/volumes/536bc4-ed-d4f59724-e378-00e0-81b92cbe/CPBM1/ROOT-366.vmdk
was not found

A request to start the VM after this error successfully starts the guest vm..





  was:
Error:
Unable to start VM with specified idUnable to start a VM due to insufficient capacity
Is returned when reinstalling a VM to original template state.

original disk is deleted, but upon startup the host tries to deleted disk
Delete virtual machine  -  ROOT-366  -  Completed
Reconfigure virtual machine  -  CPBM1  -  File []/vmfs/volumes/536bc4-ed-d4f59724-e378-00e0-81b92cbe/CPBM1/ROOT-366.vmdk
was not found
request VM start after this error successfully starts the guest vm..






> Reinstall VM fails to restart instance in VMware
> ------------------------------------------------
>
>                 Key: CLOUDSTACK-8065
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8065
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Hypervisor Controller, Management Server
>    Affects Versions: 4.3.1
>         Environment: CloudStack 4.3.1 with VMware 5.5
>            Reporter: Paul Angus
>            Priority: Critical
>
> Error:
> Unable to start VM with specified idUnable to start a VM due to insufficient capacity
> Is returned when reinstalling a VM to original template state.
> original disk is deleted, but upon startup the host tries to use the deleted disk instead
of the new disk.
> Delete virtual machine  -  ROOT-366  -  Completed
> Reconfigure virtual machine  -  CPBM1  -  File []/vmfs/volumes/536bc4-ed-d4f59724-e378-00e0-81b92cbe/CPBM1/ROOT-366.vmdk
was not found
> A request to start the VM after this error successfully starts the guest vm..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message