This has been verified in the MAAS QA lab: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-maas/70/artifact/results/artifacts/maas-logs/var/log/maas/celery.log and http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/trusty-adt-maas/279/artifact/results/artifacts/maas-logs/var/log/maas/celery.log/*view*/, only one write_dhcp_config task is fired. Nevermind the traceback in the logs, that's been filed as bug 1328656
This has been verified in the MAAS QA lab: http:// d-jenkins. ubuntu- ci:8080/ view/MAAS/ job/utopic- adt-maas/ 70/artifact/ results/ artifacts/ maas-logs/ var/log/ maas/celery. log and http:// d-jenkins. ubuntu- ci:8080/ view/MAAS/ job/trusty- adt-maas/ 279/artifact/ results/ artifacts/ maas-logs/ var/log/ maas/celery. log/*view* /, only one write_dhcp_config task is fired.
Nevermind the traceback in the logs, that's been filed as bug 1328656