hacluster is missing systemd support
Bug #1843933 reported by
Mike Wilson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-interface-hacluster |
Fix Released
|
Undecided
|
Mike Wilson | ||
Bug Description
The function add_init_service adds an lsb, which is designed for upstart. Systemd is also supported and injects an drop-in to alter the service. I noticed this while testing hacluster on Charmed Kubernetes since the systemd services were not properly handled. I think the shim for upstart to systemd is now missing.
| description: | updated |
| Changed in charm-interface-hacluster: | |
| assignee: | nobody → Mike Wilson (knobby) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-interface-hacluster (master) | #1 |
| Changed in charm-interface-hacluster: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit e1d44c258a83ff1
Author: Mike Wilson <email address hidden>
Date: Fri Sep 13 14:10:35 2019 -0400
Add support for systemd
Systemd support is in corosync, but currently the add_init_service
handles adding an upstart service only. This results in Charmed
Kubernetes having incorrectly monitored services.
Change-Id: I935613292ce6b7
Closes-Bug: #1843933