Hi All,
We identified order of the master/slave resource as primitive resource.
We set order limitation as follows.
However, promote was carried out even if primitvei resource caused start
trouble.
============
Last updated: Fri Jun 29 19:20:09 2012
Stack: Heartbeat
Current DC: rh62-test1 (c9aea7b3-4fe9-4766-9b09-b1f3ab2c329d) - partition with
quorum
Version: 1.0.12-unknown
1 Nodes configured, unknown expected votes
2 Resources configured.
============
Online: [ rh62-test1 ]
Master/Slave Set: msPostgresql
Masters: [ rh62-test1 ]
Stopped: [ postgresql:1 ]
Migration summary:
* Node rh62-test1:
vipCheck: migration-threshold=1 fail-count=1000000
Failed actions:
vipCheck_start_0 (node=rh62-test1, call=4, rc=1, status=complete): unknown
error
Is there setting to let you carry out order of start and promote definitely?
Or is this a bug?
The same phenomenon seems to occur in Pacemaker 1.1.7.
I registered these contents with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5075
Best Regards,
Hideo Yamauchi.
_______________________________________________
Pacemaker mailing list: [email protected]
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
