Merge lp:~paulgear/charm-helpers/enable-disable-service-systemd into lp:charm-helpers
Proposed by
Paul Gear
on 2017-05-20
| Status: | Merged |
|---|---|
| Merged at revision: | 745 |
| Proposed branch: | lp:~paulgear/charm-helpers/enable-disable-service-systemd |
| Merge into: | lp:charm-helpers |
| Diff against target: |
19 lines (+2/-0) 1 file modified
charmhelpers/core/host.py (+2/-0) |
| To merge this branch: | bzr merge lp:~paulgear/charm-helpers/enable-disable-service-systemd |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Stuart Bishop | 2017-05-20 | Approve on 2017-05-23 | |
| charmers | 2017-05-22 | Pending | |
|
Review via email:
|
|||
Description of the Change
See lp:1692178 for background on this. This is a fairly simplistic solution, but the mask/unmask has been left in place, in order not to break anything which relies on masked behaviour from systemd-controlled services. I suspect there are no charms which do this, but have no way to be sure; so this is the safe solution which makes enabling services work.
To post a comment you must log in.
| Stuart Bishop (stub) wrote : | # |
The unmask of course is happening before the enable, so this is fine. While the disable + mask may be redundant, the unmask + enable is not for the case where a service is disabled but not masked.
review:
Approve


How does this address lp:1692178 ? My understanding is that the disable/enable will not have any effect and with the mask still in place pause/resume will still fail.