-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-8.4.0
-
None
-
Low
-
rhel-sst-logical-storage
-
ssg_filesystems_storage_and_HA
-
3
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
All
-
None
Description of problem:
dlm 4.1.0 requires the quorum_model_initialize function in corosync, which was introduced in corosync v3.1.0. dlm_controld fails to start if an older version of corosync is installed.
Aug 9 22:30:59 node1 pacemaker-execd[91995]: notice: dlm_start_0[92121] error output [ dlm_controld: symbol lookup error: dlm_controld: undefined symbol: quorum_model_initialize ]
Aug 9 22:30:59 node1 pacemaker-controld[91998]: notice: Result of start operation for dlm on node1: not running
See also:
- An ocf:pacemaker:controld resource fails to start with "symbol lookup error: dlm_controld: undefined symbol: quorum_model_initialize" in a Pacemaker cluster (https://access.redhat.com/solutions/6250411)
dlm 4.1.0 currently requires only corosync >= 1.99.9.
[root@fastvm-rhel-8-0-23 pacemaker]# rpm -q --requires dlm | grep corosync
corosync >= 1.99.9
Version-Release number of selected component (if applicable):
dlm-4.1.0-1.el8
How reproducible:
Always
Steps to Reproduce:
1. Install dlm-4.1.0-1.el8 and a corosync version less than 3.1.0.
2. Try to start dlm_controld (for example, via the ocf:pacemaker:controld resource agent).
Actual results:
dlm_controld: symbol lookup error: dlm_controld: undefined symbol: quorum_model_initialize
Expected results:
dlm_controld starts without issue.