maas-devel team mailing list archive

[Jenkins Notification <devnull@xxxxxxxxxxxxx>]

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

------------------------------------------
[...truncated 1983 lines...]
...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 0046_add_nodegroup_maas_url.
 > 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
 > maasserver:0045_add_tag_kernel_opts
 > maasserver:0046_add_nodegroup_maas_url
 - 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 31505
maas-txlongpoll start/running, process 31571
maas-region-celery start/running, process 31632
Setting up maas (0.1+bzr1343+dfsg-0ubuntu2) ...
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+bzr1343+dfsg-0ubuntu2) ...
 * Stopping domain name service... bind9
waiting for pid 29859 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: [----------------------------------------
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_01_create_admin ... ok
maas-integration.TestMAASIntegration.test_02_update_maas_url ... ok
maas-integration.TestMAASIntegration.test_03_restart_dbus_avahi ... ok
maas-integration.TestMAASIntegration.test_04_update_pxe_config ... ok
maas-integration.TestMAASIntegration.test_05_import_pxe_files ... ok
maas-integration.TestMAASIntegration.test_06_update_preseed_arm ... ok
maas-integration.TestMAASIntegration.test_07_login_api ... ok
maas-integration.TestMAASIntegration.test_08_set_up_dhcp ... ok
maas-integration.TestMAASIntegration.test_09_update_dns_config ... ok
maas-integration.TestMAASIntegration.test_10_boot_nodes_enlist ... ok
maas-integration.TestMAASIntegration.test_11_check_nodes_declared ... ERROR

======================================================================
ERROR: maas-integration.TestMAASIntegration.test_11_check_nodes_declared
----------------------------------------------------------------------
_StringException: maas-cli maas ['nodes', 'list']: {{{('[]\n', '')}}}

Traceback (most recent call last):
  File "/tmp/tmp.ujNjz28LFj/ubtree0-ubtree/debian/tests/timeout.py", line 20, in wrapper
    result = func(*args, **kwargs)
  File "/tmp/tmp.ujNjz28LFj/ubtree0-ubtree/debian/tests/maas-integration.py", line 339, in test_11_check_nodes_declared
    self._wait_nodes(0)
  File "/tmp/tmp.ujNjz28LFj/ubtree0-ubtree/debian/tests/maas-integration.py", line 331, in _wait_nodes
    sleep(5)
  File "/tmp/tmp.ujNjz28LFj/ubtree0-ubtree/debian/tests/timeout.py", line 14, in _handle_timeout
    raise TimeoutError(error_message)
TimeoutError: Timer expired


----------------------------------------------------------------------
Ran 11 tests in 418.610s

FAILED (errors=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.ujNjz28LFj:-/|/tmp/tmp.ujNjz28LFj/!
+ RC=4
+ [ 4 -eq 20 ]
+ [ 0 -eq 1 ]
+ [ -x /home/ubuntu/adt-export-result ]
+ RES=PASS
+ [ 4 -gt 0 ]
+ RES=FAIL
+ /home/ubuntu/adt-export-result -D /root/adt-log maas FAIL
+ chown -R ubuntu /root/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 2013-01-23 07:54:23: Failure: adt-run exited with status 4.\n
2013-01-23 07:54:23: Failure: adt-run exited with status 4.
+ [ 0 -eq 0 ]
+ mkdir -p <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ dirname /root/adt-log
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -p 54324 -t -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /root; find /root/adt-log -type f -empty | xargs rm
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '[localhost]:54324' (ECDSA) to the list of known hosts.
sudo: unable to resolve host autopkgtest
+ scp -r -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -P 54324 ubuntu@localhost:/root/adt-log/*
    /var/crash/*crash /var/log/syslog <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ true
+ log_info_msg Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ log_msg Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results\n>
+ date +%F %X
+ printf 2013-01-23 07:54:25: Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results\n>
2013-01-23 07:54:25: Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ [ -n 2013-01-23_12-43-20 ]
+ log_info_msg Updating Jenkins results
+ log_msg Info: Updating Jenkins results\n
+ date +%F %X
+ printf 2013-01-23 07:54:25: Info: Updating Jenkins results\n
2013-01-23 07:54:25: Info: Updating Jenkins results
+ rsync -a <http://10.189.74.2:8080/job/precise-adt-maas/./ARCH=amd64,label=maas-lenovo-lab/ws/results/precise_amd64_maas_20130123-125448.result> /precise/out/
rsync: mkdir "/precise/out" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
+ true
+ [ 0 -eq 0 ]
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -p 54324 -t -o BatchMode=yes -l ubuntu localhost sudo poweroff
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '[localhost]:54324' (ECDSA) to the list of known hosts.
sudo: unable to resolve host autopkgtest
+ exit 4
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2013-01-23 07:54:26: Info: Cleaning up\n
2013-01-23 07:54:26: Info: Cleaning up
+ [ -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130123_074256.GK4tUt.img.pid ]
+ cat /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130123_074256.GK4tUt.img.pid
+ kill -9 18558
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130123_074256.GK4tUt.img.pid
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130123_074256.GK4tUt.img
+ rm -f /var/lock/adt/ssh.54324.lock
+ rm -f /var/lock/adt/vnc.5912.lock
+ [ -d /tmp/adt-amd64.nNSaUt ]
+ rm -Rf /tmp/adt-amd64.nNSaUt
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-*.img*
+ find /var/lock/adt -name *.lock -mtime +1
+ exit 4
Build step 'Execute shell' marked build as failure
Archiving artifacts