ClusterLabs/pacemaker — pull request #274 by gao-yan (2013-04-10 05:21:21+00:00)
Title: Fix: crmd: Do not update fail-count and last-failure for old failures

A DC election may introduce a lrm status refresh. If there are
previously failed lrm operations, crmd will notice them as "Old event".
While that will still trigger the update of fail-count and last-failure.
If the resource has "migration-threshold" or "failure-timeout"
attribute, that can cause unnecessary migration.

Does this make sense? Or should we directly check if the crm-debug-origin="build_active_RAs"?