Corosync regularly reports "nsscrypto: Digest does not match" error

Issue

Corosync reports nsscrypto: Digest does not match error:

$ cat /var/log/messages
----------------------------------->8----------------------------------
May 22 12:43:22 rhel8-node1 corosync[8017]:  [KNET  ] nsscrypto: Digest does not match <---
May 22 12:43:23 rhel8-node1 corosync[8017]:  [KNET  ] nsscrypto: Digest does not match
May 22 12:43:23 rhel8-node1 corosync[8017]:  [KNET  ] nsscrypto: Digest does not match
May 22 12:43:23 rhel8-node1 pacemaker-attrd[8033]: notice: Connecting to corosync cluster infrastructure
May 22 12:43:23 rhel8-node1 pacemaker-controld[8035]: notice: Connecting to corosync cluster infrastructure
May 22 12:43:23 rhel8-node1 pacemaker-attrd[8033]: notice: Node rhel8-node1priv state is now member
May 22 12:43:23 rhel8-node1 pacemaker-fenced[8031]: notice: Pacemaker fencer successfully started and accepting connections
May 22 12:43:23 rhel8-node1 pacemaker-attrd[8033]: notice: Pacemaker node attribute manager successfully started and accepting connections
May 22 12:43:23 rhel8-node1 pacemaker-attrd[8033]: notice: Setting #attrd-protocol[rhel8-node1priv]: (unset) -> 3
May 22 12:43:23 rhel8-node1 pacemaker-attrd[8033]: notice: Recorded local node as attribute writer (was unset)
May 22 12:43:23 rhel8-node1 pacemaker-controld[8035]: warning: No quorum
May 22 12:43:23 rhel8-node1 pacemaker-controld[8035]: notice: Node rhel8-node1priv state is now member
May 22 12:43:23 rhel8-node1 pacemaker-controld[8035]: notice: Pacemaker controller successfully started and accepting connections
May 22 12:43:23 rhel8-node1 pacemaker-controld[8035]: notice: State transition S_STARTING -> S_PENDING
May 22 12:43:23 rhel8-node1 corosync[8017]:  [KNET  ] nsscrypto: Digest does not match
May 22 12:43:24 rhel8-node1 corosync[8017]:  [KNET  ] nsscrypto: Digest does not match
May 22 12:43:24 rhel8-node1 corosync[8017]:  [KNET  ] rx: host: 2 link: 0 is up
May 22 12:43:24 rhel8-node1 corosync[8017]:  [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
May 22 12:43:24 rhel8-node1 corosync[8017]:  [KNET  ] nsscrypto: Digest does not match
May 22 12:43:24 rhel8-node1 corosync[8017]:  [KNET  ] pmtud: PMTUD link change for host: 2 link: 0 from 469 to 1397
May 22 12:43:24 rhel8-node1 corosync[8017]:  [KNET  ] pmtud: Global data MTU changed to: 1397
May 22 12:43:24 rhel8-node1 corosync[8017]:  [QUORUM] Sync members[2]: 1 2
May 22 12:43:24 rhel8-node1 corosync[8017]:  [QUORUM] Sync joined[1]: 2
May 22 12:43:24 rhel8-node1 corosync[8017]:  [TOTEM ] A new membership (1.9) was formed. Members joined: 2
May 22 12:43:24 rhel8-node1 pacemaker-fenced[8031]: notice: Node rhel8-node2 state is now member
May 22 12:43:24 rhel8-node1 pacemaker-attrd[8033]: notice: Node rhel8-node2 state is now member
May 22 12:43:24 rhel8-node1 pacemaker-based[8030]: notice: Node rhel8-node2 state is now member

This issue does not affect node membership or connectivity.