maas-builds team mailing list archive

[Jenkins Notification <devnull@xxxxxxxxxxxxx>]

Built with lp:maas (revno: 3128) and lp:~maas-maintainers/maas/packaging (revno: 314)

See http://d-jenkins.ubuntu-ci:8080/job/utopic-adt-maas/833/

[...truncated 5934 lines...]
Processing triggers for ufw (0.34~rc-0ubuntu4) ...
Setting up maas-proxy (1.7.0~beta4+bzr3127+3128+314-0ubuntu1) ...
squid3 stop/waiting
maas-proxy start/running, process 7656
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
Setting up python-docutils (0.12+dfsg-1) ...
update-alternatives: using /usr/share/docutils/scripts/python2/rst-buildhtml to provide /usr/bin/rst-buildhtml (rst-buildhtml) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2html to provide /usr/bin/rst2html (rst2html) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2latex to provide /usr/bin/rst2latex (rst2latex) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2man to provide /usr/bin/rst2man (rst2man) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2odt to provide /usr/bin/rst2odt (rst2odt) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2odt_prepstyles to provide /usr/bin/rst2odt_prepstyles (rst2odt_prepstyles) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2pseudoxml to provide /usr/bin/rst2pseudoxml (rst2pseudoxml) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2s5 to provide /usr/bin/rst2s5 (rst2s5) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2xetex to provide /usr/bin/rst2xetex (rst2xetex) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rst2xml to provide /usr/bin/rst2xml (rst2xml) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python2/rstpep2html to provide /usr/bin/rstpep2html (rstpep2html) in auto mode
Setting up python-sphinx (1.2.2+dfsg-1ubuntu2) ...
Setting up python-django-maas (1.7.0~beta4+bzr3127+3128+314-0ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas-region-controller-min (1.7.0~beta4+bzr3127+3128+314-0ubuntu1) ...
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 7778
 * Restarting web server apache2
   ...done.
Setting up maas-region-controller (1.7.0~beta4+bzr3127+3128+314-0ubuntu1) ...
Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Module expires already enabled
Module wsgi already enabled
rsyslog stop/waiting
rsyslog start/running, process 8025
 * Restarting PostgreSQL 9.4 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_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 0113_add_boot_source_cache_model.
 > 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
 > maasserver:0075_add_boot_resource_models
 > maasserver:0076_add_osystem_to_bootimage
 > maasserver:0077_remove_null_for_bootsourceselection_release
 > maasserver:0078_add_osystem_to_node
 > maasserver:0079_supported_subarches_for_bootimage
 > maasserver:0080_binary_to_editablebinary_in_bootsource
 > maasserver:0081_ipaddress_table_and_static_dhcp_ranges
 > maasserver:0082_cluster_interface_for_macaddress
 > maasserver:0083_add_license_key_to_node
 > maasserver:0084_add_ssl_key_model
 > maasserver:0085_add_user_to_staticipaddress
 > maasserver:0086_add_xinstall_path_and_type_to_bootimage
 > maasserver:0087_add_licensekey_model
 > maasserver:0088_ip_to_custom_field
 > maasserver:0088_z_backport_trunk_0099
 > maasserver:0089_create_nodegroupinterface_name
 > maasserver:0090_initialise_nodegroupinterface_name
 > maasserver:0091_add_boot_type_to_node
 > maasserver:0092_populate_node_boot_type
 > maasserver:0093_add_eventtype_and_event
 > maasserver:0094_add_error_description
 > maasserver:0095_add_event_description
 > maasserver:0096_add_power_state_to_node
 > maasserver:0097_add_largefile_model
 > maasserver:0098_add_bootresource_models
 > maasserver:0099_convert_cluster_interfaces_to_networks
 > maasserver:0100_remove_cluster_from_bootsrouce
 > maasserver:0100_remove_duplicate_bootsource_urls
 > maasserver:0101_make_bootsource_url_unique
 > maasserver:0102_candidate_name
 > maasserver:0103_candidate_names
 > maasserver:0104_add_node_disable_ipv4
 > maasserver:0105_remove_rtype_from_uniqueness_on_boot_resource
 > maasserver:0106_add_os_to_boot_source_selection
 > maasserver:0107_add_default_gateway_to_network
 > maasserver:0108_migrate_allocated_netboot
 > maasserver:0109_networks_dns_servers
 > maasserver:0110_deployed_state_compat
 > maasserver:0111_add_nodegroup_default_disable_ipv4
 > maasserver:0112_remove_boot_image_model
 > maasserver:0113_add_boot_source_cache_model
 - Loading initial data for maasserver.
Installed 0 object(s) from 0 fixture(s)
Running migrations for metadataserver:
 - Migrating forwards to 0015_rename_nodecommissionresult_add_result_type.
 > 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
 > metadataserver:0015_rename_nodecommissionresult_add_result_type
 - Loading initial data for metadataserver.
Installed 1 object(s) from 1 fixture(s)
 * Restarting web server apache2
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
   ...fail!
 * The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
invoke-rc.d: initscript apache2, action "restart" failed.
/var/lib/dpkg/info/maas-region-controller.postinst: 222: /var/lib/dpkg/info/maas-region-controller.postinst: Syntax error: end of file unexpected (expecting "then")
adt-run1: ** bomb timed out on command "env DEBIAN_FRONTEND=noninteractive LANG=C apt-get install -q -y -f -o APT::Install-Recommends=False -o Debug::pkgProblemResolver=true" (kind: install)
adt-run1: ** stop
adt-run1: ** close, scratch=/tmp/adt-run.RF52gW
adt-run2: >> close
qemu: terminating on signal 15 from pid 8708
adt-run2: << ok
adt-run2: >> quit
adt-run: testbed failed: timed out on command "env DEBIAN_FRONTEND=noninteractive LANG=C apt-get install -q -y -f -o APT::Install-Recommends=False -o Debug::pkgProblemResolver=true" (kind: install)
adt-run1: ** stop
adt-run2: / tests-tree rmtree /home/ubuntu/jenkins-jobs/workspace/utopic-adt-maas/results/ubtree0-tests-tree
Build step 'Execute shell' marked build as failure
Archiving artifacts
Email was triggered for: Failure
Sending email for trigger: Failure