3 values that are generated at startup time (cluster_id, two_node, nodename) are not correctly re-instated in the objdb on config reload.
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.
unit test in comment #1. Patch tested also by community (see cluster-devel).
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.