maas-builds team mailing list archive

[Jenkins Notification <devnull@xxxxxxxxxxxxx>]

See http://d-jenkins.ubuntu-ci:8080/job/trusty-adt-maas-daily/195/

[...truncated 2855 lines...]
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 0074_boot_images_timestamp.
 > 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
 > maasserver:0051_bigger_distro_series_name
 > maasserver:0052_add_node_storage
 > maasserver:0053_node_routers
 > maasserver:0054_download_progress
 > maasserver:0055_nullable_bytes_downloaded
 > maasserver:0056_netboot_off_for_allocated_nodes
 > maasserver:0057_remove_hardware_details
 > maasserver:0058_add_agent_name_to_node
 > maasserver:0059_dhcp_detection_model
 > maasserver:0060_add_zone_object
 > maasserver:0061_add_ref_from_node_to_zone
 > maasserver:0062_add_vlan_model
 > maasserver:0063_create_default_zone
 > maasserver:0064_set_default_zone
 > maasserver:0065_set_default_zone_as_model_default
 > maasserver:0066_rename_vlan_add_link_node_network
 > maasserver:0067_default_commissioning_trusty
 > maasserver:0068_network_description_textfield
 > maasserver:0069_add_mac_network_relation
 > maasserver:0070_drop_network_node_relation
 > maasserver:0071_drop_after_commissioning_action
 > maasserver:0072_remove_ipmi_autodetect
 > maasserver:0073_add_label_to_bootimage
 > maasserver:0074_boot_images_timestamp
 - Loading initial data for maasserver.
Installed 1 object(s) from 1 fixture(s)
Running migrations for metadataserver:
 - Migrating forwards to 0014_commission_result_rename_data_bin_col.
 > 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
 > metadataserver:0011_commission_result_binary_data_col
 > metadataserver:0012_commission_result_binary_data_recode
 > metadataserver:0013_commission_result_drop_old_data_col
 > metadataserver:0014_commission_result_rename_data_bin_col
 - Loading initial data for metadataserver.
Installed 1 object(s) from 1 fixture(s)
 * Restarting web server apache2
   ...done.
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 7588
maas-txlongpoll start/running, process 7626
maas-region-celery start/running, process 7659
Setting up python-testtools (0.9.35-0ubuntu1) ...
Setting up python-extras (0.0.3-2ubuntu1) ...
Setting up libnss3-nssdb (2:3.15.4-1ubuntu6) ...
Setting up libnss3:amd64 (2:3.15.4-1ubuntu6) ...
Setting up librados2 (0.78-0ubuntu1) ...
Setting up librbd1 (0.78-0ubuntu1) ...
Setting up tgt (1:1.0.43-0ubuntu2) ...
tgt start/running, process 7738
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas-cluster-controller (1.5+bzr2216+2218+263~ppa0~ubuntu14.04.1) ...
 * Restarting web server apache2
   ...done.
maas-pserv start/running, process 7955
maas-cluster-celery start/running, process 7989
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas (1.5+bzr2216+2218+263~ppa0~ubuntu14.04.1) ...
Processing triggers for libc-bin (2.19-0ubuntu3) ...
 -> Finished parsing the build-deps
adt-run1: shared downtmp with FIFO supported, showing test output in realtime
adt-run [2014-04-02 09:04:16]: & ubtree0t-maas-package-test: [-----------------------
stop: Job failed while stopping
start: Job is already running: networking
adt-run1: testbed executing test finished with exit status 1
adt-run [2014-04-02 09:04:17]: & ubtree0t-maas-package-test: -----------------------]
ubtree0t-maas-package-test FAIL non-zero exit status 1
adt-run: & ubtree0t-maas-package-test:  - - - - - - - - - - results - - - - - - - - - -
adt-run1: ** needs_reset, previously=False, requested by run_tests() line 1213
adt-run1: ** needs_reset, previously=True, requested by process_actions() line 2216
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.
adt-run1: ** stop
adt-run1: ** close, scratch=/tmp/adt-run.wBUZtx
+ 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 /var/tmp/testresults
+ chmod og+r /var/log/syslog
+ ls /var/crash/
+ [ -n  ]
+ exit 4
Connection to localhost closed.
+ 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 2014-04-02 09:04:18: Failure: adt-run exited with status 4.\n
2014-04-02 09:04:18: Failure: adt-run exited with status 4.
+ [ 0 -eq 0 ]
+ mkdir -p /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -p 54323 -tt -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /root/adt-log; find /root/adt-log -type f -empty | xargs rm 2>/dev/null
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.
find: `/root/adt-log': Permission denied
Connection to localhost closed.
+ true
+ scp -r -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -P 54323 ubuntu@localhost:/root/adt-log/* /var/crash/*crash /var/log/syslog /var/tmp/testresults /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results
+ true
+ log_info_msg Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results
+ log_msg Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results\n
+ date +%F %X
+ printf 2014-04-02 09:04:19: Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results\n
2014-04-02 09:04:19: Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results
+ [ -f /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results/summary.log ]
+ [ -n 2014-04-02_12-58-44 ]
+ ls -tr /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results/*.result
+ tail -1
+ resfile=
+ [ -n  ]
+ log_failure_msg Test didn't end normally. Generating error file
+ log_msg Failure: Test didn't end normally. Generating error file\n
+ date +%F %X
+ printf 2014-04-02 09:04:19: Failure: Test didn't end normally. Generating error file\n
2014-04-02 09:04:19: Failure: Test didn't end normally. Generating error file
+ date +%Y%m%d-%H%M%S
+ errfile=/home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results/trusty_amd64_maas_20140402-090419.error
+ echo trusty amd64 maas
+ rsync -a /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas-daily/results/trusty_amd64_maas_20140402-090419.error /trusty/tmp/
rsync: mkdir "/trusty/tmp" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.0]
+ true
+ [ 0 -eq 0 ]
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -p 54323 -tt -o BatchMode=yes -l ubuntu localhost sudo poweroff
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.


Broadcast message from ubuntu@autopkgtest

	(/dev/pts/1) at 9:04 ...




The system is going down for power off NOW!

Connection to localhost closed.
+ exit 4
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2014-04-02 09:04:20: Info: Cleaning up\n
2014-04-02 09:04:20: Info: Cleaning up
+ [ -f /var/tmp/adt/disks/run/trusty-amd64-maas-20140402_085919.V2YTS6.img.pid ]
+ cat /var/tmp/adt/disks/run/trusty-amd64-maas-20140402_085919.V2YTS6.img.pid
+ kill -9 30556
+ rm -f /var/tmp/adt/disks/run/trusty-amd64-maas-20140402_085919.V2YTS6.img.pid
+ rm -f /var/tmp/adt/disks/run/trusty-amd64-maas-20140402_085919.V2YTS6.img
+ rm -f /var/lock/adt/ssh.54323.lock
+ rm -f /var/lock/adt/vnc.5911.lock
+ [ -d /tmp/adt-amd64.o4NFqa ]
+ rm -Rf /tmp/adt-amd64.o4NFqa
+ rm -f /var/tmp/adt/disks/run/trusty-amd64-maas-*.img*
+ find /var/lock/adt -name *.lock -mtime +1
+ exit 4
Build step 'Execute shell' marked build as failure
Archiving artifacts
Email was triggered for: Failure
Sending email for trigger: Failure