Build failed in Jenkins: lucid-server-ec2 » amd64,us-west-1,instance-store,multi-instance,ubuntu-server-ec2-testing #19
Jenkins Notification
devnull at canonical.com
Thu May 16 07:28:56 UTC 2013
See <http://10.189.74.2:8080/job/lucid-server-ec2/./ARCH=amd64,REGION=us-west-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/hudson544443212543216076.sh
+ echo Running Test amd64 us-west-1 instance-store multi-instance current
Running Test amd64 us-west-1 instance-store multi-instance current
+ rm -Rf None i-90503ac8_test_remote.pyc i-92503aca_test_remote.pyc i-94503acc_test_remote.pyc i-98503ac0_test_remote.pyc i-9a503ac2_test_remote.pyc i-9c503ac4_test_remote.pyc i-9e503ac6_test_remote.pyc i-e2503aba_test_remote.pyc i-e4503abc_test_remote.pyc i-e6503abe_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 us-west-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:us-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-e9ba95ac
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing
AMI: ami-e9ba95ac
- #instances: 10
- size: m1.large
- region: us-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 10 instance for ami ami-e9ba95ac of size m1.large in region us-west-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-181b4140, Instance:i-1a1b4142, Instance:i-1c1b4144, Instance:i-1e1b4146, Instance:i-101b4148, Instance:i-121b414a, Instance:i-141b414c, Instance:i-161b414e, Instance:i-081b4150, Instance:i-0a1b4152]
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
# ec2-54-241-232-29.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-241-232-29.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Warning: Permanently added the RSA host key for IP address '54.241.232.29' to the list of known hosts.
Connection to ec2-54-241-232-29.us-west-1.compute.amazonaws.com closed by remote host.
INFO:root:Current testing phase: 1
# ec2-54-215-103-251.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Read from socket failed: Connection reset by peer
# ec2-54-215-103-251.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 54.215.103.251
INFO:root:Current testing phase: 1
# ec2-54-241-193-31.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 54.241.193.31
INFO:root:Current testing phase: 1
# ec2-50-18-15-132.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 50.18.15.132
INFO:root:Current testing phase: 1
# ec2-50-18-94-69.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 50.18.94.69
INFO:root:Current testing phase: 1
read (ec2-54-241-214-254.us-west-1.compute.amazonaws.com): Connection reset by peer
read (ec2-54-241-214-254.us-west-1.compute.amazonaws.com): Connection reset by peer
INFO:root:Current testing phase: 1
# ec2-50-18-143-237.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 50.18.143.237
INFO:root:Current testing phase: 1
# ec2-54-241-118-171.us-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
Connection closed by 54.241.118.171
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 1
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0722-b5ac139eaec749.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-1c1b4144/host.keys', 'root at ec2-54-241-232-29.us-west-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-241-232-29.us-west-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output:
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130516-0722-b5ac139eaec749.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-1c1b4144/host.keys', 'ubuntu at ec2-54-241-232-29.us-west-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-241-232-29.us-west-1.compute.amazonaws.com port 22: Connection timed out
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: 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-e9ba95ac
- #instances: 10
- size: m1.large
- region: us-west-1
- placement: None
- arch: amd64
- storage: instance-store
INFO:root:Instance: i-181b4140 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1a1b4142 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-1c1b4144 Completed: False Errors: False Phase: 3 Keyscan: None
INFO:root:Instance: i-1e1b4146 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-101b4148 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-121b414a Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-141b414c Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-161b414e Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-081b4150 Completed: False Errors: False Phase: 1 Keyscan: None
INFO:root:Instance: i-0a1b4152 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