Pacemaker fails to start after an interrupted yum update

Issue

• A node was fenced or yum was otherwise prematurely interrupted during a yum update command. Subsequently, pacemaker fails to start with errors such as the following:

  Feb  5 20:34:28 node1 systemd: pacemaker.service: main process exited, code=exited, status=127/n/a
  Feb  5 20:34:28 node1 systemd: Unit pacemaker.service entered failed state.
  Feb  5 20:34:28 node1 systemd: pacemaker.service failed.
  Feb  5 20:34:28 node1 systemd: pacemaker.service holdoff time over, scheduling restart.
  Feb  5 20:34:28 node1 systemd: start request repeated too quickly for pacemaker.service
  Feb  5 20:34:28 node1 systemd: Failed to start Pacemaker High Availability Cluster Manager.
  Feb  5 20:34:28 node1 systemd: Unit pacemaker.service entered failed state.
  Feb  5 20:34:28 node1 systemd: pacemaker.service failed.
  

• Starting pacemakerd in the foreground results in a missing library error.

  # /usr/sbin/pacemakerd -f
  /usr/sbin/pacemakerd: error while loading shared libraries: libcrmservice.so.3: cannot open shared object file: No such file or directory