pacemaker init script links aren't created on upgrade

[Patrick Domack]

When upgrading my pacemaker/corosync machines from ubuntu 12.04 to 14.04, update-rc.d for pacemaker is not run, so the new pacemaker init.d script is never executed on system startup, causing corosync/pacemaker HA system to not start.

When adding the new pacemaker init.d script, update-rc.d should be run, so pacemaker init.d is run to start pacemaker as needed.

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I guess that update-rc.d can be run by hand as a workaround? In this case, setting Importance: Medium as a workaround is available.

[Jakob Lundberg (jakob-lundberg)]

I have a problem with using the update-rc.d to generate the rc*.d links. Even though pacemaker gets sequence number 20 and corosync number 19. It appears that corosync is not fully started when pacemaker gets started.

The result is that pacemaker starts up without a connection to the peer. And resources such as DRBD gets in a split brain state.

When removing the rc*.d links for pacemaker and starting pacemaker manually there is no problem. So apperantly it is not enough to wait for the corosync init script to launch. corosync needs to get properly connected before it is safe to start pacemaker.

On earlier verisions this was not a problem as the corosync plugin started pacemaker when corosync was ready.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jakob Lundberg (jakob-lundberg)]

After some more checking I found that my issue was not with the startup order but the shutdown order.

At install of corosync, the shutdown is linked with K01corosync. Using update-rc.d pacemaker defaults will create the shutdown link K20pacemaker.

This causes corosync to be shutdown before pacemaker is.

[James Page (james-page)]

See related bug 1727063