maas dbshell stacktraces in package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Jeroen T. Vermeulen |
Bug Description
$ sudo maas dbshell
Traceback (most recent call last):
File "/usr/bin/
management.
File "/usr/lib/
utility.
File "/usr/lib/
self.
File "/usr/lib/
klass = load_command_
File "/usr/lib/
module = import_
File "/usr/lib/
__import_
File "/usr/lib/
from maasserver.
ImportError: No module named testing.database
$ dpkg-query --show maas
maas 0.1+bzr1063+
Related branches
- Gavin Panella (community): Approve
-
Diff: 152 lines (+123/-6)2 files modifiedsrc/maasserver/management/commands/dbshell.py (+44/-6)
src/maasserver/tests/test_commands_dbshell.py (+79/-0)
Changed in maas: | |
assignee: | nobody → Jeroen T. Vermeulen (jtv) |
status: | Triaged → In Progress |
milestone: | none → 14.04 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
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).