juju destroy-environment fails after a few machines have been deployed

[Dave Cheney]

provider: ec2

lucky(~/src/launchpad.net/juju-core) % juju bootstrap --upload-tools
lucky(~/src/launchpad.net/juju-core) % juju deploy mysql -n 10
lucky(~/src/launchpad.net/juju-core) % juju destroy-environment
error: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. (SignatureDoesNotMatch)

[Dave Cheney (dave-cheney)]

2012/10/05 10:27:13 get { https://ec2.us-east-1.amazonaws.com/?AWSAccessKeyId=AKIAJ4SOKUWG25EDMAOA&Action=TerminateInstances&InstanceId.1=i-4f9d0e32&InstanceId.10=i-cd8e1db0&InstanceId.11=i-658d1e18&InstanceId.2=i-4d841730&InstanceId.3=i-0184177c&InstanceId.4=i-218b185c&InstanceId.5=i-e78b189a&InstanceId.6=i-9d8b18e0&InstanceId.7=i-e98a1994&InstanceId.8=i-718f1c0c&InstanceId.9=i-eb8f1c96&Signature=xBtfi5FyQ1Fesx8bma8aLC6yJlYPwvcLT%2BbvXY0nIpE%3D&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-10-05T00%3A27%3A13Z&Version=2011-12-15 } -> {
2012/10/05 10:27:14 response:
2012/10/05 10:27:14 HTTP/1.1 403 Forbidden
Transfer-Encoding: chunked
Date: Fri, 05 Oct 2012 00:27:13 GMT
Server: AmazonEC2

17e
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.</Message></Error></Errors><RequestID>0ddd694e-a496-478a-98df-40bb4b76619a</RequestID></Response>
0

}
error: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. (SignatureDoesNotMatch)

[Dave Cheney (dave-cheney)]

Another datapoint, juju destroy-environment works fine with 6 machines.

[Dave Cheney (dave-cheney)]

The magic number is 9. More than 9 machines deployed means destroy-environment fails.

2012/10/05 12:10:41 get { https://ec2.us-east-1.amazonaws.com/?AWSAccessKeyId=AKIAJ4SOKUWG25EDMAOA&Action=TerminateInstances&InstanceId.1=i-63cc5e1e&InstanceId.10=i-0df46670&InstanceId.2=i-aff163d2&InstanceId.3=i-7ff66402&InstanceId.4=i-d5f664a8&InstanceId.5=i-9bf664e6&InstanceId.6=i-67f7651a&InstanceId.7=i-13f7656e&InstanceId.8=i-c1f765bc&InstanceId.9=i-65f46618&Signature=mOqy4COyy5vk9grQv553S2WYypunD%2F%2F6KhV2YwS0%2BYg%3D&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-10-05T02%3A10%3A41Z&Version=2011-12-15 } -> {
2012/10/05 12:10:41 response:
2012/10/05 12:10:41 HTTP/1.1 403 Forbidden
Transfer-Encoding: chunked
Date: Fri, 05 Oct 2012 02:10:40 GMT
Server: AmazonEC2

17e
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.</Message></Error></Errors><RequestID>36fdfd51-71ee-4990-a46f-9049b882195b</RequestID></Response>
0

}
error: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. (SignatureDoesNotMatch)

[Dave Cheney (dave-cheney)]

if I manually remove one machine using the AWS console to get under the limit, destroy-environment works again.

[Dave Cheney (dave-cheney)]

The reason 9 machines work and 10 machines fail is explained by this paste

http://play.golang.org/p/nvIA8fYPws

In short, the url to be signed is constructed by default sorting sorting the places machine 10 between machines 1 and 2.

 https://codereview.appspot.com/6642048/