diff options
| author | MotoKen <motokentsai@gmail.com> | 2012-09-14 11:51:15 +0800 |
|---|---|---|
| committer | MotoKen <motokentsai@gmail.com> | 2012-09-17 19:18:26 +0800 |
| commit | 632770e1314b9bdfede6df5b2b07d9e973cda6a8 (patch) | |
| tree | 98c8185dfdcf78b6efb2c59b179e072b5558093b /nova/openstack | |
| parent | 9536b3fa9861e4b9c93b5cf0a91451a92c5df92c (diff) | |
| download | nova-632770e1314b9bdfede6df5b2b07d9e973cda6a8.tar.gz nova-632770e1314b9bdfede6df5b2b07d9e973cda6a8.tar.xz nova-632770e1314b9bdfede6df5b2b07d9e973cda6a8.zip | |
Make DeregisterImage respect AWS EC2 specification
The return value of current deregister_image implementation is the AMI id.
Howerver, according to Amazon EC2 API documentation, the return value of
DeregisterImageResponse should be boolean.
See more detailed documentation in:
http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-DeregisterImage.html
The example response:
<DeregisterImageResponse xmlns="http://ec2.amazonaws.com/doc/2012-08-15/">
<requestId>59dbff89-35bd-4eac-99ed-be587EXAMPLE</requestId>
<return>true</return>
</DeregisterImageResponse>
This patch changes the response and test case for deregister_image.
Fixes bug 1051752.
Change-Id: Ifd31b88ec4f575f50244079cdeed4c9ff57206f8
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions