pacemaker fails to start after upgrading to pacemaker-2.1.0-8.el8

Issue

• After upgrading pacemaker to pacemaker-2.1.0-8.el8, the pcs cluster start and systemctl start pacemaker commands leave the pacemaker service in failed state.

  # systemctl status pacemaker
  ● pacemaker.service - Pacemaker High Availability Cluster Manager
     Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Fri 2021-11-26 12:37:03 PST; 38s ago
       Docs: man:pacemakerd
             https://clusterlabs.org/pacemaker/doc/
    Process: 1233097 ExecStart=/usr/sbin/pacemakerd (code=exited, status=76)
   Main PID: 1233097 (code=exited, status=76)
  
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: pacemaker.service: Main process exited, code=exited, status=76/PROTOCOL
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: pacemaker.service: Failed with result 'exit-code'.
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: pacemaker.service: Service RestartSec=100ms expired, scheduling restart.
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: pacemaker.service: Scheduled restart job, restart counter is at 5.
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: Stopped Pacemaker High Availability Cluster Manager.
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: pacemaker.service: Start request repeated too quickly.
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: pacemaker.service: Failed with result 'exit-code'.
  Nov 26 12:37:03 fastvm-rhel-8-0-23 systemd[1]: Failed to start Pacemaker High Availability Cluster Manager.
  

• Starting the pacemakerd process in the foreground throws an "undefined symbol" error.

  # pacemakerd
  pacemakerd: symbol lookup error: pacemakerd: undefined symbol: corosync_cfg_trackstart, version COROSYNC_CFG_0.82