Hide Forgot
Created attachment 1211666 [details] proposed fix Description of problem: Start of resource ocf:heartbeat:Delay fails when startdelay is not explicitly specified. The reason is that startdelay defaults to 30s and default timeout for operation is 30s as well. So it fails before it starts. How reproducible: always Steps to Reproduce: [vm-rhel68-1 ~] $ pcs resource create delay Delay stopdelay=15 && sleep 31 && pcs resource Actual results: delay (ocf::heartbeat:Delay): FAILED[ vm-rhel68-2 vm-rhel68-1 ] Expected results: delay (ocf::heartbeat:Delay): Started vm-rhel68-1 Additional info: It is possible to adapt either default of startdelay or defaults of operation. Reduce value of default stardelay could be better choice: 30s is probably unnecessarily long time.
https://github.com/ClusterLabs/resource-agents/pull/862/commits
I have verified that the startdelay is shorter than the monitor delay by default which allow ocf:heartbeat:Delay to start correctly with resource-agents-3.9.5-43.el6 ----- before the fix resource-agents-3.9.5-37.el6 =========================================== [root@virt-007 ~]# pcs resource create delay Delay stopdelay=15 Creating resource 'ocf:heartbeat:Delay' [root@virt-007 ~]# sleep 31 [root@virt-007 ~]# pcs resource delay (ocf::heartbeat:Delay): FAILED virt-007 after the fix resource-agents-3.9.5-43.el6 ========================================== [root@virt-007 ~]# pcs resource create delay Delay stopdelay=15 Creating resource 'ocf:heartbeat:Delay' [root@virt-007 ~]# sleep 31 [root@virt-007 ~]# pcs resource delay (ocf::heartbeat:Delay): Started virt-007
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0602.html