Installing MAAS from cloud-tools-next on precise fails

Bug #1289489 reported by Ryan Harper
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Andres Rodriguez
Ubuntu Cloud Archive
Expired
Undecided
Unassigned
maas (Ubuntu)
Invalid
Undecided
Andres Rodriguez

Bug Description

Reproduction Steps:

1. boot a precise cloud image
2. sudo apt-add-repository -r -y ppa:ubuntu-cloud-archive/cloud-tools-next
3. sudo apt-get update && sudo apt-get install maas
During install, failure appears like this:

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)
Traceback (most recent call last):
  File "/usr/bin/django-admin", line 5, in <module>
    management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/dist-packages/south/management/commands/migrate.py", line 105, in handle
    ignore_ghosts = ignore_ghosts,
  File "/usr/lib/python2.7/dist-packages/south/migration/__init__.py", line 158, in migrate_app
    Migrations.calculate_dependencies()
  File "/usr/lib/python2.7/dist-packages/south/migration/base.py", line 227, in calculate_dependencies
    migration.calculate_dependencies()
  File "/usr/lib/python2.7/dist-packages/south/migration/base.py", line 355, in calculate_dependencies
    for migration in self._get_dependency_objects("depends_on"):
  File "/usr/lib/python2.7/dist-packages/south/migration/base.py", line 335, in _get_dependency_objects
    for app, name in getattr(self.migration_class(), attrname, []):
  File "/usr/lib/python2.7/dist-packages/south/migration/base.py", line 307, in migration_class
    return self.migration().Migration
  File "/usr/lib/python2.7/dist-packages/south/utils.py", line 62, in method
    value = function(self)
  File "/usr/lib/python2.7/dist-packages/south/migration/base.py", line 296, in migration
    raise exceptions.UnknownMigration(self, sys.exc_info())
south.exceptions.UnknownMigration: Migration 'maasserver:0066_rename_vlan_add_link_node_network' probably doesn't exist.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/south/migration/base.py", line 294, in migration
    migration = __import__(full_name, {}, {}, ['Migration'])
  File "/usr/lib/python2.7/dist-packages/maasserver/migrations/0066_rename_vlan_add_link_node_network.py", line 4, in <module>
    from south.utils import datetime_utils as datetime
ImportError: cannot import name datetime_utils

Checked if it was part of the package:
ubuntu@maas-server:~$ dpkg -L python-django-south | grep datetime_utils
ubuntu@maas-server:~$ dpkg --list | grep python-django-south
ii python-django-south 0.7.3-1ubuntu1

The file is part of 0.7.5 as I can see on saucy:

(foudres) oil % cat /etc/issue
Ubuntu 13.10 \n \l

(foudres) oil % dpkg --list | grep python-django-south
ii python-django-south 0.7.5-1 all Intelligent schema migrations for django apps
(foudres) oil % dpkg -L python-django-south | grep datetime_utils
/usr/share/pyshared/south/utils/datetime_utils.py
/usr/lib/python2.7/dist-packages/south/utils/datetime_utils.py

Maas versions:
ubuntu@maas-server:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==================================-===========================================-==========================================================================
iU maas 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server
ii maas-cli 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Client Tool
ii maas-cluster-controller 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Cluster Controller
ii maas-common 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server
ii maas-dhcp 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server - DHCP Configuration (meta-package)
iU maas-dns 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server - DNS configuration (metapackage)
iF maas-region-controller 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server
ii maas-region-controller-min 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server
ii python-django-maas 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server - (django files)
ii python-maas-client 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS API Client - (python files)
ii python-maas-provisioningserver 1.5+bzr1977-0ubuntu2~ctools0 Ubuntu MAAS Server

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Assigned to both ubuntu mpackage and maas trunk because the package should have a versioned dependency on python-django-south, which should have come from upstream.

Changed in maas:
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas (Ubuntu):
assignee: nobody → Andres Rodriguez (andreserl)
Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 1289489] Re: Installing MAAS from cloud-tools-next on precise fails

On Friday 07 Mar 2014 17:20:42 you wrote:
> Assigned to both ubuntu mpackage and maas trunk because the package
> should have a versioned dependency on python-django-south, which should
> have come from upstream.

I don't think this should be on upstream, the package versioning is all done
in packaging. What did you have in mind to change in the maas code?

Changed in maas:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in maas (Ubuntu):
status: New → Confirmed
Changed in maas:
status: Incomplete → Invalid
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Hi Ryan, I tried this in a pristine precise VM with the current version of maas in cloud-tools-next (1.5+bzr2252-0ubuntu1~ctools0) and didn't get any errors during install. I didn't get errors when I ran the upgrade test from cloud-tools to cloud-tools-next either so I'm closing this as invalid. Please re-open if you are able to reproduce.
Thanks!

Changed in maas (Ubuntu):
status: Confirmed → Invalid
James Page (james-page)
Changed in cloud-archive:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-cloud-archive because there has been no activity for 60 days.]

Changed in cloud-archive:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.