Build failed in Jenkins: raring-server-ec2-daily » amd64, us-east-1,ebs,simple-user-data,ubuntu-server-ec2-testing #35

Jenkins Notification devnull at canonical.com
Wed Mar 6 19:44:14 UTC 2013


See <http://10.189.74.2:8080/job/raring-server-ec2-daily/./ARCH=amd64,REGION=us-east-1,STORAGE=ebs,TEST=simple-user-data,label=ubuntu-server-ec2-testing/35/>

------------------------------------------
Started by upstream project "raring-server-ec2-daily" build number 35
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson4799651651344926882.sh
+ echo Running Test amd64 us-east-1 ebs for current daily build.
Running Test amd64 us-east-1 ebs 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 ebs -a amd64 -R raring -t tests simple-user-data
INFO:root:Creating test for size:m1.large for arch:amd64 in region:us-east-1 placement:any root storage:ebs
INFO:root:Retieving ec2 AMI informfation from http://uec-images.ubuntu.com/query/raring/server/daily.current.txt
INFO:root:Found AMI ami-c6a73baf 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-c6a73baf
            - #instances: 1
            - size: m1.large
            - region: us-east-1 
            - placement: None 
            - arch: amd64 
            - storage: ebs
        
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-c6a73baf 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>da1b00c2-0d67-4f6a-b037-cca7f0f33040</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>da1b00c2-0d67-4f6a-b037-cca7f0f33040</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>da1b00c2-0d67-4f6a-b037-cca7f0f33040</RequestID></Response>
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-c6a73baf
            - #instances: 1
            - size: m1.large
            - region: us-east-1 
            - placement: None 
            - arch: amd64 
            - storage: ebs
        
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



More information about the ubuntu-testing-notifications mailing list