[Pacemaker] remote node not listed

[Andrew Beekhof]

On 12 Sep 2014, at 7:11 pm, Саша Александров <shurrman at gmail.com> wrote:

> Emmanuel,
> 
> telnet to daemon is ok.
> 
> I just found an answer in RH documentation ( https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/pacemaker_remote.html )
> It clearly states: WARNING: This value cannot overlap with any resource or node IDs.
> The clusterlabs guide does not...

Its in the sources, the online version probably needs refreshing.

> This fixed the issue with node not being listed.
> 
> However, I ran into the second problem: start timeout for VM is not honoured:
> 
> # pcs resource show vm-oracle-test
>  Resource: vm-oracle-test (class=ocf provider=heartbeat type=VirtualDomain)
>   Attributes: hypervisor=qemu:///system config=/etc/libvirt/qemu/oracle-test.xml
>   Meta Attrs: remote-node=oracle-test
>   Operations: monitor interval=60s (vm-oracle-test-monitor-interval-60s)
>               start on-fail=restart interval=0s timeout=300s (vm-oracle-test-start-timeout-300s-interval-0s-on-fail-restart)
>               stop on-fail=block interval=0s timeout=60s (vm-oracle-test-stop-timeout-60s-interval-0s-on-fail-block)
> 
> however
> 
> 
> Sep 12 13:08:15 wings1 crmd[13553]:   notice: process_lrm_event: LRM operation vm-oracle-test_start_0 (call=106, rc=0, cib-update=62, confirmed=true) ok
> Sep 12 13:08:15 wings1 crmd[13553]:   notice: process_lrm_event: LRM operation vm-oracle-test_monitor_60000 (call=110, rc=0, cib-update=64, confirmed=false) ok
> Sep 12 13:09:13 wings1 crmd[13553]:    error: process_lrm_event: LRM operation oracle-test_start_0 (14) Timed Out (timeout=60000ms)
> Sep 12 13:09:13 wings1 attrd[27950]:   notice: attrd_cs_dispatch: Update relayed from wings2
> Sep 12 13:09:13 wings1 attrd[27950]:   notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-oracle-test (INFINITY)
> 
> Best regards,
> Alexandr A. Alexandrov
> 
> 2014-09-12 12:47 GMT+04:00 emmanuel segura <emi2fast at gmail.com>:
> telnet oracle-test 3121 ?
> 
> 2014-09-12 9:55 GMT+02:00 Саша Александров <shurrman at gmail.com>:
> > Hi!
> >
> > I am trying to set up a cluster on two servers with several KVM virtual
> > machines. (CentOS 6.5, Pacemaker 1.10 from native repo)
> > Using this as guideline:
> > http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm207095595072
> > It states:
> >
> > Now just register the resource with pacemaker and you’re set!
> >
> > # pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system"
> > config="/root/guest1.xml" meta remote-node=guest1
> >
> > Once the vm-guest1 resource is started you will see guest1 appear in the pcs
> > status output as a node. The final pcs statusoutput should look something
> > like this.
> >
> > Last updated: Fri Mar 15 09:30:30 2013
> > Last change: Thu Mar 14 17:21:35 2013 via cibadmin on example-host
> > Stack: corosync
> > Current DC: example-host (1795270848) - partition WITHOUT quorum
> > Version: 1.1.10
> > 2 Nodes configured, unknown expected votes
> > 2 Resources configured.
> >
> >
> > Online: [ example-host guest1 ]
> >
> > Full list of resources:
> >
> >  vm-guest1      (ocf::heartbeat:VirtualDomain): Started example-host
> >
> >
> > However, remote-node does not appear in a node list, just a resource:
> >
> > # pcs resource create oracle-test VirtualDomain hypervisor="qemu:///system"
> > config="/etc/libvirt/qemu/oracle-test.xml" meta remote-node=oracle-test
> >
> > # pcs status
> > Cluster name: wings
> > Last updated: Fri Sep 12 11:45:50 2014
> > Last change: Fri Sep 12 11:35:50 2014 via crm_resource on wings1
> > Stack: cman
> > Current DC: wings1 - partition with quorum
> > Version: 1.1.10-14.el6-368c726
> > 2 Nodes configured
> > 1 Resources configured
> >
> >
> > Online: [ wings1 wings2 ]
> >
> > Full list of resources:
> >
> >  oracle-test    (ocf::heartbeat:VirtualDomain): Started wings1
> >
> > It is supposed that remote-node named oracle-test should appear in the list
> > as the third node, is not it?
> > Please advice
> >
> >
> > --
> > Best regards,
> > Alexandr A. Alexandrov
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> >
> 
> 
> 
> --
> esta es mi vida e me la vivo hasta que dios quiera
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 
> 
> 
> -- 
> С уважением, ААА.
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140917/588b594e/attachment-0003.sig>