After failed 'demote' operation the resource start is delayed until next `cluster-recheck-interval`

Issue

• When the demote operation of a cluster resource fails, pacemaker doesn't start back the resource immediately. Instead, it waits for some action to happen in the cluster (like creation/update/delete of resource) or up to cluster-recheck-interval to start the resource again.
• crm_simulate -LR output shows that the resource which failed the 'demote' operation should be started, but nothing is happening.