maas-builds team mailing list archive
-
maas-builds team
-
Mailing list archive
-
Message #00829
Jenkins Failure - trusty-adt-maas 275 - Built with lp:maas/1.5 (revno: 2285) and lp:~maas-maintainers/maas/packaging.trusty (revno: 280)
Built with lp:maas/1.5 (revno: 2285) and lp:~maas-maintainers/maas/packaging.trusty (revno: 280)
See http://d-jenkins.ubuntu-ci:8080/job/trusty-adt-maas/275/
[...truncated 5089 lines...]
> 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 25875
maas-txlongpoll start/running, process 25950
maas-region-celery start/running, process 26020
Setting up libnss3-nssdb (2:3.15.4-1ubuntu7) ...
Setting up libnss3:amd64 (2:3.15.4-1ubuntu7) ...
Setting up librados2 (0.80.1-0ubuntu1) ...
Setting up librbd1 (0.80.1-0ubuntu1) ...
Setting up tgt (1:1.0.43-0ubuntu4) ...
tgt start/running, process 26072
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.5.3+bzr2277+2285+280-0ubuntu2) ...
* 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.
maas-pserv start/running, process 26283
maas-cluster-celery start/running, process 26317
Processing triggers for ureadahead (0.100.0-16) ...
Setting up maas (1.5.3+bzr2277+2285+280-0ubuntu2) ...
Setting up adt-satdep (0) ...
Processing triggers for libc-bin (2.19-0ubuntu6) ...
adt-run2: >> execute dpkg,-s,adt-satdep /dev/null /dev/null /dev/null /tmp/adt-run.nWAgfi timeout=100 env=LANG=C
adt-run2: << ok 0
adt-run2: >> execute sh,-ec,dpkg-query%20--show%20-f%20%27%24%7BPackage%7D%5Ct%24%7BVersion%7D%5Cn%27%20%3E%20/tmp/adt-run.nWAgfi/ubtree0t-maas-package-test-packages.all /dev/null /dev/null /tmp/adt-run.nWAgfi/record-pkgversions-ubtree0t-maas-package-test-xerr /tmp/adt-run.nWAgfi timeout=100 debug=2-2 env=LANG=C
adt-run2: << ok 0
adt-run2: >> copyup /tmp/adt-run.nWAgfi/record-pkgversions-ubtree0t-maas-package-test-xerr /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/record-pkgversions-ubtree0t-maas-package-test-xerr
adt-run2: << ok
adt-run2: >> copyup /tmp/adt-run.nWAgfi/ubtree0t-maas-package-test-packages.all /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/ubtree0t-maas-package-test-packages.all
adt-run2: << ok
adt-run2: >> execute sh,-ec,test%20-d%20%22%241%22%20%7C%7C%20mkdir%20-p%20%22%241%22,x,/tmp/adt-run.Tn5Kw3/ubtree0-build /dev/null /dev/null /tmp/adt-run.nWAgfi/mkdir-xerr /tmp/adt-run.nWAgfi timeout=100 debug=2-2 env=LANG=C
adt-run2: << ok 0
adt-run2: >> copyup /tmp/adt-run.nWAgfi/mkdir-xerr /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/mkdir-xerr
adt-run2: << ok
adt-run2: >> copydown /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/ubtree0-tests-tree/ /tmp/adt-run.Tn5Kw3/ubtree0-build/real-tree/
adt-run2: << ok
adt-run2: >> execute chown,-R,ubuntu,--,/tmp/adt-run.Tn5Kw3/ubtree0-build/real-tree /dev/null /dev/null /dev/null /tmp/adt-run.nWAgfi timeout=100 env=LANG=C
adt-run2: << ok 0
adt-run [2014-06-02 22:13:34]: & ubtree0t-maas-package-test: [-----------------------
adt-run2: >> print-auxverb-command
adt-run2: << ok /tmp/adt-virt-qemua3xdGV/runcmd
Ignoring indexes: https://pypi.python.org/simple/
Downloading/unpacking nose-timer
Running setup.py (path:/tmp/pip_build_root/nose-timer/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_create_admin ... ok
maas-integration.TestMAASIntegration.test_restart_dbus_avahi ... SKIP: Avahi/DBUS are not used anymore
maas-integration.TestMAASIntegration.test_update_maas_url ... ok
maas-integration.TestMAASIntegration.test_restart_provisioning_server ... ok
maas-integration.TestMAASIntegration.test_check_initial_services ... ok
maas-integration.TestMAASIntegration.test_update_preseed_arm ... ok
maas-integration.TestMAASIntegration.test_login_api ... FAIL
SKIP: Not testing Cluster controller
======================================================================
FAIL: maas-integration.TestMAASIntegration.test_login_api
----------------------------------------------------------------------
_StringException: Empty attachments:
['maas', 'login', 'maas', 'http://192.168.21.5/MAAS/api/1.0/', u'wygPa5CFW4MCbGKKA8:bWyMRqrCAkjZuCUwhT:bxWHD6BBXAM6X3BQrzA3ZAsExM8VzHwF'] stdout
['maas', 'login', 'maas', 'http://192.168.21.5/MAAS/api/1.0/', u'wygPa5CFW4MCbGKKA8:bWyMRqrCAkjZuCUwhT:bxWHD6BBXAM6X3BQrzA3ZAsExM8VzHwF'] stderr: {{{
500 Internal Server Error:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmaster@localhost to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.4.7 (Ubuntu) Server at 192.168.21.5 Port 80</address>
</body></html>
}}}
Traceback (most recent call last):
File "/tmp/adt-run.Tn5Kw3/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 337, in test_login_api
assertCommandReturnCode(self, cmd, expected_output)
File "/tmp/adt-run.Tn5Kw3/ubtree0-build/real-tree/debian/tests/utils.py", line 143, in assertCommandReturnCode
runner.assertThat(output, Contains(expected_output))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in assertThat
raise mismatch_error
MismatchError: '\nYou are now logged in to the MAAS server' not in ''
maas-integration.TestMAASIntegration.test_update_preseed_arm: 0.0002s
maas-integration.TestMAASIntegration.test_check_initial_services: 0.0696s
maas-integration.TestMAASIntegration.test_create_admin: 0.1160s
maas-integration.TestMAASIntegration.test_login_api: 0.2085s
maas-integration.TestMAASIntegration.test_restart_provisioning_server: 0.5486s
maas-integration.TestMAASIntegration.test_update_maas_url: 1.1011s
----------------------------------------------------------------------
Ran 7 tests in 2.096s
FAILED (SKIP=2, failures=1)
adt-run [2014-06-02 22:13:39]: & ubtree0t-maas-package-test: -----------------------]
adt-run1: testbed executing test finished with exit status 1
adt-run2: >> copyup /tmp/adt-run.nWAgfi/ubtree0t-maas-package-test-stdout /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/ubtree0t-maas-package-test-stdout
adt-run2: << ok
adt-run2: >> copyup /tmp/adt-run.nWAgfi/ubtree0t-maas-package-test-stderr /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/ubtree0t-maas-package-test-stderr
adt-run2: << ok
adt-run: & ubtree0t-maas-package-test: - - - - - - - - - - results - - - - - - - - - -
ubtree0t-maas-package-test FAIL non-zero exit status 1
adt-run2: >> copyup /tmp/adt-run.nWAgfi/ubtree0t-maas-package-test-artifacts/ /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/artifacts/
adt-run2: << ok
adt-run2: >> execute rm,-rf,/tmp/adt-run.nWAgfi/ubtree0t-maas-package-test-artifacts /dev/null /dev/null /tmp/adt-run.nWAgfi/cleanup-artifacts-ubtree0t-maas-package-test-xerr /tmp/adt-run.nWAgfi timeout=100 debug=2-2 env=LANG=C
adt-run2: << ok 0
adt-run2: >> copyup /tmp/adt-run.nWAgfi/cleanup-artifacts-ubtree0t-maas-package-test-xerr /home/ubuntu/jenkins-jobs/workspace/trusty-adt-maas/results/cleanup-artifacts-ubtree0t-maas-package-test-xerr
adt-run2: << ok
adt-run1: ** needs_reset, previously=False, requested by run_tests() line 1286
adt-run1: ** needs_reset, previously=True, requested by process_actions() line 2196
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.
adt-run1: ** stop
adt-run1: ** close, scratch=/tmp/adt-run.nWAgfi
adt-run2: >> close
qemu: terminating on signal 15 from pid 4392
adt-run2: << ok
adt-run2: >> quit
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