Build failed in Jenkins: oneiric-server-ec2-daily » amd64,us-east-1,instance-store,proposed,ubuntu-server-ec2-testing #127

[Jenkins Notification]

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

------------------------------------------
Started by upstream project "oneiric-server-ec2-daily" build number 127
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson7836843580288802306.sh
+ echo Running Test amd64 us-east-1 instance-store for current daily build.
Running Test amd64 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 amd64 -R oneiric -t tests proposed
INFO:root:Creating test for size:m1.large for arch:amd64 in region:us-east-1 placement:any root storage:instance-store
INFO:root:Retieving ec2 AMI informfation from http://uec-images.ubuntu.com/query/oneiric/server/daily.current.txt
INFO:root:Found AMI ami-9e52cff7 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-9e52cff7
            - #instances: 1
            - size: m1.large
            - region: us-east-1 
            - placement: None 
            - arch: amd64 
            - 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-9e52cff7 of size m1.large 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>2a0ce59f-fee9-4e4a-8fec-59e9b0a87da4</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>2a0ce59f-fee9-4e4a-8fec-59e9b0a87da4</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>2a0ce59f-fee9-4e4a-8fec-59e9b0a87da4</RequestID></Response>
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-9e52cff7
            - #instances: 1
            - size: m1.large
            - region: us-east-1 
            - placement: None 
            - arch: amd64 
            - 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