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 1067043 - CPG membership may be inconsistent after node pause
Summary: CPG membership may be inconsistent after node pause
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync
Version: 6.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 1055584
Blocks: 1080102 1080103
TreeView+ depends on / blocked
 
Reported: 2014-02-19 14:47 UTC by Jan Friesse
Modified: 2014-10-14 07:11 UTC (History)
4 users (show)

Fixed In Version: corosync-1.4.1-18.el6
Doc Type: Bug Fix
Doc Text:
Cause: Corosync on one of node is paused. On other nodes, cpg clients are killed. Consequence: Corosync on paused node after resume never finds out that on other nodes cpg clients were killed and still believes they are alive. Membership (cpg one) is different between nodes. Fix: Make sure that corosync properly updates it's internal informations about other nodes cpg clients. Result: Killed cpg clients are properly removed from internal structures so cpg membership is equivalent between nodes.
Clone Of: 1067028
Environment:
Last Closed: 2014-10-14 07:11:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch - part 1 - cpg: Refactor mh_req_exec_cpg_procleave (3.02 KB, patch)
2014-02-19 15:01 UTC, Jan Friesse 		no flags Details | Diff
Proposed patch - part 2 - cpg: Make sure nodid is always logged as hex num (2.10 KB, patch)
2014-02-19 15:02 UTC, Jan Friesse 		no flags Details | Diff
Proposed patch - part3 - cpg: Make sure left nodes are really removed (2.43 KB, patch)
2014-02-19 15:15 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1508 0 normal SHIPPED_LIVE corosync bug fix update 2014-10-14 01:22:31 UTC

Comment 1 Jan Friesse 2014-02-19 15:01:27 UTC 
Created attachment 865103 [details]
Proposed patch - part 1 - cpg: Refactor mh_req_exec_cpg_procleave
Comment 2 Jan Friesse 2014-02-19 15:02:00 UTC 
Created attachment 865104 [details]
Proposed patch - part 2 - cpg: Make sure nodid is always logged as hex num
Comment 3 Jan Friesse 2014-02-19 15:15:50 UTC 
Created attachment 865112 [details]
Proposed patch - part3 - cpg: Make sure left nodes are really removed
Comment 9 errata-xmlrpc 2014-10-14 07:11:53 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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2014-1508.html
Note You need to log in before you can comment on or make changes to this bug.