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-98.el7

-----

before the fix resource-agents-3.9.5-81.el7
===========================================

[root@virt-135 ~]# pcs resource create delay ocf:heartbeat:Delay stopdelay=15 

[root@virt-135 ~]# sleep 31

[root@virt-135 ~]# pcs status
...
 delay  (ocf::heartbeat:Delay): FAILED (virt-135)
...
Failed Actions:
* delay_start_0 on virt-137 'unknown error' (1): call=293, status=Timed Out, exitreason='none',
    last-rc-change='Wed May 17 14:41:43 2017', queued=0ms, exec=30004ms
* delay_start_0 on virt-135 'unknown error' (1): call=77, status=Timed Out, exitreason='none',
    last-rc-change='Wed May 17 14:42:28 2017', queued=0ms, exec=30012ms
* delay_monitor_0 on virt-136 'unknown error' (1): call=64, status=Timed Out, exitreason='none',
    last-rc-change='Wed May 17 14:41:13 2017', queued=0ms, exec=30004ms

after the fix resource-agents-3.9.5-98.el7
==========================================

[root@virt-135 ~]# pcs resource create delay ocf:heartbeat:Delay stopdelay=15 

[root@virt-135 ~]# sleep 31

[root@virt-135 ~]# pcs resource
> delay  (ocf::heartbeat:Delay): Started virt-135

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://access.redhat.com/errata/RHBA-2017:1844