"maas init" doesn't create admin user
Bug #1871356 reported by
Junien F
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Alberto Donato | ||
| 2.7 |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Running MAAS snap 2.7.0-8235-
I ran "maas init" in mode "region+rack", and specified all 3 admin options on the command line (ie --admin-
I had to run "maas createadmin" to get a usable admin user.
Thanks
Related branches
~ack/maas:snap-init-no-user-authconfig-params
- MAAS Lander: Needs Fixing
- Björn Tillenius: Approve
-
Diff: 210 lines (+63/-29)2 files modifiedsrc/maascli/init.py (+38/-12)
src/maascli/snappy.py (+25/-17)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.8.0b1 |
Revision history for this message
| Alberto Donato (ack) wrote | #1 |
Revision history for this message
| Junien F (axino) wrote | #2 |
| Changed in maas: | |
| milestone: | 2.8.0b1 → 2.8.0b2 |
| Changed in maas: | |
| milestone: | 2.8.0b2 → 2.8.0rc1 |
| Changed in maas: | |
| milestone: | 2.8.0b3 → 2.8.0rc1 |
| Changed in maas: | |
| assignee: | nobody → Alberto Donato (ack) |
| Changed in maas: | |
| milestone: | 2.8.0b4 → 2.8.0rc1 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
So it seems this is actually always been the behavior when any mode other than "all" is selected.
I think the reason is that only "all" mode assumes the maas database is being initialized, therefore asking for additional configurations (first admin, external auth config, ...).
When running as "region" or "region+rack", the command currently doesn't know whether it's a new install or a new region is being added.