Keeping the installed LINBIT cluster stack intact

By using the Pacemaker 1.1.15 release, the LINBIT cluster stack has been cutting-edge. Now the distributions are catching up.

Our customers from time to time stumble upon the problem of mixing distribution- and LINBIT-based packages (eg. some RHEL6.x release brought a newer Pacemaker version, resulting in half-and-half-installed machine, breaking the cluster stack). Here’s a nice trick to avoid mixed cluster stack installations.

To avoid that, you’ll have to ensure that the LINBIT cluster stack is kept intact; for Debian based distributions we’ll simply use the apt package pinning mechanism. Create a file
/etc/apt/preferences.d/keep-linbit-packages.pref with this content:

Package: *
Pin: release o=LINBIT
Pin-Priority: 995

This basically means to prefer packages from the package Origin LINBIT.

It might occur to our dear readers that this preference should only be applied to installed packages; but that breaks as soon as a newer linbit-cluster-stack meta-package requires some new packages [1. Some libraries have a version number in the package name; for example, libcmap4. If a new cluster stack needs a libcmap5, then this wouldn’t get installed.], so we don’t do that.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *