Hi, Gianluca I modified my configuration and deleted "crm configure property no-quorum-policy=ignore" as you suggested but I have the same problem that the IP address does not fail. Thanks.
[r...@usnbrl52 log]# crm configure show node usnbrl52 node usnbrl53 primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="156.146.22.48" cidr_netmask="32" \ op monitor interval="30s" property $id="cib-bootstrap-options" \ dc-version="1.0.8-fab8db4bbd271ba0a630578ec23776dfbaa4e2cf" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" rsc_defaults $id="rsc-options" \ resource-stickiness="default" [r...@usnbrl52 log]# [r...@usnbrl52 log]# crm status ============ Last updated: Mon May 17 17:33:55 2010 Stack: openais Current DC: usnbrl53 - partition with quorum Version: 1.0.8-fab8db4bbd271ba0a630578ec23776dfbaa4e2cf 2 Nodes configured, 2 expected votes 1 Resources configured. ============ Online: [ usnbrl52 usnbrl53 ] ClusterIP (ocf::heartbeat:IPaddr2): Started usnbrl52 [r...@usnbrl52 log]# [r...@usnbrl53 log]# crm status ============ Last updated: Mon May 17 17:36:36 2010 Stack: openais Current DC: usnbrl53 - partition WITHOUT quorum Version: 1.0.8-fab8db4bbd271ba0a630578ec23776dfbaa4e2cf 2 Nodes configured, 2 expected votes 1 Resources configured. ============ Online: [ usnbrl53 ] OFFLINE: [ usnbrl52 ] Ryan ________________________________ From: Gianluca Cecchi [mailto:gianluca.cec...@gmail.com] Sent: Saturday, May 15, 2010 3:20 AM To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] IP address does not failover on a new test cluster On Fri, May 14, 2010 at 11:40 PM, Ruiyuan Jiang <ruiyuan_ji...@liz.com<mailto:ruiyuan_ji...@liz.com>> wrote: Hi, I just created a testing cluster (Corosync 1.2.1, OpenAIS 1.1.2 and Pacemaker 1.0.8) on RHEL 5.5, x86_64. When I shutdown the primary node, the secondary node does not bind the cluster IP address which it supposed to. Why? Thanks. [snip] no-quorum-ignore="no" rsc_defaults $id="rsc-options" \ resource-stickiness="default" [r...@usnbrl53 sbin]# In a two nodes cluster you have set quorum policy to no: crm configure property no-quorum-policy=ignore You should see in you surviving node log messages regarding the fact that it has no quorum to provide service as it is configured now... This message (including any attachments) is intended solely for the specific individual(s) or entity(ies) named above, and may contain legally privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, by other than the intended recipient, is strictly prohibited.
_______________________________________________ Pacemaker mailing list: Pacemaker@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