[feature] MAAS service tracking should provide user visible notifications/events on service crash/restart.

Bug #1747458 reported by Jason Hobbs on 2018-02-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Medium
Unassigned

Bug Description

If dhcpd crashes on a node, for example, via a segfault, maas.service_monitor will restart it.

However, no warnings are generated for the user in the UI or in the API. It seems like it should at least generate an event in the controller's log, and maybe a warning in the UI.

The same applies for bind, haproxy, tgtd and ntp (which is never restarted).

This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1

tags: added: cdo-qa
tags: added: maas-ha-testing
summary: - No user visible error/warning when dhcpd crashes and is restarted
+ No user visible error/warning when dhcpd or bind crashes and is
+ restarted
description: updated
summary: - No user visible error/warning when dhcpd or bind crashes and is
- restarted
+ No user visible error/warning when services crash and restarted
description: updated
description: updated

How long did you wait to make the determination that the service crash wasn't noticed by MAAS?

Also, are you sure that the service wasn't restarted by systemd and remained in a crashed state, and MAAS just simply never noticed that?

Changed in maas:
status: New → Incomplete
Changed in maas:
importance: Undecided → Low
milestone: none → 2.4.x
status: Incomplete → Triaged
importance: Low → Medium
summary: - No user visible error/warning when services crash and restarted
+ [feature] MAAS service tracking should provide user visible
+ notifications/events on service crash/restart.
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers