Bug 2027006
| Summary: | pacemaker-2.1 fails to start without corosync-3.1.5 due to undefined symbol: corosync_cfg_trackstart | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Reid Wahl <nwahl> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.5 | CC: | cluster-maint, msmazova |
| Target Milestone: | rc | Keywords: | Regression, Triaged |
| Target Release: | 8.6 | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.1.2-1.el8 | Doc Type: | No Doc Update |
| Doc Text: |
This will be invisible to most users
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 14:09:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Reid Wahl
2021-11-26 20:45:39 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. 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 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 |