Hum, looks like systemd used your sysv scripts (perhaps because of upgrades) and it had issues because they had no runlevels by default... and your workaround was to use the systemd unit, which is the one used by default...
### BEGIN INIT INFO
# Provides: corosync-qdevice
# Required-Start: $remote_fs $syslog corosync
# Required-Stop: $remote_fs $syslog corosync
# Default-Start:
# Default-Stop: 0 1 6
# Short-Description: Corosync Qdevice daemon
# Description: Starts and stops Corosync Qdevice daemon.
### END INIT INFO
and indeed the sysv scripts don't have default start runlevels.
Hum, looks like systemd used your sysv scripts (perhaps because of upgrades) and it had issues because they had no runlevels by default... and your workaround was to use the systemd unit, which is the one used by default...
### BEGIN INIT INFO
# Provides: corosync-qdevice
# Required-Start: $remote_fs $syslog corosync
# Required-Stop: $remote_fs $syslog corosync
# Default-Start:
# Default-Stop: 0 1 6
# Short-Description: Corosync Qdevice daemon
# Description: Starts and stops Corosync Qdevice daemon.
### END INIT INFO
and indeed the sysv scripts don't have default start runlevels.
I should fix this.