[Maas-devel] Build failed in Jenkins: precise-adt-maas-daily » amd64,maas-lenovo-lab #82
Jenkins Notification
devnull at canonical.com
Mon May 6 17:18:07 UTC 2013
See <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/82/>
------------------------------------------
[...truncated 1788 lines...]
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 0050_shared_to_per_tenant_storage.
> 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
> maasserver:0047_add_owner_to_filestorage
> maasserver:0048_add_key_to_filestorage
> maasserver:0049_filestorage_key_unique
> maasserver:0050_shared_to_per_tenant_storage
- 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: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
... waiting apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
...done.
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 23087
maas-txlongpoll start/running, process 23153
maas-region-celery start/running, process 23214
Setting up maas (1.2+bzr1373+dfsg-0+1376+170~ppa0~precise1) ...
Setting up maas-dns (1.2+bzr1373+dfsg-0+1376+170~ppa0~precise1) ...
* Stopping domain name service... bind9
waiting for pid 19450 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: & ubtree1t-maas-package-test: [----------------------------------------
adt-run: trace: & ubtree1t-maas-package-test: - - - - - - - - - - results - - - - - - - - - -
ubtree1t-maas-package-test FAIL non-zero exit status 1
adt-run: trace: & ubtree1t-maas-package-test: - - - - - - - - - - stdout - - - - - - - - - -
Ignoring indexes: http://pypi.python.org/simple/
Downloading/unpacking nose-timer
Running setup.py egg_info for package nose-timer
Installing collected packages: nose-timer
Running setup.py install for nose-timer
Successfully installed nose-timer
Cleaning up...
maas-integration.TestMAASIntegration.test_disable_raring ... ok
maas-integration.TestMAASIntegration.test_create_admin ... ok
maas-integration.TestMAASIntegration.test_update_maas_url ... ok
maas-integration.TestMAASIntegration.test_restart_dbus_avahi ... ok
maas-integration.TestMAASIntegration.test_update_pxe_config ... ok
maas-integration.TestMAASIntegration.test_import_pxe_files ... ok
maas-integration.TestMAASIntegration.test_update_preseed_arm ... ok
maas-integration.TestMAASIntegration.test_login_api ... ok
maas-integration.TestMAASIntegration.test_set_http_proxy ... SKIP: Not testing proxy.
maas-integration.TestMAASIntegration.test_cluster_connected ... ok
maas-integration.TestMAASIntegration.test_set_up_dhcp_region ... ok
maas-integration.TestMAASIntegration.test_set_up_dhcp_cluster ... SKIP: Not testing cluster controller
maas-integration.TestMAASIntegration.test_update_dns_config ... ok
maas-integration.TestMAASIntegration.test_boot_nodes_enlist ... ok
maas-integration.TestMAASIntegration.test_check_nodes_declared ... ERROR
SKIP: Not testing Cluster controller
======================================================================
ERROR: maas-integration.TestMAASIntegration.test_check_nodes_declared
----------------------------------------------------------------------
_StringException: maas-cli maas ['nodes', 'list']: {{{('[\n {\n "status": 0,\n "macaddress_set": [\n {\n "resource_uri": "/MAAS/api/1.0/nodes/node-1d238fc0-b670-11e2-9be2-525400123456/macs/00:e0:81:dd:d4:11/",\n "mac_address": "00:e0:81:dd:d4:11"\n },\n {\n "resource_uri": "/MAAS/api/1.0/nodes/node-1d238fc0-b670-11e2-9be2-525400123456/macs/00:e0:81:dd:d4:12/",\n "mac_address": "00:e0:81:dd:d4:12"\n }\n ],\n "netboot": true,\n "hostname": "6mrt4.master",\n "power_type": "ipmi",\n "system_id": "node-1d238fc0-b670-11e2-9be2-525400123456",\n "architecture": "amd64/generic",\n "tag_names": [],\n "resource_uri": "/MAAS/api/1.0/nodes/node-1d238fc0-b670-11e2-9be2-525400123456/"\n },\n {\n "status": 0,\n "macaddress_set": [\n {\n "resource_uri": "/MAAS/api/1.0/nodes/node-2213844a-b670-11e2-9be2-525400123456/macs/00:e0:81:dd:d5:99/",\n "mac_address": "00:e0:81:dd:d5:99"\n },\n {\n "resource_uri": "/MAAS/api/1.0/nodes/node-2213844a-b670-11e2-9be2-525400123456/macs/00:e0:81:dd:d5:9a/",\n "mac_address": "00:e0:81:dd:d5:9a"\n }\n ],\n "netboot": true,\n "hostname": ";; connection timed out; no servers could be reached.master",\n "power_type": "",\n "system_id": "node-2213844a-b670-11e2-9be2-525400123456",\n "architecture": "amd64/generic",\n "tag_names": [],\n "resource_uri": "/MAAS/api/1.0/nodes/node-2213844a-b670-11e2-9be2-525400123456/"\n }\n]\n', '')}}}
Traceback (most recent call last):
File "/tmp/tmp.hfqszhTHwo/ubtree1-ubtree/debian/tests/utils.py", line 29, in wrapper
result = func(*args, **kwargs)
File "/tmp/tmp.hfqszhTHwo/ubtree1-ubtree/debian/tests/maas-integration.py", line 486, in test_check_nodes_declared
self._wait_nodes(0)
File "/tmp/tmp.hfqszhTHwo/ubtree1-ubtree/debian/tests/maas-integration.py", line 478, in _wait_nodes
sleep(5)
File "/tmp/tmp.hfqszhTHwo/ubtree1-ubtree/debian/tests/utils.py", line 23, in _handle_timeout
raise TimeoutError(error_message)
TimeoutError: Timer expired
maas-integration.TestMAASIntegration.test_update_pxe_config: 0.0002s
maas-integration.TestMAASIntegration.test_disable_raring: 0.0003s
maas-integration.TestMAASIntegration.test_update_preseed_arm: 0.0016s
maas-integration.TestMAASIntegration.test_create_admin: 0.0730s
maas-integration.TestMAASIntegration.test_cluster_connected: 0.2106s
maas-integration.TestMAASIntegration.test_restart_dbus_avahi: 0.2195s
maas-integration.TestMAASIntegration.test_login_api: 0.3231s
maas-integration.TestMAASIntegration.test_update_maas_url: 1.1379s
maas-integration.TestMAASIntegration.test_set_up_dhcp_region: 2.4941s
maas-integration.TestMAASIntegration.test_update_dns_config: 4.2567s
maas-integration.TestMAASIntegration.test_boot_nodes_enlist: 12.7443s
maas-integration.TestMAASIntegration.test_import_pxe_files: 101.2978s
maas-integration.TestMAASIntegration.test_check_nodes_declared: 420.0151s
----------------------------------------------------------------------
Ran 15 tests in 542.781s
FAILED (SKIP=3, errors=1)
adt-run: trace: & ubtree1t-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.hfqszhTHwo:-/|/tmp/tmp.hfqszhTHwo/!
+ 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-05-06 13:18:04: Failure: adt-run exited with status 4.\n
2013-05-06 13:18:04: Failure: adt-run exited with status 4.
+ [ 0 -eq 0 ]
+ mkdir -p <http://10.189.74.2:8080/job/precise-adt-maas-daily/./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 54323 -t -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /root; find /root/adt-log -type f -empty | xargs rm -Rf
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.
+ scp -r -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/jenkins/disks/adtkey -P 54323 ubuntu at localhost:/root/adt-log/*
/var/crash/*crash /var/log/syslog <http://10.189.74.2:8080/job/precise-adt-maas-daily/./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-daily/./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-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results\n>
+ date +%F %X
+ printf 2013-05-06 13:18:05: Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results\n>
2013-05-06 13:18:05: Info: Test artifacts copied to <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results>
+ [ -n 2013-05-06_17-03-58 ]
+ log_info_msg Updating Jenkins results
+ log_msg Info: Updating Jenkins results\n
+ date +%F %X
+ printf 2013-05-06 13:18:05: Info: Updating Jenkins results\n
2013-05-06 13:18:05: Info: Updating Jenkins results
+ rsync -a <http://10.189.74.2:8080/job/precise-adt-maas-daily/./ARCH=amd64,label=maas-lenovo-lab/ws/results/precise_amd64_maas_20130506-171804.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 54323 -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]:54323' (ECDSA) to the list of known hosts.
+ exit 4
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2013-05-06 13:18:06: Info: Cleaning up\n
2013-05-06 13:18:06: Info: Cleaning up
+ [ -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130506_130358.5zU2QO.img.pid ]
+ cat /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130506_130358.5zU2QO.img.pid
+ kill -9 14756
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130506_130358.5zU2QO.img.pid
+ rm -f /var/tmp/adt/jenkins/disks/precise-amd64-maas-20130506_130358.5zU2QO.img
+ rm -f /var/lock/adt/ssh.54323.lock
+ rm -f /var/lock/adt/vnc.5911.lock
+ [ -d /tmp/adt-amd64.Q0sRs6 ]
+ rm -Rf /tmp/adt-amd64.Q0sRs6
+ 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
More information about the Maas-devel
mailing list