MaaS WebUI does not work after reboot
Bug #1199469 reported by
Pavel Malyshev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Undecided
|
Unassigned | ||
maas (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
It is not possible to login to MaaS WebUI after controller reboot.
I've installed MaaS from Raring server CD. Configured superuser and added images.
I've installed maas-dhcp and maas-dns and configured them specifing new node-group-
I was able to login to WebUI.
After that I've rebooted as DHCP didn't come up.
After reboot I'm not able to login to WebUI. Browser says "The server encountered and internal error ..."
Restarting apache and rebooting does not help.
Apache error logs contains maasserver related exceptions at start up and exceptions on requsts to WebUI.
Changed in maas (Ubuntu): | |
importance: | Undecided → High |
Changed in maas: | |
status: | Incomplete → Won't Fix |
Changed in maas (Ubuntu): | |
status: | New → Won't Fix |
To post a comment you must log in.
Looking at the logs it seems that something is misconfigured for DHCP causing this error:
ValidationError: {u'subnet_mask': [u"That field cannot be empty (unless that interface is 'unmanaged')"]}
Please make sure that your DHCP configuration is correct, or set the interface you are trying to manage to unmanaged again in order to allow the UI to work agian.