MAAS

Service checking on utopic wrongly assumes the system is using systemd.

Bug #1459338 reported by Raphaël Badin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Raphaël Badin

Bug Description

On utopic, systemctl exists (http://paste.ubuntu.com/11394085/) and so the service checking machinery assumes it should use systemd instead of upstart to check/restart services (http://paste.ubuntu.com/11394158/); more precisely, the service checking code fails to parse the output of "service maas-dhcpd status": May 27 07:57:44 autopkgtest maas.dhcp: [ERROR] DHCPv4 server failed to restart (for network interfaces eth1): Unable to parse the output from systemd for service 'maas-dhcpd'.

See original description

Related branches

lp:~rvb/maas/init-sys-bug-1459338
Andres Rodriguez (community): Approve
Blake Rouse (community): Approve
Diff: 152 lines (+52/-39)
4 files modified
src/provisioningserver/service_monitor.py (+2/-10)
src/provisioningserver/tests/test_service_monitor.py (+6/-29)
src/provisioningserver/utils/__init__.py (+19/-0)
src/provisioningserver/utils/tests/test_utils.py (+25/-0)
Raphaël Badin (rvb)
description: updated
Revision history for this message
Gavin Panella (allenap) wrote :

Some hints about how to figure it out correctly:

  $ cat /proc/1/comm # on Trusty
  init
  $ cat /proc/1/comm # on Vivid
  systemd

Raphaël Badin (rvb)
Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Triaged → In Progress
Raphaël Badin (rvb)
Changed in maas:
status: In Progress → Fix Committed
Andres Rodriguez (andreserl)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.