Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 209862

Summary: commit token data doesn't look correct sometimes when running mp5
Product: Red Hat Enterprise Linux 5 Reporter: Steven Dake <sdake>
Component: openaisAssignee: Steven Dake <sdake>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5.1CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0599 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-07 17:00:00 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:
Attachments:
Description Flags
patch to fix the problem. none

Description Steven Dake 2006-10-07 02:12:37 UTC 
Description of problem:
this looks fishy from the logs:
Oct  6 19:38:35.056031 [TOTEM] entering RECOVERY state.
Oct  6 19:38:35.056083 [TOTEM] position [0] member 192.168.2.10:
Oct  6 19:38:35.056094 [TOTEM] previous ring seq 1125934283437147 rep 192.168.2.10
Oct  6 19:38:35.056102 [TOTEM] aru 28 high delivered 28 received flag 0
Oct  6 19:38:35.056111 [TOTEM] position [1] member 192.168.2.20:
Oct  6 19:38:35.056119 [TOTEM] previous ring seq 0 rep (null)
Oct  6 19:38:35.056126 [TOTEM] aru 0 high delivered 0 received flag 0
Oct  6 19:38:35.056134 [TOTEM] position [2] member 192.168.2.30:
Oct  6 19:38:35.056141 [TOTEM] previous ring seq 0 rep (null) Oct  6
19:38:35.056148 [TOTEM] aru 0 high delivered 0 received flag 0
Oct  6 19:38:35.056156 [TOTEM] position [3] member 192.168.2.31:
Oct  6 19:38:35.056163 [TOTEM] previous ring seq 0 rep (null)
Oct  6 19:38:35.056170 [TOTEM] aru 0 high delivered 0 received flag 0
Oct  6 19:38:35.056180 [TOTEM] Did not need to originate any messages in recovery.


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


How reproducible:


Steps to Reproduce:
1. run the mp5 test tool
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Steven Dake 2007-07-25 09:56:42 UTC 
The problem is that if a commit token is resent by a previous node, the next
node in the ring will also process the commit token again and send it on.  This
causes tokens for forward nodes to be discarded by incorrect logic and the
COMMIT token to be lost in a properly formed ring.  It also results in incorrect
EVS recovery which can result in segfaults of the protocol.
Comment 2 Steven Dake 2007-07-25 09:59:47 UTC 
Created attachment 159910 [details]
patch to fix the problem.
Comment 3 RHEL Program Management 2007-07-25 10:29:06 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 6 errata-xmlrpc 2007-11-07 17:00:00 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0599.html