Bug 696734

Summary: when existing ring file is zero bytes, corosync aborts
Product: Red Hat Enterprise Linux 6 Reporter: Benjamin Kahn <bkahn>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1CC: cluster-maint, djansa, fdinitto, jfriesse, jkortus, jwest, pm-eus, sdake, tcapek
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: corosync-1.2.3-21.el6_0.2 Doc Type: Bug Fix
Doc Text:
When a ring ID file was smaller than 8 bytes, the corosync server terminated unexpectedly. With this update, if no proper ring ID file can be loaded, the corosync server creates one and no crash will occur.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-08 08:15:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 675099    
Bug Blocks:    

Description Benjamin Kahn 2011-04-14 18:15:26 UTC
This bug has been copied from bug #675099 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 6 Tomas Capek 2011-05-23 15:13:36 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When a ring ID file was smaller than 8 bytes, the corosync server terminated unexpectedly. With this update, if no proper ring ID file can be loaded, the corosync server creates one and no crash will occur.

Comment 7 errata-xmlrpc 2011-06-08 08:15:02 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 therefore 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-2011-0854.html