maas dbshell stacktraces in package

[Scott Moser]

$ sudo maas dbshell
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 443, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 261, in fetch_command
    klass = load_command_class(app_name, subcommand)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 69, in load_command_class
    module = import_module('%s.management.commands.%s' % (app_name, 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/management/commands/dbshell.py", line 19, in <module>
    from maasserver.testing.database import MAASClusterFixture
ImportError: No module named testing.database

$ dpkg-query --show maas
maas 0.1+bzr1063+dfsg-0+1099+98~ppa0~quantal1

[Gavin Panella (allenap)]

I think the answer to this is to fix bug 1052879, then this command is not exposed as part of maas's front-end. I don't think we should be exposing the whole of django-admin (which is what the maas command is).

[Julian Edwards (julian-edwards)]

I'd like to fix this as it's quite useful to be able to do DB surgery as part of support. But it's not important right now compared to everything else.

[Julian Edwards (julian-edwards)]

Can we make this command detect packaged vs development env and DTRT?