published maas documentation only reflects trunk
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
High
|
Unassigned |
Bug Description
http://
| Once MAAS is installed, you’ll need to create an administrator account:
|
| $ sudo maas createadmin --username=root --<email address hidden>
|
| Substitute your own email address for <email address hidden>. You may
| also use a different username for your administrator account, but
| “root” is a common convention and easy to remember. The command will
| prompt for a password to assign to the new user.
Yet, when I try this with current MAAS from the cloud-tools pocket of
the UCA, I get this:
| root@mabolo:~# maas createadmin --username root --email <email address hidden>
| CommandError: You must provide a password with --password.
It would be nice if 'maas createadmin' worked as the docs claim
because providing the password over the command line is a bad practice
(as it's visible to other users in most environments).
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
There are several problems working in tandem here:
- The cloud tools people make package releases over which I have zero control, and therefore the documentation has every chance of being inconsistent with what they release
- The docs at maas.ubuntu.com reflect the latest release only (and in fact someone recently prematurely pushed out the development docs)
- Huge and backwardly incompatible changes have been made lately which plunges the docs further out of date with what's in the cloud archive
So, the problem you mention with the password was fixed in Trusty/trunk and the docs reflect that, but it doesn't help at all when cloud tools contains an older random version.
I can alleviate this to some extent by publishing different versions of the documentation on maas.ubuntu.com, one for each supported release of maas.