=?UTF-8?Q?Build_failed_in_Jenkins:_quantal-server-ec2_=C2=BB_amd64, ap-nor?= =?UTF-8?Q?theast-1, ebs, simple-user-data, ubuntu-server-ec2-testing_#11?=

Jenkins Notification devnull at canonical.com
Wed Aug 29 14:30:23 UTC 2012 

See <http://10.189.74.2:8080/job/quantal-server-ec2/./ARCH=amd64,REGION=ap-northeast-1,STORAGE=ebs,TEST=simple-user-data,label=ubuntu-server-ec2-testing/11/>

------------------------------------------
Started by upstream project "quantal-server-ec2" build number 11
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson7102514083338288835.sh
+ echo Running Test amd64 ap-northeast-1 ebs simple-user-data current
Running Test amd64 ap-northeast-1 ebs simple-user-data current
+ rm -Rf None i-7fa7b97f_test_remote.pyc 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 67 revision(s).
+ execute-ubuntu-ec2-test -r ap-northeast-1 -s ebs -b current -a amd64 -R quantal -t tests simple-user-data
INFO:root:Creating test for size:m1.large for arch:amd64 in region:ap-northeast-1 placement:any root storage:ebs
INFO:root:Retieving ec2 AMI informfation from http://uec-images.ubuntu.com/query/quantal/server/daily.current.txt
INFO:root:Found AMI ami-a40db0a5 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-a40db0a5
            - #instances: 1
            - size: m1.large
            - region: ap-northeast-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-a40db0a5 of size m1.large in region ap-northeast-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-a1243da1]
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
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
INFO:root:Current testing phase: 1
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
INFO:root:Current testing phase: 1
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
INFO:root:Current testing phase: 1
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
INFO:root:Current testing phase: 1
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
INFO:root:Current testing phase: 1
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
# ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_6.0p1 Debian-2ubuntu1
Warning: Permanently added the RSA host key for IP address '54.248.62.61' to the list of known hosts.
ssh: connect to host ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20120829-1359-0d83ce50735e4a.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/ebs/i-a1243da1/host.keys', 'root at ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com', 'echo Hello World']
DEBUG:root:Cmd output: Please login as the user "ubuntu" rather than the user "root".


DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20120829-1359-0d83ce50735e4a.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/ebs/i-a1243da1/host.keys', 'ubuntu at ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output: 
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
INFO:root:Current testing phase: 3
ssh: connect to host ec2-54-248-62-61.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
lost connection
ERROR:root:Something bad happened Unable to deploy test executor to instance
INFO:root:Tidyup test
INFO:root:Testing failed for 
        AMI: ami-a40db0a5
            - #instances: 1
            - size: m1.large
            - region: ap-northeast-1 
            - placement: None 
            - arch: amd64 
            - storage: ebs
        
INFO:root:Instance: i-a1243da1 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