All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster.cman.nodename vanish on config reload
Date: Wed, 11 Jul 2012 10:14:31 +0200	[thread overview]
Message-ID: <4FFD35E7.7070207@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75574F94D2@lisa.maurer-it.com>

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



  reply	other threads:[~2012-07-11  8:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 11:33 [Cluster-devel] cluster.cman.nodename vanish on config reload Dietmar Maurer
2012-07-10 11:43 ` Fabio M. Di Nitto
2012-07-10 12:09   ` Dietmar Maurer
2012-07-10 12:26     ` Fabio M. Di Nitto
2012-07-11  7:36       ` Dietmar Maurer
2012-07-11  7:37       ` Dietmar Maurer
2012-07-11  8:14         ` Fabio M. Di Nitto [this message]
2012-07-11  8:20           ` Fabio M. Di Nitto
2012-07-11  8:21           ` Dietmar Maurer
2012-07-11  8:27             ` Fabio M. Di Nitto
2012-07-11  8:32               ` Dietmar Maurer
2012-07-11  8:35                 ` Fabio M. Di Nitto
2012-07-11  9:48                 ` Fabio M. Di Nitto
2012-07-11 10:11                   ` Dietmar Maurer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FFD35E7.7070207@redhat.com \
    --to=fdinitto@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.