MAAS sends multiple stop_dhcp_server tasks even though there's no dhcp server running.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Raphaël Badin |
Bug Description
As seen here: http://
A restart task triggered later on restarted the service. It seems that the MAAS server is trying to stop the dhcp server but fails because it wasn't running in the first place.
Package version: 1.6+bzr2367+
[2014-06-10 16:45:07,400: INFO/MainProcess] Received task: provisioningser
[2014-06-10 16:45:08,055: ERROR/Worker-2] stop_dhcp_server: Command `sudo -n service maas-dhcp-server stop` returned non-zero exit status 1:
stop: Unknown instance:
[2014-06-10 16:45:08,063: ERROR/MainProcess] Task provisioningser
Traceback (most recent call last):
File "/usr/lib/
R = retval = fun(*args, **kwargs)
File "/usr/lib/
return self.run(*args, **kwargs)
File "/usr/lib/
func(*args, **kwargs)
File "/usr/lib/
call_
File "/usr/lib/
raise ExternalProcess
ExternalProcess
Related branches
- Jeroen T. Vermeulen (community): Approve
-
Diff: 105 lines (+58/-2)2 files modifiedsrc/provisioningserver/tasks.py (+26/-1)
src/provisioningserver/tests/test_tasks.py (+32/-1)
Changed in maas: | |
assignee: | nobody → Raphaël Badin (rvb) |
status: | Triaged → Fix Committed |
milestone: | none → 1.6.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
http:// d-jenkins. ubuntu- ci:8080/ view/MAAS/ job/utopic- adt-maas/ 70/artifact/ results/ artifacts/ maas-logs/ var/log/ maas/celery. log/*view* / shows the same error running the tests on a trusty testbed