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 855959 - Unable to remove nodes from corosync running config without segfault
Summary: Unable to remove nodes from corosync running config without segfault
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libqb
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Angus Salkeld
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-10 18:37 UTC by Chris Feist
Modified: 2012-09-17 06:12 UTC (History)
1 user (show)

Fixed In Version: libqb-0.14.2-2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-17 06:12:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris Feist 2012-09-10 18:37:36 UTC 
When attempting to remove nodes from a running corosync cluster I get a segfault.  Below are the commands/output that I'm running.  (cluster is udpu)

[root@rh7-1 ~]# rpm -q corosync
corosync-2.0.1-3.el7.x86_64

I've got a 3 node cluster running pacemaker/corosync.  I shutdown pacemaker and corosync on the 3rd node (rh7-3) and try to remove it on another node from the running corosync and I end up getting a segfault.  Here are the commands I'm running.

Before rh7-3 shutdown:
[root@rh7-1 ~]# corosync-quorumtool -l

Membership information
----------------------
    Nodeid      Votes Name
         3          1 rh7-3
         2          1 rh7-2
         1          1 rh7-1

After shutdown:
[root@rh7-1 ~]# corosync-quorumtool -l

Membership information
----------------------
    Nodeid      Votes Name
         2          1 rh7-2
         1          1 rh7-1

[root@rh7-1 ~]# corosync-cmapctl  | grep nodelist
nodelist.local_node_pos (u32) = 0
nodelist.node.0.nodeid (u32) = 1
nodelist.node.0.ring0_addr (str) = rh7-1
nodelist.node.1.nodeid (u32) = 2
nodelist.node.1.ring0_addr (str) = rh7-2
nodelist.node.2.nodeid (u32) = 3
nodelist.node.2.ring0_addr (str) = rh7-3

[root@rh7-1 ~]# corosync-cmapctl -d nodelist.node.2.ring0_addr nodelist.node.2.nodeid
Can't delete key nodelist.node.2.ring0_addr. Error CS_ERR_LIBRARY
Can't delete key nodelist.node.2.nodeid. Error CS_ERR_LIBRARY

Then corosync segfaults.  I get these messages in /var/log/messages:

Sep 10 12:00:55 rh7-1 corosync[18699]:  [TOTEM ] removing UDPU member {192.168.122.116}
Sep 10 12:00:56 rh7-1 abrt[22147]: Saved core dump of pid 18699 (/usr/sbin/corosync) to /var/spool/abrt/ccpp-2012-09-10-12:00:56-18699 (33681408 bytes)
Sep 10 12:00:57 rh7-1 systemd[1]: corosync.service: main process exited, code=dumped, status=11
Comment 1 Jan Friesse 2012-09-17 06:12:03 UTC 
This was problem with libqb, which should be fixed in upstream and libqb-0.14.2-2.el7.
Note You need to log in before you can comment on or make changes to this bug.