Comment 6 for bug 1809682

Actually removing the sysv script is not an acceptable fix for this error. I mean, it might come to a day where we will disable all sysv inits, but, for now, they are called by systemd through systemd generator mechanism (https://www.freedesktop.org/software/systemd/man/systemd-sysv-generator.html) and the fix for this bug is:

change /etc/init.d/corosync-qdevice header to:

### BEGIN INIT INFO
# Provides: corosync-qdevice
# Required-Start: $remote_fs $syslog corosync
# Required-Stop: $remote_fs $syslog corosync
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Corosync Qdevice daemon
# Description: Starts and stops Corosync Qdevice daemon.
### END INIT INFO

(adding 2 3 4 5 in Default-Start)

And updating rc*.d scripts:

(c)inaddy@temp:~$ sudo update-rc.d -f corosync-qdevice remove
(c)inaddy@temp:~$ sudo update-rc.d -f corosync-qdevice defaults

And then:

(c)inaddy@temp:~$ systemctl enable corosync-qdevice.service
Synchronizing state of corosync-qdevice.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable corosync-qdevice
Created symlink /etc/systemd/system/multi-user.target.wants/corosync-qdevice.service → /lib/systemd/system/corosync-qdevice.service.

With that, the service will be started again.

I'll provide a fix for this soon, after I finish the [main] Ubuntu HA packages first (that is why I moved this into "corosync-qdevice" and not "corosync" only).

Thank you.