[Pacemaker] [PATCH]Bug 2567 - crm resource migrate should support an optional "role" parameter

[Andrew Beekhof]

On Mon, May 9, 2011 at 9:58 AM, Holger Teutsch <holger.teutsch at web.de> wrote:
> On Fri, 2011-05-06 at 16:15 +0200, Andrew Beekhof wrote:
>> On Fri, May 6, 2011 at 12:28 PM, Holger Teutsch <holger.teutsch at web.de> wrote:
>> > On Fri, 2011-05-06 at 11:03 +0200, Andrew Beekhof wrote:
>> >> On Fri, May 6, 2011 at 9:53 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>> >> > On Thu, May 5, 2011 at 5:43 PM, Holger Teutsch <holger.teutsch at web.de> wrote:
>> >> >> On Fri, 2011-04-29 at 09:41 +0200, Andrew Beekhof wrote:
>> >> >>> >>
>> >> >>> > Unfortunately the devel code does not run at all in my environment so I
>> >> >>> > have to fix this first.
>> >> >>>
>> >> >>> Oh?  I ran CTS on it the other day and it was fine here.
>> >> >>>
>> >> >>
>> >> >> I installed pacemaker-devel on top of a compilation of pacemaker-1.1. In
>> >> >> addition I tried "make uninstall" for both versions and then again
>> >> >> "make install" for devel. Pacemaker does not come up, crm_mon shows
>> >> >> nodes as offline.
>> >> >>
>> >> >> I suspect reason is
>> >> >> May  5 17:09:34 devel1 crmd: [5942]: notice: crmd_peer_update: Status update: Client devel1/crmd now has status [online] (DC=<null>)
>> >> >> May  5 17:09:34 devel1 crmd: [5942]: info: crm_update_peer: Node devel1: id=1790093504 state=unknown addr=(null) votes=0 born=0 seen=0 proc=00000000000000000000000000111312 (new)
>> >> >> May  5 17:09:34 devel1 crmd: [5942]: info: pcmk_quorum_notification: Membership 0: quorum retained (0)
>> >> >> May  5 17:09:34 devel1 crmd: [5942]: debug: do_fsa_action: actions:trace: #011// A_STARTED
>> >> >> May  5 17:09:34 devel1 crmd: [5942]: info: do_started: Delaying start, no membership data (0000000000100000)
>> >> >>                                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >> >> May  5 17:09:34 devel1 crmd: [5942]: debug: register_fsa_input_adv: Stalling the FSA pending further input: cause=C_FSA_INTERNAL
>> >> >>
>> >> >> Any ideas ?
>> >> >
>> >> > Hg version?  Corosync config?
>> >> > I'm running -devel here right now and things are fine.
>> >>
>> >> Uh, I think I see now.
>> >> Try http://hg.clusterlabs.org/pacemaker/1.1/rev/b94ce5673ce4
>> >>
>>
>> Yeah, I realized afterwards that it was specific to devel.
>> What does your corosync config look like?
> I run corosync-1.3.0-3.1.x86_64.
> It's exactly the same config that worked with
> pacemaker 1.1 rev 10608:b4f456380f60

If it works for that version, then it should work for any of the 7
commits since.
None of them could produce:

May  5 17:09:33 devel1 pacemakerd: [5929]: info: get_cluster_type:
Cluster type is: 'corosync'

Going back through the commit logs, it looks like the following is
when things broke:
   http://hg.clusterlabs.org/pacemaker/1.1/rev/44e5f4e760f6

Specifically this need to be removed:
+    setenv("HA_cluster_type",	"corosync",1);

Could you see if that change helps?