And I just installed MAAS myself in a clean system without any issues. (So my question is, do you have the cloud archive enabled or installed celery and/or kombu from another place? - apt-cache policy <package> should show the version I'm mlooking for)
Setting up maas-region-controller (1.2+bzr1373+dfsg-0ubuntu1~12.04.1) ... 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 9083 squid-deb-proxy stop/waiting squid-deb-proxy start/running, process 9132 Restarting rabbitmq-server: SUCCESS rabbitmq-server. 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.1 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_user_permissions Creating table auth_user_groups Creating table auth_user Creating table auth_message 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 ... No fixtures found. 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 > > [10/9260] > 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. No fixtures found. Running migrations for metadataserver: - Migrating forwards to 0003_populate_hardware_details. > metadataserver:0001_initial > metadataserver:0002_add_nodecommissionresult > metadataserver:0003_populate_hardware_details - Loading initial data for metadataserver. Installed 1 object(s) from 1 fixture(s) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1207429 Title: Multiple package upgrade problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
