[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2018-05-10 Thread Andres Rodriguez
Hi! **This is an automated message** We believe this is may no longer be an issue in the latest MAAS release. Due to the original date of the bug report, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2017-11-09 Thread Andres Rodriguez
** Changed in: maas Milestone: 2.3.0 => 2.3.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319600 Title: maas-cli stack trace if .maascli.db unreadable To manage notifications about this bug

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2017-11-02 Thread Andres Rodriguez
** Changed in: maas Milestone: None => 2.3.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319600 Title: maas-cli stack trace if .maascli.db unreadable To manage notifications about this bug

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2015-09-28 Thread Mike Pontillo
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

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2015-09-28 Thread Mike Pontillo
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

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2014-10-12 Thread Launchpad Bug Tracker
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

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2014-10-12 Thread Launchpad Bug Tracker
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319600 Title:

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2014-05-15 Thread Raphaël Badin
** 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

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2014-05-15 Thread Raphaël Badin
** Tags removed: maas-cli ** Tags added: cli -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319600 Title: maas-cli stack trace if .maascli.db unreadable To manage notifications about this bug go

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2014-05-14 Thread Seth Arnold
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

[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable

2014-05-14 Thread Seth Arnold
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