You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ronelle Landy (Updated) (JIRA)" <ji...@apache.org> on 2012/02/01 23:49:53 UTC
[jira] [Updated] (DTACLOUD-136) Deltacloud is not reporting back
errors from Vsphere
[ https://issues.apache.org/jira/browse/DTACLOUD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy updated DTACLOUD-136:
-----------------------------------
Attachment: vsphereConsole.png
> Deltacloud is not reporting back errors from Vsphere
> ----------------------------------------------------
>
> Key: DTACLOUD-136
> URL: https://issues.apache.org/jira/browse/DTACLOUD-136
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud-core-0.5.0
> Vsphere 5.x
> Reporter: Ronelle Landy
> Assignee: David Lutterkort
> Attachments: vsphereConsole.png
>
>
> Creating an instance from an image in Deltacloud did not succeed but produced no error, backtrace or any other feedback.
> Trying to launch an instance from the same image using the Vsphere console returned the following error:
> "asdftg-RHELVsphereInstance .vmx was not found
> An unexpected error was received from the ESX host while powering on VM vm-123"
> ( See attached screenshot for full error)
> Deltacloud should return this error to the user.
> In addition, if instances created from images (now missing .vmx) already exist in the datastore, Deltacloud cannot start these instances. Again, the start operation doesn't throw an error, the instance just remains in a stopped state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira