I think the bug here is that we display an unwieldy stack trace rather than a nice error message.
Running "sudo maas <anything>" may cause this bug to occur, since the ~/.maascli.db will be created by the root user, rather than the currently-logged-in user.
I think the bug here is that we display an unwieldy stack trace rather than a nice error message.
Running "sudo maas <anything>" may cause this bug to occur, since the ~/.maascli.db will be created by the root user, rather than the currently-logged-in user.