[2.2.0+bzr6057-snap] Stacktrace appears when pointing to a non-existent region controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Adequate error handling is missing from the MAAS snap.
When putting the snap in 'region' mode and pointing to the default MAAS URL a stacktrace can be displayed. The user could instead be presented with something like:
"There is no functional region controller available at the specified URL."
$ snap info maas
.
.
.
tracking: stable
installed: 2.2.0+bzr6057-snap (91) 98MB devmode
refreshed: 2017-05-30 16:15:09 +0000 UTC
channels:
latest/stable: 2.2.0+bzr6057-snap (91) 98MB -
latest/edge: trunk+bzr6071-snap (101) 98MB devmode
$ sudo maas init
Mode (all/region+
MAAS URL [default=http://
Traceback (most recent call last):
File "/snap/
sys.exit(run())
File "/snap/
return maascli.main()
File "/snap/
options.
File "/snap/
raise exc
File "/snap/
self.
File "/snap/
help_
KeyError: 'database_host'
Unsurprisingly, the same thing happens for mode 'region+rack'.
Oddly, no error is generated at all when 'rack' mode is chosen, even though there is no region controller to connect to:
$ sudo maas init
Mode (all/region+
MAAS URL [default=http://
Secret: kjkj
$ sudo maas status
dhcpd STOPPED Not started
dhcpd6 STOPPED Not started
ntp RUNNING pid 6064, uptime 0:01:41
rackd RUNNING pid 6066, uptime 0:01:41
tgt RUNNING pid 6225, uptime 0:01:22
Does this mean that the rack controller was installed but is not registered (with a region controller)?
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Hi Peter, can you clarify this "When putting the snap in 'region' mode and pointing to the default MAAS ".
Is this when pointing a rack controller to a non-existing region, or is this when pointing the region controller to a non-existing region ? The output you are providing seems to be related to the rack and not to a region.