deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere
Date Thu, 02 Feb 2012 14:05:55 GMT


Michal Fojtik commented on DTACLOUD-136:

14:58 < mfojtik> the way how we launch an instances in vsphere is that we execute a
task but not wait for finish (it tooks too much time).. instead we create a YAML representation
of instance stored in vsphere datastore... this YAML instalce is reporting 'PENDING' until
the 'real' instance is being created
14:59 < mfojtik> rlandy: if the 'real' instance fail to create, the YAML one is removed
14:59 < mfojtik> rlandy: thus, this is not a bug but "limitation" of vsphere
15:00 < mfojtik> rlandy: also there is no way how to retrieve the error i'm afraid
> Deltacloud is not reporting back errors from Vsphere
> ----------------------------------------------------
>                 Key: DTACLOUD-136
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message