[2.3, service-tracking] MAAS service tracking never notices tracked daemons crash (ntp is an example) or viceversa
Bug #1747459 reported by
Jason Hobbs
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
| 2.3 |
Triaged
|
High
|
Unassigned | ||
Bug Description
If ntp crashes on a region controller, for example, via SIGSEGV, MAAS never seems to notice. The service indicator in the UI stays green for ntp on that controller, MAAS continues to tell nodes to use the VIP for ntp, even though it may not work.
To reproduce:
1) kill -SIGSEGV <pidof ntpd> on a MAAS region controller.
2) verify that the controller's status never changes and ntp continues to be up.
3) if using HA, verify that crm status shows all units up for the MAAS vip.
This is with 2.3.0-6434-
Related branches
~blake-rouse/maas:lower-service-monitor-loop
- Newell Jensen (community): Approve
-
Diff: 52 lines (+4/-4)4 files modifiedsrc/maasserver/regiondservices/service_monitor_service.py (+1/-1)
src/maasserver/regiondservices/tests/test_service_monitor_service.py (+1/-1)
src/provisioningserver/rackdservices/service_monitor_service.py (+1/-1)
src/provisioningserver/rackdservices/tests/test_service_monitor_service.py (+1/-1)
| tags: | added: cdo-qa maas-ha-testing |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | New → Incomplete |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #2 |
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote | #3 |
| Changed in maas: | |
| status: | Incomplete → New |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #4 |
| Changed in maas: | |
| importance: | Undecided → Critical |
| milestone: | none → 2.4.x |
| milestone: | 2.4.x → 2.4.0alpha1 |
| status: | New → Triaged |
| importance: | Critical → High |
| summary: |
- MAAS never notices that ntp crashes + MAAS service tracking never notices tracked daemons crash (ntp is an + example) |
| Changed in maas: | |
| milestone: | 2.4.0alpha1 → 2.4.0alpha2 |
Revision history for this message
| Andres Rodriguez (andreserl) wrote Re: MAAS service tracking never notices tracked daemons crash (ntp is an example) or viceversa | #5 |
| summary: |
MAAS service tracking never notices tracked daemons crash (ntp is an - example) + example) or viceversa |
| Changed in maas: | |
| importance: | High → Critical |
| Changed in maas: | |
| milestone: | 2.4.0alpha2 → 2.4.0beta1 |
| summary: |
- MAAS service tracking never notices tracked daemons crash (ntp is an - example) or viceversa + [2.4, service-tracking] MAAS service tracking never notices tracked + daemons crash (ntp is an example) or viceversa |
| Changed in maas: | |
| milestone: | 2.4.0beta1 → 2.4.0beta2 |
| Changed in maas: | |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| summary: |
- [2.4, service-tracking] MAAS service tracking never notices tracked + [2.3, service-tracking] MAAS service tracking never notices tracked daemons crash (ntp is an example) or viceversa |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #6 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
How long did you wait to make the determination that the service crash wasn't noticed by MAAS?
Also, did you confirm that system *never* tried to start the service again ?