[Debian-ha-maintainers] Bug#862248: Bug#862248: No straightforward and permanent way to disable DRBD autostart, no drbd systemd unit file

[Apollon Oikonomopoulos]

Control: severity -1 wishlist

Hi,

On 17:53 Wed 10 May     , Christian Balzer wrote:
> Jessie (backports), systemd.
> 
> When running DRBD with pacemaker it is recommended (and with systemd
> required, see link below) to disable DRBD startup at boot time.
> 
> However:
> ---
> # systemctl disable drbd
> drbd.service is not a native service, redirecting to systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install disable drbd
> insserv: warning: current start runlevel(s) (empty) of script `drbd' overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `drbd' overrides LSB defaults (0 1 6).
> ---
> 
> But since systemd-sysv picks up anything in /etc/init.d/ we get after a
> reboot:
> ---
> # systemctl status drbd
>   drbd.service - LSB: Control drbd resources.
>    Loaded: loaded (/etc/init.d/drbd; generated; vendor preset: enabled)
>    Active: active (exited) since Wed 2017-05-10 10:37:39 JST; 6h ago
>      Docs: man:systemd-sysv-generator(8)
>    CGroup: /system.slice/drbd.service
> ---
> 
> Ways forward would be a unit file for systemd that actually allows disable
> to work as expected or some other means to (permanently) neuter the init.d
> file (instead of an "exit 0" at the top which did the trick for now).

Thanks for the report!

You can always use `systemctl mask drbd.service', which will neuter the 
initscript completely. I'm downgrading the severity to 'wishlist', 
unless `systemctl mask' causes some ill side-effects, in which case 
please change the severity again.

But yes, ideally we should provide a native unit.

Regards,
Apollon