pacemaker fails with error "status=Timed out" when starting an NFS-based Filesystem resource initially after boot in a RHEL 7 High Availability cluster

Issue

• The cluster management software, pacemaker, does not bring a Filesystem resource online properly after a cluster node is rebooted

Failed actions:
    fs-nfsFS_start_0 on node1.example.com 'unknown error' (1): call=211, status=Timed Out, exit-reason='none', last-rc-change='Wed Jun  3 10:03:23 2015', queued=0ms, exec=60003ms

• pacemaker always fails to mount our NFS file system the first time while the system is booting. If we restart the resource afterwards it starts just fine.
• Filesystem resource with fstype=nfs times out during start on boot:

Jun  2 15:57:25 node1 lrmd[3174]: warning: child_timeout_callback: fs-nfsFS_start_0 process (PID 4530) timed out
Jun  2 15:57:25 node1 lrmd[3174]: warning: operation_finished: fs-nfsFS_start_0:4530 - timed out after 60000ms
Jun  2 15:57:25 node1 crmd[3177]: error: process_lrm_event: Operation fs-nfsFS_start_0: Timed Out (node=node1.example.com, call=209, timeout=60000ms)
Jun  2 15:57:25 node1 Filesystem(fs-nfsFS)[7272]: INFO: Running stop for nfsserver.example.com:/nfsFS on /nfsFS
Jun  2 15:57:25 node1 crmd[3177]: notice: process_lrm_event: Operation fs-nfsFS_stop_0: ok (node=node1.example.com, call=233, rc=0, cib-update=86, confirmed=true)
Jun  2 15:57:28 node1 systemd: Started NFS status monitor for NFSv2/3 locking..
Jun  2 15:57:28 node1 systemd: Startup finished in 2.172s (kernel) + 1.433s (initrd) + 1min 17.810s (userspace) = 1min 21.416s.