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

Jenkins Notification devnull at canonical.com
Thu Sep 5 08:40:49 UTC 2013 

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

------------------------------------------
Started by upstream project "lucid-server-ec2-daily" build number 172
[EnvInject] - Loading node environment variables.
Building remotely on ec2-tester
[ubuntu-server-ec2-testing] $ /bin/sh -xe /tmp/hudson7598611557850370833.sh
+ echo Running Test amd64 eu-west-1 instance-store for current daily build.
Running Test amd64 eu-west-1 instance-store for current daily build.
+ 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 -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-f1aab085 
INFO:root:Number of TestCaseExecutors to implement: 1
INFO:root:Executing 
        AMI: ami-f1aab085
            - #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-f1aab085 of size m1.large in region eu-west-1 (None)
INFO:root:Instances requested, reservation instances [Instance:i-ce41bc81]
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
# ec2-54-228-60-51.eu-west-1.compute.amazonaws.com SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7
# ec2-54-228-60-51.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.35.169.117' 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
INFO:root:Current testing phase: 2
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130905-0811-7185a06abae044.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-ce41bc81/host.keys', 'root at ec2-54-228-60-51.eu-west-1.compute.amazonaws.com', 'echo Hello World']
ssh: connect to host ec2-54-228-60-51.eu-west-1.compute.amazonaws.com port 22: Connection timed out
DEBUG:root:Cmd output: 
DEBUG:root:Cmd: ['ssh', '-i', 'uec2-20130905-0811-7185a06abae044.pem', '-o', 'UserKnownHostsFile=None/amd64/m1.large/instance-store/i-ce41bc81/host.keys', 'ubuntu at ec2-54-228-60-51.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-228-60-51.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
WARNING:root:These instances did not terminate: [u'i-ce41bc81']
ERROR:boto:400 Bad Request
ERROR:boto:<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidGroup.InUse</Code><Message>There are active instances using security group 'uec2-20130905-0811-7185a06abae044'</Message></Error></Errors><RequestID>ea171bb2-4d61-4a50-9d97-773fab557e94</RequestID></Response>
Traceback (most recent call last):
  File "/usr/bin/execute-ubuntu-ec2-test", line 160, in <module>
    success = tce.execute_test()
  File "/usr/share/ubuntu-server-ec2-testing/python/ubuntu/ec2/testing.py", line 313, in execute_test
    self.tidyup()
  File "/usr/share/ubuntu-server-ec2-testing/python/ubuntu/ec2/testing.py", line 517, in tidyup
    self.security.delete()
  File "/usr/lib/python2.7/dist-packages/boto/ec2/securitygroup.py", line 80, in delete
    return self.connection.delete_security_group(self.name)
  File "/usr/lib/python2.7/dist-packages/boto/ec2/connection.py", line 1773, in delete_security_group
    return self.get_status('DeleteSecurityGroup', params, verb='POST')
  File "/usr/lib/python2.7/dist-packages/boto/connection.py", line 718, in get_status
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidGroup.InUse</Code><Message>There are active instances using security group 'uec2-20130905-0811-7185a06abae044'</Message></Error></Errors><RequestID>ea171bb2-4d61-4a50-9d97-773fab557e94</RequestID></Response>
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results

More information about the ubuntu-testing-notifications mailing list