On 15/05/14 09:22, Seth Arnold wrote: > Public bug reported: > > The maas command line client is brittle to unexpected inputs. On trusty, > I tried to run the 'sudo maas createsuperuser' command that I used on > precise, quantal, and saucy, but it failed. I wanted detailed help, so I > ran 'maas -h', and that dumped a stack trace because the file > /home/ubuntu/.maascli.db was owned by root. I tried running a bare > 'maas' to get help, and that gave an error message with instruction to > run a command that isn't actually executable. > > I expected the 'createsuperuser' command to be useful -- hints about its > replacement would be welcome.
On this page http://maas.ubuntu.com/docs1.5/install.html It says to run "sudo maas-region-admin createadmin ..." Is there any reason you missed that that we can help to fix? (In the last release, the maas command was renamed to maas-region-admin, and maas-cli to maas, which has caused some confusion) > I expected a simple error message if a database file isn't readable > rather than a stack trace. > > I expected some simple help regardless of database ownership. This should have happened without the stacktrace, and is the real bug here. I will amend the title accordingly. > I expected the advice about getting help to be usable with copy-and- > paste. Please file a separate bug for that. (Also please file bugs on the upstream maas project) -- 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 to: https://bugs.launchpad.net/maas/+bug/1319600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
