Build failed in Jenkins: quantal-adt-maas » amd64,maas-lenovo-lab #55

Jenkins Notification devnull at canonical.com
Mon Oct 29 22:04:33 UTC 2012 

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

------------------------------------------
[...truncated 1570 lines...]
update-alternatives: using /usr/share/docutils/scripts/python2/rstpep2html to provide /usr/bin/rstpep2html (rstpep2html) in auto mode
Setting up python-sphinx (1.1.3+dfsg-4ubuntu3) ...
Processing triggers for ureadahead ...
Setting up maas-dhcp (0.1+bzr1269+dfsg-0~1307~quantal1) ...
maas-dhcp-server stop/waiting
Setting up python-maas-provisioningserver (0.1+bzr1269+dfsg-0~1307~quantal1) ...
Setting up maas-cluster-controller (0.1+bzr1269+dfsg-0~1307~quantal1) ...
maas-pserv start/running, process 9031
maas-cluster-celery start/running, process 9062
Setting up postgresql-9.1 (9.1.6-1ubuntu1) ...
Creating new cluster (configuration: /etc/postgresql/9.1/main, data: /var/lib/postgresql/9.1/main)...
Moving configuration file /var/lib/postgresql/9.1/main/postgresql.conf to /etc/postgresql/9.1/main...
Moving configuration file /var/lib/postgresql/9.1/main/pg_hba.conf to /etc/postgresql/9.1/main...
Moving configuration file /var/lib/postgresql/9.1/main/pg_ident.conf to /etc/postgresql/9.1/main...
Configuring postgresql.conf to use port 5432...
update-alternatives: using /usr/share/postgresql/9.1/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
 * Starting PostgreSQL 9.1 database server
   ...done.
Setting up python-django-maas (0.1+bzr1269+dfsg-0~1307~quantal1) ...
Processing triggers for ufw ...
Setting up apache2-mpm-worker (2.2.22-6ubuntu2) ...
 * Starting 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
   ...done.
Setting up apache2 (2.2.22-6ubuntu2) ...
Setting up libapache2-mod-wsgi (3.4-0ubuntu1) ...
 * 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.
Setting up squid-deb-proxy (0.6.6) ...
squid-deb-proxy start/running, process 9496
Processing triggers for ureadahead ...
Setting up maas-region-controller (0.1+bzr1269+dfsg-0~1307~quantal1) ...
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 9647
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 9699
 * Restarting message broker rabbitmq-server
   ...done.
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 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 ...
Installed 0 object(s) from 0 fixture(s)

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 0039_add_nodegroup_to_bootimage.
 > 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_nodegroup_to_bootimage
 - Loading initial data for maasserver.
Installed 0 object(s) from 0 fixture(s)
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 10847
maas-txlongpoll start/running, process 10916
maas-region-celery start/running, process 10980
Processing triggers for ureadahead ...
Setting up maas (0.1+bzr1269+dfsg-0~1307~quantal1) ...
Setting up maas-dns (0.1+bzr1269+dfsg-0~1307~quantal1) ...
 * Stopping domain name service... bind9
waiting for pid 8653 to die
   ...done.
 * Starting domain name service... bind9
   ...done.
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
 -> Finished parsing the build-deps
