[ClusterLabs] pcs create master/slave resource doesn't work
jpokorny at redhat.com
Mon Nov 27 15:19:12 EST 2017
On 27/11/17 12:07 -0600, Ken Gaillot wrote:
> On Fri, 2017-11-24 at 18:00 +0800, Hui Xiang wrote:
>> Very appreciated on your help, I am getting further more, but still
>> it looks very strange.
>> 1. To use "debug-promote", I upgrade pacemaker from 1.12 to 1.16, pcs
>> to 0.9.160.
>> 2. Recreate resource with below commands
>> pcs resource create ovndb_servers ocf:ovn:ovndb-servers \
>> master_ip=192.168.0.99 \
>> op monitor interval="10s" \
>> op monitor interval="11s" role=Master
>> pcs resource master ovndb_servers-master ovndb_servers \
>> meta notify="true" master-max="1" master-node-max="1" clone-max="3"
>> pcs resource create VirtualIP ocf:heartbeat:IPaddr2 ip=192.168.0.99 \
>> op monitor interval=10s
>> pcs constraint colocation add VirtualIP with master ovndb_servers-
>> master \
>> 3. pcs status
>> Master/Slave Set: ovndb_servers-master [ovndb_servers]
>> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld
>> VirtualIP (ocf::heartbeat:IPaddr2): Stopped
>> 4. Manually run 'debug-start' on 3 nodes and 'debug-promote' on one
>> of nodes
>> run below on [ node-1.domain.tld node-2.domain.tld node-3.domain.tld
>> # pcs resource debug-start ovndb_servers --full
>> run below on [ node-1.domain.tld ]
>> # pcs resource debug-promote ovndb_servers --full
> Before running debug-* commands, I'd unmanage the resource or put the
> cluster in maintenance mode, so Pacemaker doesn't try to "correct" your
Agree for that being a rule of thumb for avoiding surprises, though in
this particular case, it did not appear there's anything to correct.
Would it then make sense for the pcs (high-level tool) to check the
circumstances, especially concurrent run of the resource, prior to
delegating the command down the line?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the Users