RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2027006 - pacemaker-2.1 fails to start without corosync-3.1.5 due to undefined symbol: corosync_cfg_trackstart
Summary: pacemaker-2.1 fails to start without corosync-3.1.5 due to undefined symbol: ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.5
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: 8.6
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-26 20:45 UTC by Reid Wahl
Modified: 2024-12-20 21:39 UTC (History)
2 users (show)

Fixed In Version: pacemaker-2.1.2-1.el8
Doc Type: No Doc Update
Doc Text:
This will be invisible to most users
Clone Of:
Environment:
Last Closed: 2022-05-10 14:09:46 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104069 0 None None None 2021-11-26 20:47:43 UTC
Red Hat Knowledge Base (Solution) 6542881 0 None None None 2021-11-26 20:59:28 UTC
Red Hat Product Errata RHBA-2022:1885 0 None None None 2022-05-10 14:10:01 UTC

Description Reid Wahl 2021-11-26 20:45:39 UTC 
Description of problem:

If a user upgrades pacemaker to pacemaker-2.1 (RHEL 8.5 version) and does not upgrade corosync to corosync-3.1.5 (RHEL 8.5), then pacemaker fails to start due to an undefined symbol.

This BZ is a request to add a version-specific dependency on corosync to the pacemaker RPM, so that the updated corosync is pulled in automatically on an update, avoiding this scenario.

[root@fastvm-rhel-8-0-23 ~]# rpm -q corosync pacemaker
corosync-3.1.0-3.el8_4.1.x86_64
pacemaker-2.1.0-8.el8.x86_64
[root@fastvm-rhel-8-0-23 ~]# pacemakerd
pacemakerd: symbol lookup error: pacemakerd: undefined symbol: corosync_cfg_trackstart, version COROSYNC_CFG_0.82

[root@fastvm-rhel-8-0-23 ~]# rpm -q corosync pacemaker
corosync-3.1.5-1.el8.x86_64
pacemaker-2.1.0-8.el8.x86_64
[root@fastvm-rhel-8-0-23 ~]# pacemakerd
[no prompt]

-----

Version-Release number of selected component (if applicable):

pacemaker-2.1.0-8.el8
corosync less than corosync-3.1.5-1.el8

-----

How reproducible:

Always

-----

Steps to Reproduce:
1. Install corosync-3.1.0-3.el8_4.1 and pacemaker-2.1.0-8.el8.
2. Start corosync (systemctl start corosync).
3. Start pacemaker (`pacemakerd` -- for a more informative error).

-----

Actual results:

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

-----

Expected results:

# pacemakerd
[runs with no prompt]

**or**

# systemctl start pacemaker
# systemctl status pacemaker
● pacemaker.service - Pacemaker High Availability Cluster Manager
   Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2021-11-26 12:42:16 PST; 3s ago

-----

Additional info:
Comment 1 Ken Gaillot 2021-11-29 16:10:57 UTC 
Ah, right. The upstream code is protected by a conditional defined by the configure script, so upstream is OK. The RHEL 8.5+ build root has the newer corosync, so the configure script will enable the functionality for those builds, but as you describe, a user could upgrade pacemaker without upgrading corosync, and run into the issue.

We should be able to fix this for 8.6/9.0GA.
Comment 6 Markéta Smazová 2021-12-16 13:03:31 UTC 
before fix
-----------

>   [root@virt-043 ~]# rpm -q corosync pacemaker
>   corosync-3.1.0-3.el8.x86_64
>   pacemaker-2.1.0-8.el8.x86_64

>   [root@virt-138 ~]# systemctl start corosync && systemctl is-active corosync
>   active
>   [root@virt-138 ~]# systemctl start pacemaker
>   [root@virt-138 ~]# pacemakerd
>   pacemakerd: symbol lookup error: pacemakerd: undefined symbol: corosync_cfg_trackstart, version COROSYNC_CFG_0.82

>   [root@virt-138 ~]# systemctl status pacemaker
>   ● pacemaker.service - Pacemaker High Availability Cluster Manager
>      Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; enabled; vendor preset: disabled)
>      Active: failed (Result: exit-code) since Wed 2021-12-15 10:46:12 CET; 1min 11s ago
>        Docs: man:pacemakerd
>              https://clusterlabs.org/pacemaker/doc/
>     Process: 188972 ExecStart=/usr/sbin/pacemakerd (code=exited, status=127)
>    Main PID: 188972 (code=exited, status=127)

>   Dec 15 10:46:12 virt-138 systemd[1]: pacemaker.service: Main process exited, code=exited, status=127/n/a
>   Dec 15 10:46:12 virt-138 systemd[1]: pacemaker.service: Failed with result 'exit-code'.
>   Dec 15 10:46:12 virt-138 systemd[1]: pacemaker.service: Service RestartSec=100ms expired, scheduling restart.
>   Dec 15 10:46:12 virt-138 systemd[1]: pacemaker.service: Scheduled restart job, restart counter is at 5.
>   Dec 15 10:46:12 virt-138 systemd[1]: Stopped Pacemaker High Availability Cluster Manager.
>   Dec 15 10:46:12 virt-138 systemd[1]: pacemaker.service: Start request repeated too quickly.
>   Dec 15 10:46:12 virt-138 systemd[1]: pacemaker.service: Failed with result 'exit-code'.
>   Dec 15 10:46:12 virt-138 systemd[1]: Failed to start Pacemaker High Availability Cluster Manager.


after fix
----------

Check version of corosync and pacemaker:

>   [root@virt-138 ~]# rpm -q corosync pacemaker
>   corosync-3.1.0-3.el8.x86_64
>   pacemaker-2.1.0-8.el8.x86_64

