Bug confirmed. It's an odd looking initscript, as it does not have the
usual actions in itself.
** Changed in: corosync (Ubuntu)
Status: New => Triaged
** Changed in: corosync (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1809682
Title:
"systemctl enable corosync-qdevice.service" fails
Status in corosync package in Ubuntu:
Triaged
Bug description:
"systemctl enable corosync-qdevice.service" fails:
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
update-rc.d: error: corosync-qdevice Default-Start contains no runlevels,
aborting.
Reason is that an init.d script as well as a systemd service definition
exists:
# dpkg -L corosync-qdevice
/lib/systemd/system/corosync-qdevice.service
/etc/init.d/corosync-qdevice
Therefore, using pcs to add a qdevice to the cluster fails:
pcs quorum device add model net host=qdevice-host algorithm=ffsplit
Log:
I, [2018-12-24T22:39:00.208158 #149] INFO -- : Running: systemctl enable
corosync-qdevice.service
I, [2018-12-24T22:39:00.208322 #149] INFO -- : CIB USER: hacluster, groups:
I, [2018-12-24T22:39:00.463878 #149] INFO -- : Return Value: 1
E, [2018-12-24T22:39:00.464110 #149] ERROR -- : Enabling corosync-qdevice
failed
Workaround is to manually remove the "/etc/init.d/corosync-qdevice"
script.
Solution is to remove the "/etc/init.d/corosync-qdevice" file from the
"corosync-qdevice" package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1809682/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
