Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Wed, 1 Feb 2012 22:47:53 +0000 (UTC)
From: "Ronelle Landy (Created) (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <1227410433.26.1328136473765.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DTACLOUD-136) Deltacloud is not reporting back
 errors from Vsphere
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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