| 2018-02-05 16:15:16 |
Jason Hobbs |
bug |
|
|
added bug |
| 2018-02-05 16:15:21 |
Jason Hobbs |
tags |
|
cdo-qa |
|
| 2018-02-05 16:30:32 |
Jason Hobbs |
tags |
cdo-qa |
cdo-qa maas-ha-testing |
|
| 2018-02-05 16:33:21 |
Jason Hobbs |
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 |
|
| 2018-02-05 16:33:33 |
Jason Hobbs |
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.
This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1 |
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.
This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1 |
|
| 2018-02-05 16:36:54 |
Jason Hobbs |
summary |
No user visible error/warning when dhcpd or bind crashes and is restarted |
No user visible error/warning when services crash and restarted |
|
| 2018-02-05 16:37:03 |
Jason Hobbs |
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.
This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1 |
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, and tgtd.
This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1 |
|
| 2018-02-05 16:38:21 |
Jason Hobbs |
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, and tgtd.
This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1 |
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 |
|
| 2018-02-05 16:46:18 |
Andres Rodriguez |
maas: status |
New |
Incomplete |
|
| 2018-02-05 16:52:29 |
Andres Rodriguez |
maas: importance |
Undecided |
Low |
|
| 2018-02-05 16:52:31 |
Andres Rodriguez |
maas: milestone |
|
2.4.x |
|
| 2018-02-05 16:52:34 |
Andres Rodriguez |
maas: status |
Incomplete |
Triaged |
|
| 2018-02-05 16:52:36 |
Andres Rodriguez |
maas: importance |
Low |
Medium |
|
| 2018-02-05 16:53:35 |
Andres Rodriguez |
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. |
|
| 2019-09-19 11:57:20 |
Adam Collard |
maas: status |
Triaged |
Invalid |
|
| 2019-09-19 18:35:13 |
Jason Hobbs |
maas: status |
Invalid |
New |
|
| 2019-09-20 11:45:55 |
Alberto Donato |
maas: status |
New |
Invalid |
|
