Build failed in Jenkins: lucid-server-ec2 » amd64,ap-northeast-1,instance-store,multi-instance,ubuntu-server-ec2-testing #19
Jenkins Notification
devnull at canonical.com
Thu May 16 07:26:39 UTC 2013
See <http://10.189.74.2:8080/job/lucid-server-ec2/./ARCH=amd64,REGION=ap-northeast-1,STORAGE=instance-store,TEST=multi-instance,label=ubuntu-server-ec2-testing/19/>
------------------------------------------
Started by upstream project "lucid-server-ec2" build number 19
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson5774254643446959307.sh
+ echo Running Test amd64 ap-northeast-1 instance-store multi-instance current
Running Test amd64 ap-northeast-1 instance-store multi-instance current
+ rm -Rf None i-0072a402_test_remote.pyc i-0272a400_test_remote.pyc i-0472a406_test_remote.pyc i-0672a404_test_remote.pyc i-0872a40a_test_remote.pyc i-0a72a408_test_remote.pyc i-0e72a40c_test_remote.pyc i-f875a3fa_test_remote.pyc i-fc75a3fe_test_remote.pyc i-fe75a3fc_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 69 revision(s).
+ execute-ubuntu-ec2-test -r ap-northeast-1 -s instance-store -b current -a amd64 -R lucid -t tests multi-instance
INFO:root:Creating test for size:m1.large for arch:amd64 in region:ap-northeast-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-3fa9273e
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing
AMI: ami-3fa9273e
- #instances: 10
- size: m1.large
- region: ap-northeast-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 10 instance for ami ami-3fa9273e of size m1.large in region ap-northeast-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-0e45f30c, Instance:i-0c45f30e, Instance:i-1245f310, Instance:i-1045f312, Instance:i-1645f314, Instance:i-1445f316, Instance:i-1a45f318, Instance:i-1845f31a, Instance:i-1e45f31c, Instance:i-1c45f31e]
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
# ec2-54-248-169-7.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-248-169-7.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '54.248.169.7' 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
cp: cannot stat `/var/log/cloud-init-output.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init-output.log
INFO:root:Current testing phase: 1
# ec2-54-250-44-19.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-250-44-19.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '54.250.44.19' 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
cp: cannot stat `/var/log/cloud-init-output.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init-output.log
INFO:root:Current testing phase: 1
# ec2-54-250-31-209.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-250-31-209.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '54.250.31.209' 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
cp: cannot stat `/var/log/cloud-init-output.log': No such file or directory
FAIL: failed to copy /var/log/cloud-init-output.log
INFO:root:Current testing phase: 1
# ec2-54-248-55-11.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-248-55-11.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '54.248.55.11' to the list of known hosts.
Connection to ec2-54-248-55-11.ap-northeast-1.compute.amazonaws.com closed by remote host.
INFO:root:Current testing phase: 1
# ec2-176-34-6-205.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 176.34.6.205
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
# ec2-175-41-234-230.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 175.41.234.230
INFO:root:Current testing phase: 1
read (ec2-54-249-164-250.ap-northeast-1.compute.amazonaws.com): Connection reset by peer
read (ec2-54-249-164-250.ap-northeast-1.compute.amazonaws.com): Connection reset by peer
INFO:root:Current testing phase: 1
# ec2-54-250-0-255.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 54.250.0.255
INFO:root:Current testing phase: 1
# ec2-176-34-10-136.ap-northeast-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 176.34.10.136
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-0e45f30c/host.keys', 'root at ec2-54-248-169-7.ap-northeast-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-248-169-7.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output:
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-0e45f30c/host.keys', 'ubuntu at ec2-54-248-169-7.ap-northeast-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-248-169-7.ap-northeast-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output:
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-0c45f30e/host.keys', 'root@', 'echo Hello World']
ssh: Could not resolve hostname : Name or service not known
DEBUG:root:Cmd output:
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-0c45f30e/host.keys', 'ubuntu@', 'echo Hello World']
ssh: Could not resolve hostname : Name or service not known
DEBUG:root:Cmd output:
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-1245f310/host.keys', 'root@', 'echo Hello World']
ssh: Could not resolve hostname : Name or service not known
DEBUG:root:Cmd output:
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-1245f310/host.keys', 'ubuntu@', 'echo Hello World']
ssh: Could not resolve hostname : Name or service not known
DEBUG:root:Cmd output:
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-1045f312/host.keys', 'root@', 'echo Hello World']
ssh: Could not resolve hostname : Name or service not known
DEBUG:root:Cmd output:
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0713-08a855c9ee0b44.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-1045f312/host.keys', 'ubuntu@', 'echo Hello World']
ssh: Could not resolve hostname : Name or service not known
DEBUG:root:Cmd output:
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: 3
ssh: Could not resolve hostname : Name or service not known
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-3fa9273e
- #instances: 10
- size: m1.large
- region: ap-northeast-1
- placement: None
- arch: amd64
- storage: instance-store
INFO:root:Instance: i-0e45f30c Completed: False Errors: False Phase: 3 Keyscan: None
INFO:root:Instance: i-0c45f30e Completed: False Errors: False Phase: 3 Keyscan: None
INFO:root:Instance: i-1245f310 Completed: False Errors: False Phase: 3 Keyscan: None
INFO:root:Instance: i-1045f312 Completed: False Errors: False Phase: 3 Keyscan: None
INFO:root:Instance: i-1645f314 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1445f316 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1a45f318 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1845f31a Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1e45f31c Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1c45f31e Completed: False Errors: False Phase: 1 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