[Cluster-devel] cluster.cman.nodename vanish on config reload

[Fabio M. Di Nitto <fdinitto@redhat.com>]

On 7/11/2012 10:21 AM, Dietmar Maurer wrote:
>>>> This lead directly to commit f3f4499d4ace7a3bf5fe09ce6d9f04ed6d8958f6
>>>>
>>>> But this is just the check you introduced. If I revert that patch,
>>>> everything works as before, but I noticed that It still deletes the
>>>> values from the corosync objdb after config reload - even in 3.1.8!
>>>>
>>>> Both cluster.cman.nodename and cluster.cman.cluster_id get removed.
>>>>
>>>> Testing with earlier versions now.
>>>
>>> That even happens with 3.1.4 (cant test easily with older versions).
>>>
>>> Any ideas?
>>
>> No, not yet, but what kind of operational problem do you get? does it affect
>> runtime? if so how?
> 
> I cannot change/reload the configuration  with commit f3f4499d4ace7a3bf5fe09ce6d9f04ed6d8958f6
> 
> When I revert that commit everything works fine.
> 
> I just wonder why those values get removed from the corosync objdb?

That?s the root cause of the issue.

> 
> Note: You added that check, so I guess it has negative side effects when there is no nodename (why did you add that check)?

Well yes, it is an error if we can?t determine our nodename.

The issue now is to understand why it fails for you but doesn?t fail for
me using git.

Fabio