[Maas-devel] Signals for DHCP changes still broken

[Julian Edwards]

The dhcp probe task is still causing the dhcp config to get rewritten on my 
box.  This is using the very latest daily build:
1.4+bzr1853+dfsg+1898+231~ppa0~ubuntu14.04.1

/var/log/maas/celery.log:
[2014-02-07 09:48:17,151: INFO/MainProcess] Task 
provisioningserver.tasks.periodic_probe_dhcp[e96c29f4-ba0d-48ee-
b09d-8587f94d7dc7] succeeded in 3.513536813s: None
[2014-02-07 09:48:17,961: INFO/MainProcess] Task 
provisioningserver.tasks.write_dhcp_config[171180a4-
aba7-447b-8d6a-6f60723ccd69] succeeded in 0.89445007s: None
[2014-02-07 09:48:17,964: INFO/MainProcess] Received task: 
provisioningserver.tasks.restart_dhcp_server[61c83b46-092e-4afc-
af1d-43d42e8adf34]
[2014-02-07 09:48:18,058: INFO/MainProcess] Task 
provisioningserver.tasks.restart_dhcp_server[61c83b46-092e-4afc-
af1d-43d42e8adf34] succeeded in 0.092753507s: None
[2014-02-07 09:49:12,230: INFO/Beat] Scheduler: Sending due task 
unconditional-dhcp-lease-upload (provisioningserver.tasks.upload_dhcp_leases)
[2014-02-07 09:49:12,234: INFO/Beat] Scheduler: Sending due task probe-dhcp-
servers (provisioningserver.tasks.periodic_probe_dhcp)
[2014-02-07 09:49:12,235: INFO/MainProcess] Received task: 
provisioningserver.tasks.upload_dhcp_leases[915c11c6-ea19-43ad-
af51-0ade6966d9c2]
[2014-02-07 09:49:12,246: INFO/MainProcess] Received task: 
provisioningserver.tasks.periodic_probe_dhcp[6469abb2-2d2e-45e0-be25-
eeacf3a745c4]
[2014-02-07 09:49:12,413: INFO/MainProcess] Task 
provisioningserver.tasks.upload_dhcp_leases[915c11c6-ea19-43ad-
af51-0ade6966d9c2] succeeded in 0.176264391s: None
[2014-02-07 09:49:15,742: ERROR/Worker-3] Ignoring DHCP scan for lxcbr0, it no 
longer exists. Check your cluster interfaces configuration.
[2014-02-07 09:49:15,846: INFO/MainProcess] Received task: 
provisioningserver.tasks.write_dhcp_config[cf5828ae-
b63e-44b8-9fce-30b9c7c61279]
[2014-02-07 09:49:15,886: INFO/MainProcess] Task 
provisioningserver.tasks.periodic_probe_dhcp[6469abb2-2d2e-45e0-be25-
eeacf3a745c4] succeeded in 3.473343046s: None
[2014-02-07 09:49:16,918: INFO/MainProcess] Received task: 
provisioningserver.tasks.restart_dhcp_server[d0bc8d95-3936-4c81-a569-
b3bb7f9451b9]
[2014-02-07 09:49:16,925: INFO/MainProcess] Task 
provisioningserver.tasks.write_dhcp_config[cf5828ae-
b63e-44b8-9fce-30b9c7c61279] succeeded in 1.077313058s: None
[2014-02-07 09:49:17,053: INFO/MainProcess] Task 
provisioningserver.tasks.restart_dhcp_server[d0bc8d95-3936-4c81-a569-
b3bb7f9451b9] succeeded in 0.127430325s: None

I'm also seeing the region celery log doing something similar:

/var/log/maas/celery-region.log:
[2014-02-07 09:50:45,122: INFO/MainProcess] Task 
provisioningserver.tasks.write_full_dns_config[06ece4a4-7e13-418a-9e08-1c73a0614bac] 
succeeded in 14.680276781s: None
[2014-02-07 09:50:45,124: INFO/MainProcess] Received task: 
provisioningserver.tasks.rndc_command[9acef0f8-52e5-4469-a218-7be039b53cb3]
[2014-02-07 09:50:45,173: INFO/MainProcess] Task 
provisioningserver.tasks.rndc_command[9acef0f8-52e5-4469-a218-7be039b53cb3] 
succeeded in 0.0473858280002s: None
[2014-02-07 09:51:15,773: INFO/MainProcess] Received task: 
provisioningserver.tasks.write_full_dns_config[cc584309-
a6d0-4aa1-998d-2a059eafc9cd]
[2014-02-07 09:51:15,875: INFO/MainProcess] Received task: 
provisioningserver.tasks.write_full_dns_config[9dd3dcac-7c50-4a0c-97bc-0bdef4585ad3]
[2014-02-07 09:51:30,385: INFO/MainProcess] Task 
provisioningserver.tasks.write_full_dns_config[cc584309-
a6d0-4aa1-998d-2a059eafc9cd] succeeded in 14.609658213s: None
[2014-02-07 09:51:30,388: INFO/MainProcess] Received task: 
provisioningserver.tasks.rndc_command[3bb93aaa-49f9-416d-a3d0-15026450eba0]
[2014-02-07 09:51:44,908: INFO/MainProcess] Task 
provisioningserver.tasks.write_full_dns_config[9dd3dcac-7c50-4a0c-97bc-0bdef4585ad3] 
succeeded in 14.523519088s: None
[2014-02-07 09:51:44,911: INFO/MainProcess] Received task: 
provisioningserver.tasks.rndc_command[022d1817-78d8-4af9-a8d6-e7eb583ed566]
[2014-02-07 09:51:44,949: INFO/MainProcess] Task 
provisioningserver.tasks.rndc_command[3bb93aaa-49f9-416d-a3d0-15026450eba0] 
succeeded in 0.0395799510002s: None
[2014-02-07 09:51:46,555: INFO/MainProcess] Task 
provisioningserver.tasks.rndc_command[022d1817-78d8-4af9-a8d6-e7eb583ed566] 
succeeded in 1.607736075s: None

There is only my MAAS DHCP server on the network, which is ignored.  Maybe 
that triggers a bug in the field change code?