[Bug 1207429] Re: Multiple package upgrade problems
Marking this bug invalid as it was related to software not present in the UBuntu archives ** Changed in: maas (Ubuntu) Status: Confirmed => Invalid -- 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
[Bug 1207429] Re: Multiple package upgrade problems
Sure enough, python-kombu 2.1.1-2ubuntu1~0.IS.12.04 came from a private archive, as did python-celery. I'll track this down from here. -- 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
[Bug 1207429] Re: Multiple package upgrade problems
I just did an upgrade from maas 0.1+bzr482+dfsg-0ubuntu1 to 1.2+bzr1373 +dfsg-0ubuntu1~12.04.1 without issues as well: Configuration file `/etc/maas/maas_local_settings.py' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** maas_local_settings.py (Y/I/N/O/D/Z) [default=N] ? y Installing new version of config file /etc/maas/maas_local_settings.py ... Installing new version of config file /etc/maas/maas-http.conf ... 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 13887 squid-deb-proxy stop/waiting squid-deb-proxy start/running, process 13947 Restarting rabbitmq-server: SUCCESS rabbitmq-server. Changing password for user "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: already exists. resetting password: success. creating database maasdb: already exists. dbconfig-common: flushing administrative password Syncing... Creating tables ... 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: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:0003_populate_hardware_details - Loading initial data for metadataserver. Installed 1 object(s) from 1 fixture(s) * Restarting web server apache2 ... waiting . ...done. squid-deb-proxy stop/waiting squid-deb-proxy start/running, process 14881 maas-txlongpoll start/running, process 14949 maas-region-celery start/running, process 15012 Setting up maas (1.2+bzr1373+dfsg-0ubuntu1~12.04.1) ... Setting up python-maas-provision (2.2.2-0ubuntu4.1) ... Setting up maas-provision-common (2.2.2-0ubuntu4.1) ... Installing new version of config file /etc/cobbler/version ... Setting up maas-provision (2.2.2-0ubuntu4.1) ... cobbler start/running,
[Bug 1207429] Re: Multiple package upgrade problems
In either case (upgrade from cobbler based maas to newer maas | fresh install of newer maas) I have not experienced any of the issues! -- 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
[Bug 1207429] Re: Multiple package upgrade problems
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 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
[Bug 1207429] Re: Multiple package upgrade problems
This is a very weird issue. This doesn't really seem to be a maas bug but rather something related to kombu. Could you please show the versions of celery, python-komby and maas packages? -- 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
[Bug 1207429] Re: Multiple package upgrade problems
I get this on a fresh install of maas on precise:
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 31130
squid-deb-proxy stop/waiting
squid-deb-proxy start/running, process 31179
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
[ OK ]
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
Traceback (most recent call last):
File "/usr/bin/django-admin", line 5, in
management.execute_from_command_line()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 429, in execute_from_command_line
utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
191, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
219, in execute
self.validate()
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
249, in validate
num_errors = get_validation_errors(s, app)
File "/usr/lib/python2.7/dist-packages/django/core/management/validation.py",
line 35, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File "/usr/lib/python2.7/dist-packages/django/db/models/loading.py", line
146, in get_app_errors
self._populate()
File "/usr/lib/python2.7/dist-packages/django/db/models/loading.py", line 64,
in _populate
self.load_app(app_name)
File "/usr/lib/python2.7/dist-packages/django/db/models/loading.py", line 78,
in load_app
models = import_module('.models', app_name)
File "/usr/lib/python2.7/dist-packages/django/utils/importlib.py", line 35,
in import_module
__import__(name)
File "/usr/lib/python2.7/dist-packages/maasserver/models/__init__.py", line
53, in
from maasserver.models.bootimage import BootImage
File "/usr/lib/python2.7/dist-packages/maasserver/models/bootimage.py", line
25, in
from maasserver.models.nodegroup import NodeGroup
File "/usr/lib/python2.7/dist-packages/maasserver/models/nodegroup.py", line
33, in
from maasserver.refresh_worker import refresh_worker
File "/usr/lib/python2.7/dist-packages/maasserver/refresh_worker.py", line
19, in
from provisioningserver.tasks import refresh_secrets
File "/usr/lib/python2.7/dist-packages/provisioningserver/tasks.py", line 32,
in
from celery.app import app_or_default
File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line 19, in
from ..utils import cached_property, instantiate
File "/usr/lib/python2.7/dist-packages/celery/utils/__init__.py", line 31, in
from kombu.utils import cached_property, gen_unique_id, kwdict # noqa
ImportError: No module named kombu.utils
--
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
[Bug 1207429] Re: Multiple package upgrade problems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: maas (Ubuntu) Status: New => Confirmed -- 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
[Bug 1207429] Re: Multiple package upgrade problems
Your maas package is only half-upgraded. Cobbler and maas-import-isos no longer exist so I am going to re-target this to the Ubuntu package as it looks like packaging problems to me. ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** No longer affects: maas -- 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
