<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>I can agree, Master monitor operation is broken in 1.1.10 release.</div>
<div>When the slave monitor action is started, the master monitor action is not called any more.</div>
<div> </div>
<div>I have created a setup with Stateful resource with two nodes.</div>
<div>Then the Pacemaker installation is changed to different versions without changing the configuration part of the CIB.</div>
<div>
<div> </div>
<div>Result:</div>
<div>1.1.10-rc5, 1.1.10-rc6 and 1.1.10-rc7 does not have this error</div>
<div>1.1.10-1 release has the error</div>
<div> </div>
<div>Installation order (just that anybody know how it was done):</div>
<div>1.1.10-1 -> error</div>
<div>1.1.10-rc5 -> no error</div>
<div>1.1.10-rc6 -> no error</div>
<div>1.1.10-rc7 -> no error</div>
<div>1.1.10-1 -> error</div>
<div> </div>
<div>Rainer</div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Freitag, 26. Juli 2013 um 09:32 Uhr<br/>
<b>Von:</b> "Takatoshi MATSUO" <matsuo.tak@gmail.com><br/>
<b>An:</b> "The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org><br/>
<b>Betreff:</b> Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available</div>
<div name="quoted-content">Hi<br/>
<br/>
I used Stateful RA and caught a same issue.<br/>
<br/>
1. before starting slave<br/>
<br/>
# crm_simulate -VVV -S -x /var/lib/pacemaker/pengine/pe-input-1543.bz2<br/>
| grep "Resource action"<br/>
* Resource action: stateful monitor=2000 on 16-sl6<br/>
<br/>
2. starting slave<br/>
# crm_simulate -VVV -S -x /var/lib/pacemaker/pengine/pe-input-1544.bz2<br/>
| grep "Resource action"<br/>
* Resource action: stateful monitor on 17-sl6<br/>
* Resource action: stateful notify on 16-sl6<br/>
* Resource action: stateful start on 17-sl6<br/>
* Resource action: stateful notify on 16-sl6<br/>
* Resource action: stateful notify on 17-sl6<br/>
* Resource action: stateful monitor=3000 on 17-sl6<br/>
<br/>
3. after<br/>
# crm_simulate -VVV -S -x /var/lib/pacemaker/pengine/pe-input-1545.bz2<br/>
| grep "Resource action"<br/>
* Resource action: stateful monitor=3000 on 17-sl6<br/>
<br/>
Monitor=2000 is deleted.<br/>
Is this correct ?<br/>
<br/>
<br/>
My setting<br/>
--------<br/>
property \<br/>
no-quorum-policy="ignore" \<br/>
stonith-enabled="false"<br/>
<br/>
rsc_defaults \<br/>
resource-stickiness="INFINITY" \<br/>
migration-threshold="1"<br/>
<br/>
ms msStateful stateful \<br/>
meta \<br/>
master-max="1" \<br/>
master-node-max="1" \<br/>
clone-max="2" \<br/>
clone-node-max="1" \<br/>
notify="true"<br/>
<br/>
primitive stateful ocf:heartbeat:Stateful \<br/>
op start timeout="60s" interval="0s" on-fail="restart" \<br/>
op monitor timeout="60s" interval="3s" on-fail="restart" \<br/>
op monitor timeout="60s" interval="2s" on-fail="restart" role="Master" \<br/>
op promote timeout="60s" interval="0s" on-fail="restart" \<br/>
op demote timeout="60s" interval="0s" on-fail="stop" \<br/>
op stop timeout="60s" interval="0s" on-fail="block"<br/>
--------<br/>
<br/>
Regards,<br/>
Takatoshi MATSUO<br/>
<br/>
2013/7/26 Takatoshi MATSUO <matsuo.tak@gmail.com>:<br/>
> Hi<br/>
><br/>
> My report is late for 1.1.10 :(<br/>
><br/>
> I am using pacemaker 1.1.10-0.1.ab2e209.git.<br/>
> It seems that master's monitor is stopped when slave is started.<br/>
><br/>
> Does someone encounter same problem ?<br/>
> I attach a log and settings.<br/>
><br/>
><br/>
> Thanks,<br/>
> Takatoshi MATSUO<br/>
><br/>
> 2013/7/26 Digimer <lists@alteeve.ca>:<br/>
>> Congrats!! I know this was a long time in the making.<br/>
>><br/>
>> digimer<br/>
>><br/>
>><br/>
>> On 25/07/13 20:43, Andrew Beekhof wrote:<br/>
>>><br/>
>>> Announcing the release of Pacemaker 1.1.10<br/>
>>><br/>
>>> <a href="https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.10" target="_blank">https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.10</a><br/>
>>><br/>
>>> There were three changes of note since rc7:<br/>
>>><br/>
>>> + Bug cl#5161 - crmd: Prevent memory leak in operation cache<br/>
>>> + cib: Correctly read back archived configurations if the primary is<br/>
>>> corrupted<br/>
>>> + cman: Do not pretend we know the state of nodes we've never seen<br/>
>>><br/>
>>> Along with assorted bug fixes, the major topics for this release were:<br/>
>>><br/>
>>> - stonithd fixes<br/>
>>> - fixing memory leaks, often caused by incorrect use of glib reference<br/>
>>> counting<br/>
>>> - supportability improvements (code cleanup and deduplication,<br/>
>>> standardized error codes)<br/>
>>><br/>
>>> Release candidates for the next Pacemaker release (1.1.11) can be<br/>
>>> expected some time around Novemeber.<br/>
>>><br/>
>>> A big thankyou to everyone that spent time testing the release<br/>
>>> candidates and/or contributed patches. However now that Pacemaker is<br/>
>>> perfect, anyone reporting bugs will be shot :-)<br/>
>>><br/>
>>> To build `rpm` packages:<br/>
>>><br/>
>>> 1. Clone the current sources:<br/>
>>><br/>
>>> # git clone --depth 0 git://github.com/ClusterLabs/pacemaker.git<br/>
>>> # cd pacemaker<br/>
>>><br/>
>>> 1. Install dependancies (if you haven't already)<br/>
>>><br/>
>>> [Fedora] # sudo yum install -y yum-utils<br/>
>>> [ALL] # make rpm-dep<br/>
>>><br/>
>>> 1. Build Pacemaker<br/>
>>><br/>
>>> # make release<br/>
>>><br/>
>>> 1. Copy and deploy as needed<br/>
>>><br/>
>>> ## Details - 1.1.10 - final<br/>
>>><br/>
>>> Changesets: 602<br/>
>>> Diff: 143 files changed, 8162 insertions(+), 5159 deletions(-)<br/>
>>><br/>
>>> ## Highlights<br/>
>>><br/>
>>> ### Features added since Pacemaker-1.1.9<br/>
>>><br/>
>>> + Core: Convert all exit codes to positive errno values<br/>
>>> + crm_error: Add the ability to list and print error symbols<br/>
>>> + crm_resource: Allow individual resources to be reprobed<br/>
>>> + crm_resource: Allow options to be set recursively<br/>
>>> + crm_resource: Implement --ban for moving resources away from nodes<br/>
>>> and --clear (replaces --unmove)<br/>
>>> + crm_resource: Support OCF tracing when using<br/>
>>> --force-(check|start|stop)<br/>
>>> + PE: Allow active nodes in our current membership to be fenced without<br/>
>>> quorum<br/>
>>> + PE: Suppress meaningless IDs when displaying anonymous clone status<br/>
>>> + Turn off auto-respawning of systemd services when the cluster starts<br/>
>>> them<br/>
>>> + Bug cl#5128 - pengine: Support maintenance mode for a single node<br/>
>>><br/>
>>> ### Changes since Pacemaker-1.1.9<br/>
>>><br/>
>>> + crmd: cib: stonithd: Memory leaks resolved and improved use of glib<br/>
>>> reference counting<br/>
>>> + attrd: Fixes deleted attributes during dc election<br/>
>>> + Bug cf#5153 - Correctly display clone failcounts in crm_mon<br/>
>>> + Bug cl#5133 - pengine: Correctly observe on-fail=block for failed<br/>
>>> demote operation<br/>
>>> + Bug cl#5148 - legacy: Correctly remove a node that used to have a<br/>
>>> different nodeid<br/>
>>> + Bug cl#5151 - Ensure node names are consistently compared without<br/>
>>> case<br/>
>>> + Bug cl#5152 - crmd: Correctly clean up fenced nodes during membership<br/>
>>> changes<br/>
>>> + Bug cl#5154 - Do not expire failures when on-fail=block is present<br/>
>>> + Bug cl#5155 - pengine: Block the stop of resources if any depending<br/>
>>> resource is unmanaged<br/>
>>> + Bug cl#5157 - Allow migration in the absence of some colocation<br/>
>>> constraints<br/>
>>> + Bug cl#5161 - crmd: Prevent memory leak in operation cache<br/>
>>> + Bug cl#5164 - crmd: Fixes crash when using pacemaker-remote<br/>
>>> + Bug cl#5164 - pengine: Fixes segfault when calculating transition<br/>
>>> with remote-nodes.<br/>
>>> + Bug cl#5167 - crm_mon: Only print "stopped" node list for incomplete<br/>
>>> clone sets<br/>
>>> + Bug cl#5168 - Prevent clones from being bounced around the cluster<br/>
>>> due to location constraints<br/>
>>> + Bug cl#5170 - Correctly support on-fail=block for clones<br/>
>>> + cib: Correctly read back archived configurations if the primary is<br/>
>>> corrupted<br/>
>>> + cib: The result is not valid when diffs fail to apply cleanly for CLI<br/>
>>> tools<br/>
>>> + cib: Restore the ability to embed comments in the configuration<br/>
>>> + cluster: Detect and warn about node names with capitals<br/>
>>> + cman: Do not pretend we know the state of nodes we've never seen<br/>
>>> + cman: Do not unconditionally start cman if it is already running<br/>
>>> + cman: Support non-blocking CPG calls<br/>
>>> + Core: Ensure the blackbox is saved on abnormal program termination<br/>
>>> + corosync: Detect the loss of members for which we only know the<br/>
>>> nodeid<br/>
>>> + corosync: Do not pretend we know the state of nodes we've never seen<br/>
>>> + corosync: Ensure removed peers are erased from all caches<br/>
>>> + corosync: Nodes that can persist in sending CPG messages must be<br/>
>>> alive afterall<br/>
>>> + crmd: Do not get stuck in S_POLICY_ENGINE if a node we couldn't fence<br/>
>>> returns<br/>
>>> + crmd: Do not update fail-count and last-failure for old failures<br/>
>>> + crmd: Ensure all membership operations can complete while trying to<br/>
>>> cancel a transition<br/>
>>> + crmd: Ensure operations for cleaned up resources don't block recovery<br/>
>>> + crmd: Ensure we return to a stable state if there have been too many<br/>
>>> fencing failures<br/>
>>> + crmd: Initiate node shutdown if another node claims to have<br/>
>>> successfully fenced us<br/>
>>> + crmd: Prevent messages for remote crmd clients from being relayed to<br/>
>>> wrong daemons<br/>
>>> + crmd: Properly handle recurring monitor operations for remote-node<br/>
>>> agent<br/>
>>> + crmd: Store last-run and last-rc-change for all operations<br/>
>>> + crm_mon: Ensure stale pid files are updated when a new process is<br/>
>>> started<br/>
>>> + crm_report: Correctly collect logs when 'uname -n' reports fully<br/>
>>> qualified names<br/>
>>> + fencing: Fail the operation once all peers have been exhausted<br/>
>>> + fencing: Restore the ability to manually confirm that fencing<br/>
>>> completed<br/>
>>> + ipc: Allow unpriviliged clients to clean up after server failures<br/>
>>> + ipc: Restore the ability for members of the haclient group to connect<br/>
>>> to the cluster<br/>
>>> + legacy: Support "crm_node --remove" with a node name for corosync<br/>
>>> plugin (bnc#805278)<br/>
>>> + lrmd: Default to the upstream location for resource agent scratch<br/>
>>> directory<br/>
>>> + lrmd: Pass errors from lsb metadata generation back to the caller<br/>
>>> + pengine: Correctly handle resources that recover before we operate on<br/>
>>> them<br/>
>>> + pengine: Delete the old resource state on every node whenever the<br/>
>>> resource type is changed<br/>
>>> + pengine: Detect constraints with inappropriate actions (ie. promote<br/>
>>> for a clone)<br/>
>>> + pengine: Ensure per-node resource parameters are used during probes<br/>
>>> + pengine: If fencing is unavailable or disabled, block further<br/>
>>> recovery for resources that fail to stop<br/>
>>> + pengine: Implement the rest of get_timet_now() and rename to<br/>
>>> get_effective_time<br/>
>>> + pengine: Re-initiate _active_ recurring monitors that previously<br/>
>>> failed but have timed out<br/>
>>> + remote: Workaround for inconsistent tls handshake behavior between<br/>
>>> gnutls versions<br/>
>>> + systemd: Ensure we get shut down correctly by systemd<br/>
>>> + systemd: Reload systemd after adding/removing override files for<br/>
>>> cluster services<br/>
>>> + xml: Check for and replace non-printing characters with their octal<br/>
>>> equivalent while exporting xml text<br/>
>>> + xml: Prevent lockups by setting a more reliable buffer allocation<br/>
>>> strategy<br/>
>>><br/>
>>><br/>
>>> _______________________________________________<br/>
>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br/>
>>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br/>
>>><br/>
>>> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br/>
>>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br/>
>>> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br/>
>>><br/>
>><br/>
>><br/>
>> --<br/>
>> Digimer<br/>
>> Papers and Projects: <a href="https://alteeve.ca/w/" target="_blank">https://alteeve.ca/w/</a><br/>
>> What if the cure for cancer is trapped in the mind of a person without<br/>
>> access to education?<br/>
>><br/>
>><br/>
>> _______________________________________________<br/>
>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br/>
>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br/>
>><br/>
>> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br/>
>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br/>
>> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br/>
<br/>
_______________________________________________<br/>
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br/>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br/>
<br/>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br/>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br/>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div>
</div>
</div>
</div></div></body></html>