Stop pacemaker and corosync:

>   [root@virt-138 ~]# systemctl stop pacemaker &&  systemctl stop corosync

Upgrade pacemaker:

>   [root@virt-138 ~]# yum upgrade /tmp/pacemaker{,-cli,-cluster-libs,-libs}-2.1.2-1.el8.x86_64.rpm /tmp/pacemaker-schemas-2.1.2-1.el8.noarch.rpm
>   Updating Subscription Management repositories.
>   Unable to read consumer identity

>   This system is not registered with an entitlement server. You can use subscription-manager to register.

>   Last metadata expiration check: 3:07:08 ago on Wed 15 Dec 2021 10:41:05 CET.
>   Dependencies resolved.
>   ========================================================================================================================
>    Package                           Architecture      Version                   Repository                          Size
>   ========================================================================================================================
>   Upgrading:
>    corosync                          x86_64            3.1.5-1.el8               beaker-HighAvailability            278 k
>    corosynclib                       x86_64            3.1.5-1.el8               beaker-AppStream                    69 k
>    pacemaker                         x86_64            2.1.2-1.el8               @commandline                       460 k
>    pacemaker-cli                     x86_64            2.1.2-1.el8               @commandline                       329 k
>    pacemaker-cluster-libs            x86_64            2.1.2-1.el8               @commandline                       137 k
>    pacemaker-libs                    x86_64            2.1.2-1.el8               @commandline                       733 k
>    pacemaker-schemas                 noarch            2.1.2-1.el8               @commandline                        84 k

>   Transaction Summary
>   ========================================================================================================================
>   Upgrade  7 Packages

>   Total size: 2.0 M
>   Total download size: 347 k
>   Is this ok [y/N]:y


>   [...]

>   Installed products updated.

>   Upgraded:
>     corosync-3.1.5-1.el8.x86_64            corosynclib-3.1.5-1.el8.x86_64              pacemaker-2.1.2-1.el8.x86_64
>     pacemaker-cli-2.1.2-1.el8.x86_64       pacemaker-cluster-libs-2.1.2-1.el8.x86_64   pacemaker-libs-2.1.2-1.el8.x86_64
>     pacemaker-schemas-2.1.2-1.el8.noarch

>   Complete!


When upgrading pacemaker a newer version of corosync is pulled as a dependency 


Check version of corosync and pacemaker:

>   [root@virt-138 ~]# rpm -q corosync pacemaker
>   corosync-3.1.5-1.el8.x86_64
>   pacemaker-2.1.2-1.el8.x86_64


Start corosync and pacemaker:

>   [root@virt-138 ~]# systemctl start corosync && systemctl is-active corosync
>   active
>   [root@virt-138 ~]# systemctl start pacemaker && systemctl is-active pacemaker
>   active

Check pacemaker status:

>   [root@virt-138 ~]# systemctl status pacemaker
>   ● pacemaker.service - Pacemaker High Availability Cluster Manager
>      Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; enabled; vendor preset: disabled)
>      Active: active (running) since Wed 2021-12-15 14:50:01 CET; 1min 48s ago
>        Docs: man:pacemakerd
>              https://clusterlabs.org/pacemaker/doc/
>    Main PID: 4229 (pacemakerd)
>       Tasks: 7
>      Memory: 32.8M
>      CGroup: /system.slice/pacemaker.service
>              ├─4229 /usr/sbin/pacemakerd
>              ├─4231 /usr/libexec/pacemaker/pacemaker-based
>              ├─4232 /usr/libexec/pacemaker/pacemaker-fenced
>              ├─4233 /usr/libexec/pacemaker/pacemaker-execd
>              ├─4234 /usr/libexec/pacemaker/pacemaker-attrd
>              ├─4235 /usr/libexec/pacemaker/pacemaker-schedulerd
>              └─4236 /usr/libexec/pacemaker/pacemaker-controld

>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  warning: watchdog-fencing-query failed
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: State transition S_PENDING -> S_NOT_DC
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Requesting local execution of probe operation for fence-virt-138 on virt-138
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Requesting local execution of probe operation for fence-virt-139 on virt-138
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Result of probe operation for fence-virt-138 on virt-138: not running (No such device)
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Result of probe operation for fence-virt-139 on virt-138: not running (No such device)
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Requesting local execution of start operation for fence-virt-138 on virt-138
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Result of start operation for fence-virt-138 on virt-138: ok
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Requesting local execution of monitor operation for fence-virt-138 on virt-138
>   Dec 15 14:50:24 virt-138 pacemaker-controld[4236]:  notice: Result of monitor operation for fence-virt-138 on virt-138: ok

Check cluster status:

>   [root@virt-138 ~]# pcs status
>   Cluster name: STSRHTS23335
>   Cluster Summary:
>     * Stack: corosync
>     * Current DC: virt-139 (version 2.1.2-1.el8-ada5c3b36e2) - partition with quorum
>     * Last updated: Wed Dec 15 14:52:25 2021
>     * Last change:  Wed Dec 15 14:50:24 2021 by hacluster via crmd on virt-139
>     * 2 nodes configured
>     * 2 resource instances configured

>   Node List:
>     * Online: [ virt-138 virt-139 ]

>   Full List of Resources:
>     * fence-virt-138      (stonith:fence_xvm):     Started virt-138
>     * fence-virt-139      (stonith:fence_xvm):     Started virt-139

>   Daemon Status:
>     corosync: active/enabled
>     pacemaker: active/enabled
>     pcsd: active/enabled


Marking verified in pacemaker-2.1.2-1.el8
Comment 8 errata-xmlrpc 2022-05-10 14:09:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (pacemaker bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1885
Note You need to log in before you can comment on or make changes to this bug.