[2.0 beta 2] Trying to enabled dhcp on fabric-1 with IPv4 networks, results in maas-dhcpd6 attempted to be enabled

[Andres Rodriguez]

Trying to enable dhcp on fabric-1 that has 2 IPv4 subnets, results in:

The interesting thig is this: Erro configuring DHCPv4.... DHCPv6 failed

2016-04-14 17:10:23 [RegionServer,1,192.168.100.5] "Error configuring DHCPv4 on rack controller '4y3h7n': DHCPv6 server failed to stop: Service 'maas-dhcpd6' failed to stop. Its current state is 'dead' and 'Result: exit-code'."

fabric-0, has 1 IPv6 subnet and 1 IPv4 subnet.

==> /var/log/maas/maas.log <==
Apr 14 17:09:53 maas00 maas.service_monitor: [ERROR] Service 'maas-dhcpd6' failed to stop. Its current state is 'dead' and 'Result: exit-code'.
Apr 14 17:10:21 maas00 maas.service_monitor: [INFO] Service 'maas-dhcpd' has been restarted. Its current state is 'on' and 'running'.

==> /var/log/maas/regiond.log <==
2016-04-14 17:10:21 [RegionServer,1,192.168.100.5] Successfully configured DHCPv4 on rack controller '4y3h7n'.
2016-04-14 17:10:23 [RegionServer,2,192.168.100.5] Successfully configured DHCPv4 on rack controller '4y3h7n'.

==> /var/log/maas/maas.log <==
Apr 14 17:10:23 maas00 maas.service_monitor: [INFO] Service 'maas-dhcpd6' is not off, it will be stopped.
Apr 14 17:10:23 maas00 maas.service_monitor: [ERROR] Service 'maas-dhcpd6' failed to stop. Its current state is 'dead' and 'Result: exit-code'.

==> /var/log/maas/regiond.log <==
2016-04-14 17:10:23 [RegionServer,1,192.168.100.5] "Error configuring DHCPv4 on rack controller '4y3h7n': DHCPv6 server failed to stop: Service 'maas-dhcpd6' failed to stop. Its current state is 'dead' and 'Result: exit-code'."

==> /var/log/maas/maas.log <==
Apr 14 17:10:23 maas00 maas.service_monitor: [INFO] Service 'maas-dhcpd6' is not off, it will be stopped.
Apr 14 17:10:23 maas00 maas.service_monitor: [ERROR] Service 'maas-dhcpd6' failed to stop. Its current state is 'dead' and 'Result: exit-code'.

==> /var/log/maas/regiond.log <==
2016-04-14 17:10:23 [RegionServer,2,192.168.100.5] "Error configuring DHCPv4 on rack controller '4y3h7n': DHCPv6 server failed to stop: Service 'maas-dhcpd6' failed to stop. Its current state is 'dead' and 'Result: exit-code'."
2016-04-14 17:10:23 [-] 10.90.90.1 - - [14/Apr/2016:21:10:23 +0000] "GET /MAAS/rpc/ HTTP/1.0" 200 388 "-" "provisioningserver.rpc.clusterservic$.ClusterClientService"

subnets: http://paste.ubuntu.com/15839154/

ip add sh usb0:
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.5/24 brd 192.168.100.255 scope global usb0:1
       valid_lft forever preferred_lft forever
    inet 10.90.90.1/24 brd 10.90.90.255 scope global usb0
       valid_lft forever preferred_lft forever
    inet6 fe80::20e:c6ff:fe88:b79f/64 scope link
       valid_lft forever preferred_lft forever

[Blake Rouse (blake-rouse)]

The issue is that the service monitor is expecting the service to be off not dead. Being dead is a valid state of being off as well.