← Back to team overview

maas-builds team mailing list archive

Jenkins Failure - trusty-adt-maas 310 - Built with lp:maas/1.5 (revno: 2298) and lp:~maas-maintainers/maas/packaging.trusty (revno: 295)

 

Built with lp:maas/1.5 (revno: 2298) and lp:~maas-maintainers/maas/packaging.trusty (revno: 295)

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

[...truncated 5111 lines...]
Setting up python-django-maas (1.6.1+bzr2550+2298+295-0ubuntu4) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas-region-controller-min (1.6.1+bzr2550+2298+295-0ubuntu4) ...
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 7860
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 7914
 * Restarting web server apache2
   ...done.
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 8111
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas-dns (1.6.1+bzr2550+2298+295-0ubuntu4) ...
 * Stopping domain name service... bind9
waiting for pid 7354 to die
   ...done.
 * Starting domain name service... bind9
   ...done.
Setting up maas-region-controller (1.6.1+bzr2550+2298+295-0ubuntu4) ...
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 8301
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 8357
 * Restarting message broker rabbitmq-server
   ...done.
Creating user "maas_longpoll" ...
...done.
Creating vhost "/maas_longpoll" ...
...done.
Setting permissions for user "maas_longpoll" in vhost "/maas_longpoll" ...
...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.3 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 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
(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.
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 9533
maas-txlongpoll start/running, process 9608
maas-region-celery start/running, process 9680
Setting up libnss3-nssdb (2:3.17.1-0ubuntu0.14.04.1) ...
Setting up libnss3:amd64 (2:3.17.1-0ubuntu0.14.04.1) ...
Setting up librados2 (0.80.5-0ubuntu0.14.04.1) ...
Setting up librbd1 (0.80.5-0ubuntu0.14.04.1) ...
Setting up tgt (1:1.0.43-0ubuntu4) ...
tgt start/running, process 9730
Setting up python-extras (0.0.3-2ubuntu1) ...
Setting up python-testtools (0.9.35-0ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas-cluster-controller (1.6.1+bzr2550+2298+295-0ubuntu4) ...
 * Restarting web server apache2
   ...done.
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/provisioningserver/__main__.py", line 42, in <module>
    main()
  File "/usr/lib/python2.7/dist-packages/provisioningserver/utils/__init__.py", line 597, in __call__
    self.execute(argv)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/utils/__init__.py", line 592, in execute
    args.handler.run(args)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/upgrade_cluster.py", line 210, in run
    hook()
  File "/usr/lib/python2.7/dist-packages/provisioningserver/upgrade_cluster.py", line 183, in generate_boot_resources_config
    boot_resources = BootConfig.load_from_cache(config_file)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/config.py", line 263, in load_from_cache
    with open(filename, "rb") as stream:
IOError: [Errno 2] No such file or directory: u'/etc/maas/bootresources.yaml'
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.gbJU4f
adt-run2: >> close
qemu: terminating on signal 15 from pid 22506
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/trusty-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


Follow ups