Bug 681258

Summary: Memory leak when objdb reload config
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: agk, ccaulfie, cluster-maint, djansa, fdinitto, jfriesse, jkortus, lhh, mbroz, pm-eus, rpeterso, sdake, tcapek, teigland
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: corosync-1.2.3-21.el6_0.2 Doc Type: Bug Fix
Doc Text:
When inconsistent cluster.conf files with different versions were used among nodes, a memory leak occurred in the corosync server during the configuration reload. This bug has been fixed and the configuration reload via the cman_tool no longer causes memory leaks.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-08 08:14:50 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: 677975    
Bug Blocks:    

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

Comment 5 Tomas Capek 2011-05-23 15:15:33 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 inconsistent cluster.conf files with different versions were used among nodes, a memory leak occurred in the corosync server during the configuration reload. This bug has been fixed and the configuration reload via the cman_tool no longer causes memory leaks.

Comment 6 errata-xmlrpc 2011-06-08 08:14:50 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