Build failed in Jenkins: lucid-server-ec2 » amd64,eu-west-1,instance-store,simple-user-data,ubuntu-server-ec2-testing #24

Jenkins Notification devnull at canonical.com
Mon Sep 9 09:32:51 UTC 2013 

See <http://10.189.74.2:8080/job/lucid-server-ec2/./ARCH=amd64,REGION=eu-west-1,STORAGE=instance-store,TEST=simple-user-data,label=ubuntu-server-ec2-testing/24/>

------------------------------------------
Started by upstream project "lucid-server-ec2" build number 24
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson5528125769225042153.sh
+ echo Running Test amd64 eu-west-1 instance-store simple-user-data current
Running Test amd64 eu-west-1 instance-store simple-user-data current
+ rm -Rf *
+ 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 73 revision(s).
+ execute-ubuntu-ec2-test -r eu-west-1 -s instance-store -b current -a amd64 -R lucid -t tests simple-user-data
INFO:root:Creating test for size:m1.large for arch:amd64 in region:eu-west-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-4af91c3d 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-4af91c3d
            - #instances: 1
            - size: m1.large
            - region: eu-west-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-4af91c3d of size m1.large in region eu-west-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-52b8971d]
INFO:root:Waiting for reservation to complete
INFO:root:Monitoring for test completion
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
# ec2-54-246-49-53.eu-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-246-49-53.eu-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '10.34.155.30' to the list of known hosts.
cp: cannot stat `/var/log/cloud-init.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init.log
ssh: connect to host ec2-54-246-49-53.eu-west-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130909-0848-32570d455b324e.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-52b8971d/host.keys', 'root at ec2-54-246-49-53.eu-west-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-246-49-53.eu-west-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output: 
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130909-0848-32570d455b324e.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-52b8971d/host.keys', 'ubuntu at ec2-54-246-49-53.eu-west-1.compute.amazonaws.com', 'echo Hello World']
DEBUG:root:Cmd output: Hello World

INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-246-49-53.eu-west-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-246-49-53.eu-west-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-246-49-53.eu-west-1.compute.amazonaws.com port 22: Connection timed out
ERROR:root:Something bad happened Unable to execute in-instance tests.
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-4af91c3d
            - #instances: 1
            - size: m1.large
            - region: eu-west-1 
            - placement: None 
            - arch: amd64 
            - storage: instance-store
        
INFO:root:Instance: i-52b8971d Completed: False Errors: False Phase: 3 Keyscan: None
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