API and GUI still show 'start' as an option for Stopped Instance in EC2 - not
available in AWS
----------------------------------------------------------------------------------------------
Key: DTACLOUD-111
URL: https://issues.apache.org/jira/browse/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 RESPONSE %%%
<error status='500' url='/api/instances/i-3bcfc558/start?format=xml'>
<kind>backend_error</kind>
<backend driver='ec2'>
<code>500</code>
</backend>
<message><![CDATA[start_instance capability not supported by backend
Deltacloud::Drivers::EC2::EC2Driver]]></message>
</error>
%%%
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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
