On 7/11/2012 9:37 AM, Dietmar Maurer wrote: >> Ok, bisect myself. >> >> 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? Fabio
