[Pacemaker] exportfs resource agent modifications

[Hauke Bruno Wollentin]

Hi there,

we are using exportfs for building datastores for VMWare. 

After migrating 1 NFS resource to another node (after sucessful fencing e.g.), 
VMWare doesn't see that datastore until I manually fire _exportfs -f_ on the 
new cluster node.

I tried to modify the resource agent itself like:

247         restore_rmtab 
248 
249         ocf_log info "File system exported"
250 
251         sleep 5 #added
252 
253         ocf_run exportfs -f || exit $OCF_ERR_GENERIC #added
254 
255         ocf_log info "kernel table flushed" #added
256 
257         return $OCF_SUCCESS

but this didn't do the trick.

Does anyone has an idea how to resolve that issue?

Cheers,
Hauke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20141117/8bb71a95/attachment-0003.sig>