Linaro AMI list feature returns status 400
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro AWS Tools |
Invalid
|
High
|
Stevan Radaković |
Bug Description
$ ./linaro-ami list
Name ID Created Status
Description
-------
ERROR:boto:400 Bad Request
ERROR:boto:<?xml version="1.0" encoding="UTF-8"?>
<Response>
(None) for parameter snapshotId is invalid. Expected:
'snap-.
Traceback (most recent call last):
File "./linaro-ami", line 63, in <module>
controller.
File "/home/
line 133, in command_list
self.
File "/home/
line 100, in get_image_
snapshots = self._connectio
File "/usr/lib/
1456, in get_all_snapshots
[('item', Snapshot)], verb='POST')
File "/usr/lib/
896, in get_list
raise self.ResponseEr
boto.exception.
<?xml version="1.0" encoding="UTF-8"?>
<Response>
(None) for parameter snapshotId is invalid. Expected:
'snap-.
This is glitch on EC2 side, uncovering mishandling in Boto:
ami-xxxxxxxx:
/dev/sda1=
description: | updated |
Changed in linaro-aws-tools: | |
milestone: | 2012.08 → 2012.09 |
Changed in linaro-aws-tools: | |
milestone: | 2012.09 → none |
status: | Triaged → Incomplete |
Changed in linaro-aws-tools: | |
status: | Incomplete → Invalid |
This bug is not reproducible anymore, the AMI on the AWS Console is either removed or it simply doesn't cause problems no more.