I think the bug here is that we display an unwieldy stack trace rather
than a nice error message.
Running "sudo maas " may cause this bug to occur, since the
~/.maascli.db will be created by the root user, rather than the
currently-logged-in user.
--
You received this bug notification because
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/1319600
** Tags removed: maas-cli
** Tags added: cli
--
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/1319600
Title:
maas-cli stack trace if .maascli.db unreadable
To manage notifications
Is there any reason you missed that that we can help to fix?
Only that in the middle of testing an update I followed the same
directions for precise, quantal, saucy, and noticed no problems until
trusty. Fair's fair, things change, but it would have been nice to have
a hint in the right
