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 (Created) (JIRA)" <ji...@apache.org> on 2012/02/01 23:47:53 UTC

[jira] [Created] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere

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

        

[jira] [Closed] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere

Posted by "Ronelle Landy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DTACLOUD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronelle Landy closed DTACLOUD-136.
----------------------------------


Closing this issue ... verified doc noted copied below:

Note:

The Deltacloud does not report potential errors, if you are creating an instance in vSphere. When you launch an instance, Deltacloud does not wait until the task is finished. Instead of that, Deltacloud creates a YAML representation of the instance in vSphere datastore. The YAML instance is in a 'PENDING' state until the 'real' instance is created. If the real instance fails to create, the YAML representation is removed. However, Deltacloud does not send you any error message. 
                
> 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: Dagmar Husarova
>         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

        

[jira] [Commented] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere

Posted by "Michal Fojtik (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DTACLOUD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198800#comment-13198800 ] 

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: 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

        

[jira] [Updated] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere

Posted by "Ronelle Landy (Updated) (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Resolved] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere

Posted by "Dagmar Husarova (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DTACLOUD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dagmar Husarova resolved DTACLOUD-136.
--------------------------------------

    Resolution: Fixed

added to nanoc site to API --> REST API --> Compute resources --> Instances --> Create an instance
                
> 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: Dagmar Husarova
>         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

        

[jira] [Assigned] (DTACLOUD-136) Deltacloud is not reporting back errors from Vsphere

Posted by "Ronelle Landy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DTACLOUD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronelle Landy reassigned DTACLOUD-136:
--------------------------------------

    Assignee: Dagmar Husarova  (was: David Lutterkort)

Assigning to doc as per mfojtik's comment:

>> DTACLOUD-136   Deltacloud is not reporting back errors from Vsphere 
 Need to be documented (dhusarov)
                
> 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: Dagmar Husarova
>         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