deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (Created) (JIRA)" <>
Subject [jira] [Created] (DTACLOUD-111) API and GUI still show 'start' as an option for Stopped Instance in EC2 - not available in AWS
Date Wed, 07 Dec 2011 21:04:39 GMT
API and GUI still show 'start' as an option for Stopped Instance in EC2 - not available in

                 Key: DTACLOUD-111
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server, Website
         Environment: Fedora 16, Firefox 7.0.1,
Executing API curl commands and checking in DeltaCloud GUI and AWS
            Reporter: Ronelle Landy
            Assignee: David Lutterkort

This issue may be related to DTACLOUD-8, DTACLOUD-9 or DTACLOUD-100

Provider EC2: After executing >> curl -X POST --user username:password http://host:3003/api/instances/i-3bcfc558/stop?format=xml

Querying the instance will show 'start' as an available action (this is not possible to do
from AWS). Executing >> curl -X POST  --user username:password http://host:3003/api/instances/i-3bcfc558/start?format=xml
will error out:


<error status='500' url='/api/instances/i-3bcfc558/start?format=xml'>
  <backend driver='ec2'>
  <message><![CDATA[start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver]]></message>


The GUI shows the instance as 'STOPPED' but also shows a 'start' button - even though this
is not supported.
AWS shows the instance as 'terminated' (possibly related to DTACLOUD-100)

If this is just a matter of time lag - ie: if waited long enough, the 'start' option would
no longer be there, then it would be helpful is there was some warning or indication that
change of status is happening.

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