Raises CannotConfigureDHCP when saving managedcluster interface.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | MAAS |
High
|
Unassigned | ||
Bug Description
Trunk (as of 11/24/2014) gives an "Internal server error." when trying to save a managed interface.
This was performed on a fresh MAAS installation (from packages).
Here is the relevant output from /var/log/
==> /var/log/
return do_configure_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
client(command, omapi_key=
File "/usr/lib/
result.
File "<string>", line 2, in raiseException
CannotConfigure
start: Job failed to start
==> /var/log/
Nov 24 13:19:23 mc maas.tftp: [WARNING] No boot images have been imported from the region.
Nov 24 13:15:21 mc maas.tftp: message repeated 2 times: [ [WARNING] No boot images have been imported from the region.]
Nov 24 13:19:42 mc maas: [WARNING] Failed to create Network when adding/editing cluster interface eth0-eth0 with error [{'ip': [u'Network with this Ip already exists.'], 'name': [u'Network with this Name already exists.']}]. This is OK if it already exists.
Nov 24 13:15:05 mc maas.tftp: [WARNING] No boot images have been imported from the region.
Nov 24 13:19:47 mc maas.calls: [INFO] Starting task 'write_
Nov 24 13:19:47 mc maas.calls: [INFO] Starting task 'rndc_command' with args: ([u'reload'], False) {}
Nov 24 13:19:47 mc maas.calls: [INFO] Finished task 'rndc_command' with args: ([u'reload'], False) {}
Nov 24 13:19:47 mc maas.calls: [INFO] Finished task 'write_
Nov 24 13:19:43 mc maas.tftp: message repeated 55 times: [ [WARNING] No boot images have been imported from the region.]
Nov 24 13:19:47 mc maas.dhcp: [ERROR] DHCPv4 server failed to restart (for network interfaces eth0): Command `sudo -n service maas-dhcpd restart` returned non-zero exit status 1:#012stop: Unknown instance: #012start: Job failed to start
==> /var/log/
2014-11-24 13:04:05-0800 [Uninitialized] ClusterClient connection established (HOST:IPv4Addre
2014-11-24 13:04:05-0800 [Uninitialized] ClusterClient connection established (HOST:IPv4Addre
2014-11-24 13:04:05-0800 [ClusterClient,
2014-11-24 13:04:05-0800 [ClusterClient,
2014-11-24 13:04:05-0800 [ClusterClient,
2014-11-24 13:04:05-0800 [ClusterClient,
2014-11-24 13:04:06-0800 [ClusterClient,
2014-11-24 13:04:06-0800 [ClusterClient,
2014-11-24 13:04:06-0800 [ClusterClient,
2014-11-24 13:04:06-0800 [ClusterClient,
ubuntu@mc:~$ dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.7.1+bzr3373-
ii maas-cli 1.7.1+bzr3373-
ii maas-cluster-
ii maas-common 1.7.1+bzr3373-
ii maas-dhcp 1.7.1+bzr3373-
ii maas-dns 1.7.1+bzr3373-
ii maas-proxy 1.7.1+bzr3373-
ii maas-region-
ii maas-region-
ii python-django-maas 1.7.1+bzr3373-
ii python-maas-client 1.7.1+bzr3373-
ii python-
| Changed in maas: | |
| status: | New → Triaged |
| Andres Rodriguez (andreserl) wrote : | #1 |
| Christian Reis (kiko) wrote : | #2 |
See also bug 1361673
| summary: |
- Internal Server Error when saving managed cluster interface. + Raises CannotConfigureDHCP when saving managedcluster interface. |
| Christian Reis (kiko) wrote : | #3 |
There is a hint in the bug report. The error message is:
CannotConfigu
start: Job failed to start
The first error occurs when you attempt to stop a service which is already stopped:
kiko@
dmesg stop/waiting
kiko@
stop: Unknown instance:
What appears to have happened is that there was an error starting the DHCP server, which can happen when there is an error in the config file; here's what happens when you have a broken file:
kiko@chorus:~$ sudo start isc-dhcp-server
start: Job failed to start
The syslog output is invaluable in that situation:
kiko@chorus:~$ sudo tail /var/log/syslog
Feb 12 15:37:51 chorus dhcpd: key "rndc-key";
Feb 12 15:37:51 chorus dhcpd: ^
Feb 12 15:37:51 chorus dhcpd: /etc/dhcp/
Feb 12 15:37:51 chorus dhcpd: key "rndc-key"
Feb 12 15:37:51 chorus dhcpd: ^
Feb 12 15:37:51 chorus dhcpd: /etc/dhcp/
Feb 12 15:37:51 chorus dhcpd: key "rndc-key"
Feb 12 15:37:51 chorus dhcpd: ^
Feb 12 15:37:51 chorus dhcpd: Configuration file errors encountered -- exiting
Feb 12 15:37:51 chorus kernel: [376499.698220] init: isc-dhcp-server pre-start process (1011) terminated with status 1
I'm afraid without syslog output we can't easily help this one.
| Christian Reis (kiko) wrote : | #4 |
We had a user report a similar error on IRC, with the following error: http://
| Christian Reis (kiko) wrote : | #5 |
That one is different:
Feb 10 12:07:16 vmslab-maas maas.dhcp: [ERROR] Could not rewrite DHCPv4 server configuration (for network interfaces eth1): Command `sudo -n maas-provision atomic-write --filename /etc/maas/
Now why would atomic_write() fail?
I'm a bit confused as to what ActionScript.
| Raphaël Badin (rvb) wrote : | #6 |
@Newell:
Can you please have a look in upstart's log: /var/log/
Also, please attach the result of `ifconfig` and the content of /etc/maas/
| Raphaël Badin (rvb) wrote : | #7 |
@Newell: is this running from within a LXC machine by any chance?
| Newell Jensen (newell-jensen) wrote : Re: [Bug 1395896] Re: Raises CannotConfigureDHCP when saving managedcluster interface. | #8 |
No this was not running within an LXC machine. This was on my host
machine. I have not been able to reproduce this with the current code. I
will need to try and re-install that specific branch and see if I can
reproduce it.
On Tue, Feb 17, 2015 at 2:03 PM, Raphaël Badin <email address hidden>
wrote:
> @Newell: is this running from within a LXC machine by any chance?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Raises CannotConfigureDHCP when saving managedcluster interface.
>
> Status in MAAS:
> Triaged
>
> Bug description:
> Trunk (as of 11/24/2014) gives an "Internal server error." when trying
> to save a managed interface.
>
> This was performed on a fresh MAAS installation (from packages).
>
> Here is the relevant output from /var/log/
>
> ==> /var/log/
> return do_configure_
> File
> "/usr/lib/
> line 148, in wrapper
> return func(*args, **kwargs)
> File "/usr/lib/
> in do_configure_dhcp
> client(command, omapi_key=
> File "/usr/lib/
> 219, in wait
> result.
> File "<string>", line 2, in raiseException
> CannotConfigure
> instance:
> start: Job failed to start
>
> ==> /var/log/
> Nov 24 13:19:23 mc maas.tftp: [WARNING] No boot images have been
> imported from the region.
> Nov 24 13:15:21 mc maas.tftp: message repeated 2 times: [ [WARNING] No
> boot images have been imported from the region.]
> Nov 24 13:19:42 mc maas: [WARNING] Failed to create Network when
> adding/editing cluster interface eth0-eth0 with error [{'ip': [u'Network
> with this Ip already exists.'], 'name': [u'Network with this Name already
> exists.']}]. This is OK if it already exists.
> Nov 24 13:15:05 mc maas.tftp: [WARNING] No boot images have been
> imported from the region.
> Nov 24 13:19:47 mc maas.calls: [INFO] Starting task
> 'write_
> [<provisionings
> 0x7f09b808d550>, <provisioningse
> object at 0x7f09b808dd90>], 'callback':
> provisioningser
> None, 'trusted_networks': u'192.168.
> Nov 24 13:19:47 mc maas.calls: [INFO] Starting task 'rndc_command' with
> args: ([u'reload'], False) {}
> Nov 24 13:19:47 mc maas.calls: [INFO] Finished task 'rndc_command' with
> args: ([u'reload'], False) {}
> Nov 24 13:19:47 mc maas.calls: [INFO] Finished task
> 'write_
> [<provisionings
> 0x7f09b808d550>, <provisioningse
> object at 0x7f09b808dd90>], 'callback':
> provisioningser
| Changed in maas: | |
| milestone: | next → 1.8.0 |
| importance: | Critical → High |
| Andres Rodriguez (andreserl) wrote : | #9 |
Hi Newell,
I';m marking this as incomplete as we have not been able to reproduce. If you can confirm it is still present it can be marked back as new.
| Changed in maas: | |
| status: | Triaged → Incomplete |
| mahmoh (mahmoh) wrote : | #10 |
I can reproduce I believe:
$ Jun 17 12:25:22 maas maas.calls: [INFO] Starting task 'write_
Jun 17 12:25:22 maas maas.calls: [INFO] Starting task 'rndc_command' with args: ([u'reload'], False) {}
Jun 17 12:25:22 maas maas.tasks: [ERROR] rndc_command failed: Command `rndc -c /etc/bind/
Jun 17 12:25:22 maas maas.tasks: [ERROR] rndc_command: Command `rndc -c /etc/bind/
Jun 17 12:25:22 maas maas.tasks: [ERROR] write_full_
ERROR 2015-06-17 12:25:22,493 django.request Internal Server Error: /MAAS/clusters/
Traceback (most recent call last):
File "/usr/lib/
response = wrapped_
File "/usr/lib/
return view_func(request, *args, **kwargs)
File "/usr/lib/
return self.dispatch(
File "/usr/lib/
return handler(request, *args, **kwargs)
File "/usr/lib/
return super(BaseUpdat
File "/usr/lib/
return self.form_
File "/usr/lib/
return super(ClusterIn
File "/usr/lib/
self.object = form.save()
File "/usr/lib/
interface = super(Nod...
| Changed in maas: | |
| status: | Incomplete → New |
| mahmoh (mahmoh) wrote : | #11 |
^, I can reproduce this on both 1.7 & 1.8:
$ dpkg -l | grep maas
ii maas 1.7.5+bzr3369-
ii maas-cli 1.7.5+bzr3369-
ii maas-cluster-
ii maas-common 1.7.5+bzr3369-
ii maas-dhcp 1.7.5+bzr3369-
ii maas-dns 1.7.5+bzr3369-
ii maas-proxy 1.7.5+bzr3369-
ii maas-region-
ii maas-region-
ii python-django-maas 1.7.5+bzr3369-
ii python-maas-client 1.7.5+bzr3369-
ii python-
| mahmoh (mahmoh) wrote : | #12 |
$ Jun 17 12:54:06 maas maas.tftp: [WARNING] No boot images have been imported from the region.
Jun 17 12:55:51 maas maas.bootsources: [INFO] Updated boot sources cache.
Jun 17 12:55:51 maas maas.bootresources: [INFO] Started importing of boot images from 1 source(s).
Jun 17 12:55:53 maas maas.bootresources: [INFO] Importing images from source: http://
Jun 17 12:56:58 maas maas: [WARNING] Failed to create Network when adding/editing cluster interface maas-p4p1 with error [{'ip': [u'Network with this Ip already exists.'], 'name': [u'Network with this Name already exists.']}]. This is OK if it already exists.
Jun 17 12:56:58 maas maas.dns: [ERROR] Reloading BIND failed: Command `rndc -c /etc/bind/
Jun 17 12:57:07 maas maas: [WARNING] Failed to create Network when adding/editing cluster interface maas-p4p1 with error [{'ip': [u'Network with this Ip already exists.'], 'name': [u'Network with this Name already exists.']}]. This is OK if it already exists.
Jun 17 12:57:07 maas maas.dns: [ERROR] Reloading BIND failed: Command `rndc -c /etc/bind/
Jun 17 12:57:13 maas maas.bootresources: [INFO] Finished importing of boot images from 1 source(s).
Jun 17 12:57:13 maas maas.import-images: [INFO] Started importing boot images.
tail -f regiond.log
* the key is invalid.
2015-06-17 12:57:07 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:57:13 [RegionServer,
2015-06-17 12:57:13 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:57:13 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:57:13 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:57:14 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:57:22 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:57:31 [-] 192.168.2.1 - - [17/Jun/
2015-06-17 12:58:01 [-] 192.168.2.1 - - [17/Jun/
| Changed in maas: | |
| status: | New → Triaged |
| Blake Rouse (blake-rouse) wrote : | #13 |
I beleive this has been fixed for a while.
| Changed in maas: | |
| status: | Triaged → Invalid |


Hi Newell,
Can you please verify this happens in the latest 1.7.1 which is in experimental?
Also, please provide an step by step and a sample configuration of the NIC's of your system to see if we can reproduce it.