Bug 839241 - cman config reload can leak memory and does not propagate all info correctly
cman config reload can leak memory and does not propagate all info correctly
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Fabio Massimo Di Nitto
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2012-07-11 06:50 EDT by Fabio Massimo Di Nitto
Modified: 2013-02-21 02:42 EST (History)
6 users (show)

See Also:
Fixed In Version: cluster-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 02:42:41 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fabio Massimo Di Nitto 2012-07-11 06:50:29 EDT
3 values that are generated at startup time (cluster_id, two_node, nodename) are not correctly re-instated in the objdb on config reload.

start cluster
corosync-objctl |grep cman


increase version in cluster.conf, reload

the same command will show no output.

In the reload path, via code review, there is also a corner case where we can leak a tiny amount of memory if config reload fails. This is not easy to trigger or test. devel review required for the fix.

After patching, corosync-objctl will show the items as expected.
Comment 1 Fabio Massimo Di Nitto 2012-07-11 06:51:29 EDT

unit test in comment #1. Patch tested also by community (see cluster-devel).
Comment 8 errata-xmlrpc 2013-02-21 02:42:41 EST
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.


Note You need to log in before you can comment on or make changes to this bug.