Build failed in Jenkins: precise-adt-maas » amd64,maas-lenovo-lab #11

Jenkins Notification devnull at canonical.com
Mon Nov 26 11:45:53 UTC 2012 

See <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/11/>

------------------------------------------
[...truncated 1917 lines...]
Setting up erlang-xmerl (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-edoc (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-docbuilder (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-erl-docgen (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-eunit (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-ic (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-inviso (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-odbc (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-snmp (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-os-mon (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-parsetools (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-percept (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-ssh (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-webtool (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-tools (1:14.b.4-dfsg-1ubuntu1) ...
Setting up erlang-nox (1:14.b.4-dfsg-1ubuntu1) ...
Setting up rabbitmq-server (2.7.1-0ubuntu4) ...
Adding group `rabbitmq' (GID 116) ...
Done.
Adding system user `rabbitmq' (UID 109) ...
Adding new user `rabbitmq' (UID 109) with group `rabbitmq' ...
Not creating home directory `/var/lib/rabbitmq'.
Starting rabbitmq-server: SUCCESS
rabbitmq-server.
Setting up squid-langpack (20111114-1) ...
Setting up squid3-common (3.1.19-1ubuntu3.12.04.1) ...
Setting up squid3 (3.1.19-1ubuntu3.12.04.1) ...
Creating Squid HTTP proxy 3.x spool directory structure
2012/11/26 11:35:38| Creating Swap Directories
squid3 start/running, process 24923
Setting up squid (3.1.19-1ubuntu3.12.04.1) ...
Setting up squid-deb-proxy (0.6.3) ...
squid-deb-proxy start/running, process 25003
Setting up bind9 (1:9.8.1.dfsg.P1-4ubuntu0.4) ...
Adding group `bind' (GID 117) ...
Done.
Adding system user `bind' (UID 110) ...
Adding new user `bind' (UID 110) with group `bind' ...
Not creating home directory `/var/cache/bind'.
wrote key file "/etc/bind/rndc.key"
#
 * Starting domain name service... bind9
   ...done.
Setting up isc-dhcp-server (4.1.ESV-R4-0ubuntu5.6) ...
Generating /etc/default/isc-dhcp-server...
isc-dhcp-server start/running, process 25192
isc-dhcp-server6 stop/pre-start, process 25246
Setting up python-zookeeper (3.3.5+dfsg1-1ubuntu1) ...
Setting up maas-dhcp (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
maas-dhcp-server stop/waiting
Setting up python-nose (1.1.2-3) ...
Setting up python-testtools (0.9.14-0ubuntu1) ...
Processing triggers for python-twisted-core ...
Setting up python-twisted (11.1.0-1ubuntu2) ...
Setting up python-oops-twisted (0.0.6-0ubuntu2) ...
Setting up python-txamqp (0.5-0ubuntu2) ...
Setting up python-txtftp (0.1~bzr31-0ubuntu7~12.04.2~ppa1) ...
Setting up python-maas-provisioningserver (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
Setting up maas-cluster-controller (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
maas-pserv start/running, process 25474
maas-cluster-celery start/running, process 25505
Setting up python-txlongpoll (0.3.1+bzr86-0ubuntu1) ...
Setting up python-django-maas (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
Setting up maas-region-controller (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
Considering dependency proxy for proxy_http:
Enabling module proxy.
Enabling module proxy_http.
To activate the new configuration, you need to run:
  service apache2 restart
Enabling module expires.
To activate the new configuration, you need to run:
  service apache2 restart
Module wsgi already enabled
rsyslog stop/waiting
rsyslog start/running, process 25653
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 25702
Restarting rabbitmq-server: SUCCESS
rabbitmq-server.
Creating user "maas_longpoll" ...
...done.
Creating vhost "/maas_longpoll" ...
...done.
Setting permissions for user "maas_longpoll" in vhost "/maas_longpoll" ...
...done.
Creating user "maas_workers" ...
...done.
Creating vhost "/maas_workers" ...
...done.
Setting permissions for user "maas_workers" in vhost "/maas_workers" ...
...done.
 * Restarting PostgreSQL 9.1 database server
   ...done.
dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf

Creating config file /etc/dbconfig-common/maas-region-controller.conf with new version
creating postgres user maas:  success.
verifying creation of user: success.
creating database maasdb: success.
verifying database maasdb exists: success.
dbconfig-common: flushing administrative password
Syncing...
Creating tables ...
Creating table auth_permission
Creating table auth_group_permissions
Creating table auth_group
Creating table auth_user_user_permissions
Creating table auth_user_groups
Creating table auth_user
Creating table auth_message
Creating table django_content_type
Creating table django_session
Creating table django_site
Creating table piston_nonce
Creating table piston_consumer
Creating table piston_token
Creating table south_migrationhistory
Installing custom SQL ...
Installing indexes ...
No fixtures found.

Synced:
 > django.contrib.auth
 > django.contrib.contenttypes
 > django.contrib.sessions
 > django.contrib.sites
 > django.contrib.messages
 > django.contrib.staticfiles
 > piston
 > south

Not synced (use migrations):
 - maasserver
 - metadataserver
(use ./manage.py migrate to migrate these)
Running migrations for maasserver:
 - Migrating forwards to 0044_node_hostname_unique.
 > maasserver:0001_initial
 > maasserver:0002_add_token_to_node
 > maasserver:0002_macaddress_unique
 > maasserver:0003_rename_sshkeys
 > maasserver:0004_add_node_error
 > maasserver:0005_sshkey_user_and_key_unique_together
 > maasserver:0006_increase_filestorage_filename_length
 > maasserver:0007_common_info_created_add_time
 > maasserver:0008_node_power_address
 > maasserver:0009_add_nodegroup
 > maasserver:0010_add_node_netboot
 > maasserver:0011_add_dns_zone_serial_sequence
 > maasserver:0012_DHCPLease
 > maasserver:0013_connect_node_node_group
 > maasserver:0014_nodegroup_dhcp_settings_are_optional
 > maasserver:0016_node_nodegroup_not_null
 > maasserver:0017_add_dhcp_key_to_nodegroup
 > maasserver:0018_activate_worker_user
 > maasserver:0019_add_nodegroup_dhcp_interface
 > maasserver:0020_nodegroup_dhcp_interfaces_is_plural
 > maasserver:0021_add_uuid_to_nodegroup
 > maasserver:0022_add_status_to_nodegroup
 > maasserver:0023_add_bootimage_model
 > maasserver:0024_add_nodegroupinterface
 > maasserver:0025_remove_unused_fields_in_nodegroup
 > maasserver:0026_add_node_distro_series
 > maasserver:0027_add_tag_table
 > maasserver:0028_add_node_hardware_details
 > maasserver:0029_zone_sharing
 > maasserver:0030_ip_address_to_generic_ip_address
 > maasserver:0031_node_architecture_field_size
 > maasserver:0032_node_subarch
 > maasserver:0033_component_error
 > maasserver:0034_timestamp_component_error
 > maasserver:0035_add_nodegroup_cluster_name
 > maasserver:0036_populate_nodegroup_cluster_name
 > maasserver:0037_nodegroup_cluster_name_unique
 > maasserver:0038_nodegroupinterface_ip_range_fix
 > maasserver:0039_add_filestorage_content
 > maasserver:0039_add_nodegroup_to_bootimage
 > maasserver:0040_make_filestorage_data_not_null
 > maasserver:0041_remove_filestorage_data
 > maasserver:0042_fix_039_conflict
 > maasserver:0043_unique_hostname_preparation
 > maasserver:0044_node_hostname_unique
 - Loading initial data for maasserver.
No fixtures found.
Running migrations for metadataserver:
 - Migrating forwards to 0003_populate_hardware_details.
 > metadataserver:0001_initial
 > metadataserver:0002_add_nodecommissionresult
 > metadataserver:0003_populate_hardware_details
 - Loading initial data for metadataserver.
Installed 1 object(s) from 1 fixture(s)
 * Restarting web server apache2
apache2: apr_sockaddr_info_get() failed for autopkgtest
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
 ... waiting apache2: apr_sockaddr_info_get() failed for autopkgtest
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
   ...done.
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 26767
maas-txlongpoll start/running, process 26833
maas-region-celery start/running, process 26894
Setting up maas (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
Setting up python-txzookeeper (0.9.5-0ubuntu1) ...
Setting up python-txaws (0.2-0ubuntu10) ...
Setting up juju (0.5+bzr531-0ubuntu1.3) ...
Setting up maas-dns (0.1+bzr1314+dfsg-0ubuntu1~ppa1) ...
 * Stopping domain name service... bind9
waiting for pid 25127 to die
   ...done.
 * Starting domain name service... bind9
   ...done.
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for python-support ...
 -> Finished parsing the build-deps
adt-run: trace: & ubtree0t-maas-package-test: [----------------------------------------
qemu: terminating on signal 15 from pid 8042
Connection to localhost closed by remote host.
+ RET=255
+ [ 0 -eq 1 ]
+ [ 255 -gt 0 ]
+ log_failure_msg adt-run exited with status 255.
+ log_msg Failure: adt-run exited with status 255.\n
+ date +%F %X
+ printf 2012-11-26 06:44:07: Failure: adt-run exited with status 255.\n
2012-11-26 06:44:07: Failure: adt-run exited with status 255.
+ [ 0 -eq 0 ]
+ mkdir -p <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -p 54322 -t -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /home/ubuntu/adt-log; find /home/ubuntu/adt-log -type f -empty | xargs rm
Pseudo-terminal will not be allocated because stdin is not a terminal.
ssh: connect to host localhost port 54322: Connection refused
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2012-11-26 06:44:07: Info: Cleaning up\n
2012-11-26 06:44:07: Info: Cleaning up
+ [ -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20121126_063010.img.pid ]
+ cat /var/tmp/adt/jenkins/disks/precise-amd64-maas-20121126_063010.img.pid
+ kill -9 7000
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20121126_063010.img.pid
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20121126_063010.img
+ rm -f /var/lock/adt/ssh.54322.lock
+ rm -f /var/lock/adt/vnc.6186.lock
+ [ -d /tmp/adt-amd64.7Vqd9h ]
+ rm -Rf /tmp/adt-amd64.7Vqd9h
+ exit 255
Build step 'Execute shell' marked build as failure
Archiving artifacts

More information about the ubuntu-testing-notifications mailing list