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.
** Also affects: corosync-qdevice (Ubuntu Groovy)
Importance: Undecided
Status: Fix Released
** Also affects: corosync-qdevice (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: corosync-qdevice (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: corosync-qdevice (Ubuntu Groovy)
Status: Fix Released => Confirmed
** Changed in: corosync-qdevice (Ubuntu Focal)
Status: New => Confirmed
** Changed in: corosync-qdevice (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809682
Title:
"systemctl enable corosync-qdevice.service" fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
