[
https://issues.apache.org/jira/browse/DTACLOUD-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-254.
----------------------------------
Verified in deltacloud commit version: dfa9c3535f0705ead13a18e0016ca6333b74a6c4
. Test results are included below:
>> ./bin/deltacloudd -i mock -r <server> -p 3009
>> curl -X GET -H "X-Deltacloud-Driver:ec2" -H
>> "X-Deltacloud-Provider:us-east-1" --user "un;pw5"
>> "http://nec-em16.rhts.eng.bos.redhat.com:3009/api/addresses?format=xml";
<?xml version='1.0' encoding='utf-8' ?>
<addresses>
<address
href='http://nec-em16.rhts.eng.bos.redhat.com:3009/api/addresses/23.23.228.199'
id='23.23.228.199'>
<ip>23.23.228.199</ip>
<actions>
<link
href='http://nec-em16.rhts.eng.bos.redhat.com:3009/api/addresses/23.23.228.199'
method='delete' rel='destroy' />
<link
href='http://nec-em16.rhts.eng.bos.redhat.com:3009/api/disassociate_addresses/23.23.228.199'
method='post' rel='disassociate' />
</actions>
<instance
href='http://nec-em16.rhts.eng.bos.redhat.com:3009/api/instances/i-5f31ae24'
id='i-5f31ae24'></instance>
</address>
</addresses>
> EC2 and Eucalyptus driver GET-request errors
> --------------------------------------------
>
> Key: DTACLOUD-254
> URL: https://issues.apache.org/jira/browse/DTACLOUD-254
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: ruby1.8, deltacloud-core-1.0.0, deltacloud-core-head
> Reporter: Christian Karnath
> Assignee: Michal Fojtik
>
> If deltacloudd is not started with the ec2 or eucalyptus driver (i. e.
> deltacloudd -i mock) and the driver is changed via X-Deltacloud-Driver to ec2
> or eucalyptus, the following errors will occur:
> /api/firewalls
> -> The required capability to execute this operation is missing
> /api/addresses
> -> The required capability to execute this operation is missing
> /api/realms/<realm>
> -> Not Found
> /api/images/<image>
> -> Not Found
> /api/keys/<key>
> -> Not Found
--
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
