Build failed in Jenkins: lucid-server-ec2-daily » i386,us-east-1,instance-store,proposed,ubuntu-server-ec2-testing #121

[Jenkins Notification]

See <http://10.189.74.2:8080/job/lucid-server-ec2-daily/./ARCH=i386,REGION=us-east-1,STORAGE=instance-store,TEST=proposed,label=ubuntu-server-ec2-testing/121/>

------------------------------------------
Started by upstream project "lucid-server-ec2-daily" build number 121
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson3229385789235644521.sh
+ echo Running Test i386 us-east-1 instance-store for current daily build.
Running Test i386 us-east-1 instance-store for current daily build.
+ rm -Rf tests
+ bzr branch lp:~ubuntu-server-ec2-testing-dev/+junk/ec2-automated-tests tests
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data.  See "bzr help launchpad-login".
Branched 68 revision(s).
+ execute-ubuntu-ec2-test -r us-east-1 -s instance-store -a i386 -R lucid -t tests proposed
INFO:root:Creating test for size:m1.small for arch:i386 in region:us-east-1 placement:any root storage:instance-store
INFO:root:Retieving ec2 AMI informfation from http://uec-images.ubuntu.com/query/lucid/server/daily.current.txt
INFO:root:Found AMI ami-dc1d81b5 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-dc1d81b5
            - #instances: 1
            - size: m1.small
            - region: us-east-1 
            - placement: None 
            - arch: i386 
            - storage: instance-store
        
INFO:root:Creating ec2 Connection
INFO:root:Creating keypair for test
INFO:root:Creating security group for test
INFO:root:Starting instances
INFO:root:Executing 1 instance for ami ami-dc1d81b5 of size m1.small in region us-east-1 (None)
ERROR:boto:400 Bad Request
ERROR:boto:<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InstanceLimitExceeded</Code><Message>50 instance(s) are already running.</Message></Error></Errors><RequestID>8c33dc04-0085-42d5-ae85-5b0820888157</RequestID></Response>
ERROR:root:Unable to complete reservation EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InstanceLimitExceeded</Code><Message>50 instance(s) are already running.</Message></Error></Errors><RequestID>8c33dc04-0085-42d5-ae85-5b0820888157</RequestID></Response>
ERROR:root:Something bad happened Unable to complete reservation EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InstanceLimitExceeded</Code><Message>50 instance(s) are already running.</Message></Error></Errors><RequestID>8c33dc04-0085-42d5-ae85-5b0820888157</RequestID></Response>
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-dc1d81b5
            - #instances: 1
            - size: m1.small
            - region: us-east-1 
            - placement: None 
            - arch: i386 
            - storage: instance-store
        
INFO:root:

Test Summary:
    Tests to Execute: 1
    Tests Completed: 0
    Tests Failed: 1
    Total Tests Executed: 1


ERROR:root:At least one test case execution failed - please investigate.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results