Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 610334

Summary: isolating a node for 11-29 seconds results in bad cpg membership 15% of time
Product: Red Hat Enterprise Linux 6 Reporter: Steven Dake <sdake>
Component: corosyncAssignee: Angus Salkeld <asalkeld>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0CC: cluster-maint, nstraz, sdake, syeghiay, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 605313 Environment:
Last Closed: 2010-07-06 08:04:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 583844    
Bug Blocks: 599016    

Comment 1 Steven Dake 2010-07-02 06:00:50 UTC 
When isolating a node via iptables for a period of between 11-29 seconds and then removing the isolation the node, cpg membership is invalid.

This simulates a network interface going offline for between 11-29 seconds, and then becoming active again.

token = 10 sec
consensus = 20 sec
between token and consensus timeout period, an isolation followed by removal of isolation demonstrates this issue.
Comment 2 Angus Salkeld 2010-07-02 11:17:38 UTC 
I have used (modified) laryngitis with a sleep between the isolate and the unisolate to test both the current rhel6 corosync package and one with my cpg membership patches (Bug 583844). Both always fail on which ever node it chooses.

Jul  2 21:00:47 r3 qarshd[3448]: Running cmdline: /tmp/coro-netctl drop
...
Jul  2 21:01:02 r3 qarshd[3469]: Running cmdline: /tmp/coro-netctl accept
(note the time gap == 15sec)

this is using a script to do the isolating that uses iptables-restore
to make the 2 iptables commands more atomic (this improves the normal
case).

This seems to be as cpg doesn't handle the particular membership info that gets
passed to it very well.
Comment 3 Angus Salkeld 2010-07-05 23:05:31 UTC 
After putting in some debug (below), it looks like the cpg membership is
ok. In this situation there is no change in the membership (no join/leaves).

I think the bug is a non-issue.

What do you think Steve?

Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_memb) 192.168.100.91
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_memb) 192.168.100.92
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_memb) 192.168.100.93
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_new_memb) 192.168.100.91
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_new_memb) 192.168.100.92
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_new_memb) 192.168.100.93
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_trans_memb) 192.168.100.91
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_trans_memb) 192.168.100.92
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] my_trans_memb) 192.168.100.93
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] left_list (empty)
Jul  6 08:21:10 r2 corosync[2882]:   [TOTEM ] join_list (empty)
Jul  6 08:21:10 r2 corosync[2882]:   [CPG   ] cpg_confchg:members [13888] 1 2 3 
Jul  6 08:21:10 r2 corosync[2882]:   [CPG   ] cpg_confchg:left    [13888] <empty>
Jul  6 08:21:10 r2 corosync[2882]:   [CPG   ] cpg_confchg:joined  [13888] <empty>
Comment 4 Angus Salkeld 2010-07-06 08:04:34 UTC 
There was initially a bug in my diagnostic code that caused Steve to
make this bug. Not a bug.