adt-run: trace: & ubtree0t-maas-package-test: [----------------------------------------
+ buildtree=/tmp/tmp.039VTwNh21/ubtree0-ubtree/
+ shift
+ rm -rf -- /tmp/tmp.039VTwNh21/ubtree0t-maas-package-test-testtmp /tmp/tmp.039VTwNh21/ubtree0t-maas-package-test-testtmp/tmpdir /tmp/tmp.039VTwNh21/ubtree0t-maas-package-test-testtmp/adttmp
+ mkdir -- /tmp/tmp.039VTwNh21/ubtree0t-maas-package-test-testtmp /tmp/tmp.039VTwNh21/ubtree0t-maas-package-test-testtmp/tmpdir /tmp/tmp.039VTwNh21/ubtree0t-maas-package-test-testtmp/adttmp
adt-run: trace: & ubtree0t-maas-package-test:  - - - - - - - - - - results - - - - - - - - - -
ubtree0t-maas-package-test FAIL non-zero exit status 1
adt-run: trace: & ubtree0t-maas-package-test:  - - - - - - - - - - stdout - - - - - - - - - -
maas-integration.TestMAASIntegration.test_integration ... FAIL

======================================================================
FAIL: maas-integration.TestMAASIntegration.test_integration
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
  File "/tmp/tmp.039VTwNh21/ubtree0-ubtree/debian/tests/maas-integration.py", line 258, in test_integration
    self.login_api()
  File "/tmp/tmp.039VTwNh21/ubtree0-ubtree/debian/tests/maas-integration.py", line 84, in login_api
    "You are now logged in to the MAAS server at "
MismatchError: "You are now logged in to the MAAS server at http://10.98.0.90/MAAS/api/1.0/ with the profile name 'maas'." not in "\nYou are now logged in to the MAAS server at\nhttp://10.98.0.90/MAAS/api/1.0/ with the profile name 'maas'.\n\nFor help with the available commands, try:\n\n  maas-cli maas --help\n\n"


----------------------------------------------------------------------
Ran 1 test in 2.590s

FAILED (failures=1)
adt-run: trace: & ubtree0t-maas-package-test: ----------------------------------------]
adt-run: trace1: ** needs_reset, previously=False
adt-run: trace: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.
adt-run: trace: ** stop
adt-run: trace: ** close, scratch=tb-scratch~/tmp/tmp.039VTwNh21:-/|/tmp/tmp.039VTwNh21/!
+ RC=4
+ [ 0 -eq 1 ]
+ chown -R ubuntu /home/ubuntu/adt-log
+ chmod og+r /var/log/syslog
+ chmod og+r /var/crash/*
+ true
+ exit 4
+ RET=4
+ [ 0 -eq 1 ]
+ [ 4 -gt 0 ]
+ log_failure_msg adt-run exited with status 4.
+ log_msg Failure: adt-run exited with status 4.\n
+ date +%F %X
+ printf 2012-10-29 18:03:59: Failure: adt-run exited with status 4.\n
2012-10-29 18:03:59: Failure: adt-run exited with status 4.
+ [ 0 -eq 0 ]
+ mkdir -p <http://10.189.74.2:8080/job/quantal-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 54350 -t -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /home/ubuntu/adt-log; find  -type f -empty | xargs rm
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '[localhost]:54350' (ECDSA) to the list of known hosts.
sudo: unable to resolve host autopkgtest
find: `./.autopkgtest/gpg': Permission denied
rm: cannot remove `./qa-lab-tests/.bzr/checkout/views': Permission denied
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2012-10-29 18:03:59: Info: Cleaning up\n
2012-10-29 18:03:59: Info: Cleaning up
+ [ -f /var/tmp/adt/jenkins/disks/quantal-amd64-maas-20121029_180025.img.pid ]
+ cat /var/tmp/adt/jenkins/disks/quantal-amd64-maas-20121029_180025.img.pid
+ kill -9 1159
+ rm -f /var/tmp/adt/jenkins/disks/quantal-amd64-maas-20121029_180025.img.pid
+ rm -f /var/tmp/adt/jenkins/disks/quantal-amd64-maas-20121029_180025.img
+ rm -f /var/lock/adt/ssh.54350.lock
+ rm -f /var/lock/adt/vnc.5955.lock
+ [ -d /tmp/adt-amd64.SjNkFl ]
+ rm -Rf /tmp/adt-amd64.SjNkFl
+ exit 4
Build step 'Execute shell' marked build as failure
Archiving artifacts

More information about the ubuntu-testing-notifications mailing list