[Maas-devel] Build failed in Jenkins: saucy-adt-maas-daily » amd64,lenovo-RD230-01 #23
Jenkins Notification
devnull at canonical.com
Fri May 24 01:19:49 UTC 2013
See <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/23/>
------------------------------------------
[...truncated 1672 lines...]
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_groups
Creating table auth_user_user_permissions
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 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.
Installed 0 object(s) from 0 fixture(s)
Running migrations for metadataserver:
- Migrating forwards to 0010_add_script_result.
> metadataserver:0001_initial
> metadataserver:0002_add_nodecommissionresult
> metadataserver:0003_populate_hardware_details
> metadataserver:0004_add_commissioningscript
> metadataserver:0005_nodecommissionresult_add_timestamp
> metadataserver:0006_nodecommissionresult_add_status
> metadataserver:0007_nodecommissionresult_change_name_size
> metadataserver:0008_rename_lshw_commissioning_output
> metadataserver:0009_delete_status
> metadataserver:0010_add_script_result
- 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-region
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-region
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 13505
Processing triggers for ureadahead ...
Setting up maas (1.4+bzr1488+dfsg-0+1491+183~ppa0~saucy1) ...
Setting up maas-dns (1.4+bzr1488+dfsg-0+1491+183~ppa0~saucy1) ...
* Stopping domain name service... bind9
waiting for pid 9332 to die
...done.
* Starting domain name service... bind9
...done.
Setting up python-testtools (0.9.29-2ubuntu1) ...
Setting up python-extras (0.0.3-2) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
-> Finished parsing the build-deps
adt-run: trace: & ubtree1t-maas-package-test: [----------------------------------------
+ buildtree=/tmp/tmp.afDMx05V8B/ubtree1-ubtree/
+ shift
+ rm -rf -- /tmp/tmp.afDMx05V8B/ubtree1t-maas-package-test-testtmp /tmp/tmp.afDMx05V8B/ubtree1t-maas-package-test-testtmp/tmpdir /tmp/tmp.afDMx05V8B/ubtree1t-maas-package-test-testtmp/adttmp
+ mkdir -- /tmp/tmp.afDMx05V8B/ubtree1t-maas-package-test-testtmp /tmp/tmp.afDMx05V8B/ubtree1t-maas-package-test-testtmp/tmpdir /tmp/tmp.afDMx05V8B/ubtree1t-maas-package-test-testtmp/adttmp
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: https://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_check_initial_services ... FAIL
SKIP: Not testing Cluster controller
======================================================================
FAIL: maas-integration.TestMAASIntegration.test_check_initial_services
----------------------------------------------------------------------
_StringException: File /var/log/upstart/maas-cluster-celery.log content: {{{could not be read}}}
Traceback (most recent call last):
File "/tmp/tmp.afDMx05V8B/ubtree1-ubtree/debian/tests/maas-integration.py", line 273, in test_check_initial_services
'/var/log/upstart/maas-cluster-celery.log')
File "/tmp/tmp.afDMx05V8B/ubtree1-ubtree/debian/tests/utils.py", line 95, in assertStartedUpstartService
runner.assertThat(output, Contains(service_name + " start/running"))
MismatchError: 'maas-cluster-celery start/running' not in 'maas-cluster-celery stop/waiting\n'
maas-integration.TestMAASIntegration.test_disable_raring: 0.0002s
maas-integration.TestMAASIntegration.test_check_initial_services: 0.0195s
maas-integration.TestMAASIntegration.test_create_admin: 0.1446s
maas-integration.TestMAASIntegration.test_restart_dbus_avahi: 0.1587s
maas-integration.TestMAASIntegration.test_update_maas_url: 1.1411s
----------------------------------------------------------------------
Ran 5 tests in 1.466s
FAILED (SKIP=1, failures=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.afDMx05V8B:-/|/tmp/tmp.afDMx05V8B/!
+ 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-23 21:19:45: Failure: adt-run exited with status 4.\n
2013-05-23 21:19:45: Failure: adt-run exited with status 4.
+ [ 0 -eq 0 ]
+ mkdir -p <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results>
+ dirname /root/adt-log
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/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.
sudo: unable to resolve host autopkgtest-region
+ scp -r -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -P 54323 ubuntu at localhost:/root/adt-log/*
/var/crash/*crash /var/log/syslog <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results>
+ true
+ log_info_msg Test artifacts copied to <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results>
+ log_msg Info: Test artifacts copied to <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results\n>
+ date +%F %X
+ printf 2013-05-23 21:19:46: Info: Test artifacts copied to <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results\n>
2013-05-23 21:19:46: Info: Test artifacts copied to <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results>
+ [ -n 2013-05-23_23-31-34 ]
+ log_info_msg Updating Jenkins results
+ log_msg Info: Updating Jenkins results\n
+ date +%F %X
+ printf 2013-05-23 21:19:46: Info: Updating Jenkins results\n
2013-05-23 21:19:46: Info: Updating Jenkins results
+ rsync -a <http://10.189.74.2:8080/job/saucy-adt-maas-daily/./ARCH=amd64,label=lenovo-RD230-01/ws/results/saucy_amd64_maas_20130524-011948.result> /saucy/out/
rsync: mkdir "/saucy/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/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.
sudo: unable to resolve host autopkgtest-region
+ exit 4
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2013-05-23 21:19:46: Info: Cleaning up\n
2013-05-23 21:19:46: Info: Cleaning up
+ [ -f /var/tmp/adt/disks/saucy-amd64-maas-20130523_210621.pTTuX0.img.pid ]
+ cat /var/tmp/adt/disks/saucy-amd64-maas-20130523_210621.pTTuX0.img.pid
+ kill -9 17913
+ rm -f /var/tmp/adt/disks/saucy-amd64-maas-20130523_210621.pTTuX0.img.pid
+ rm -f /var/tmp/adt/disks/saucy-amd64-maas-20130523_210621.pTTuX0.img
+ rm -f /var/lock/adt/ssh.54323.lock
+ rm -f /var/lock/adt/vnc.5911.lock
+ [ -d /tmp/adt-amd64.aoK7KQ ]
+ rm -Rf /tmp/adt-amd64.aoK7KQ
+ rm -f /var/tmp/adt/disks/saucy-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