High: Xen: retry domain lookup in repeating monitor and stop

If the guest is rebooting, it may completely disappear from the
list of defined guests, thus xm/xen-list would return with not
running. Apparently, this period lasts only for a second or two.
It is easily reproducible by rebooting the guest.

The effect is that a guest can be started on two nodes in
parallel or even twice on the same node thus resulting in guest's
filesystems corrupted.

In both stop and repeating monitor actions, if we encounter no
domain (OCF_NOT_RUNNING), we keep trying for the next 5 seconds.

The impact of this patch is that when stopping a non-existent
domain or unexpected disappearance of a running domain there will
be an extra 5 second delay.

This should be repaired within the xen domain.
Medium: Tools: ocf-tester: don't use bash to run agents, they're executable anyway
Fix: VirtualDomain: Fixes comparison of uninitialized variable during force stop
Merge pull request #321 from davidvossel/virtdomain_default_uri_fix

Fix: VirtualDomain: Fixes comparison of uninitialized variable during force stop
Merge pull request #314 from dmuhamedagic/xensleep

High: Xen: retry domain lookup in repeating monitor and stop
Merge pull request #317 from dmuhamedagic/ocf-tester-no-bash

bash is not necessary to invoke resource agents
Don't consider cloned ip as cluster ips if there're set on lo

https://github.com/ClusterLabs/resource-agents/issues/323
Merge branches 'master' and 'master' of git://github.com/ClusterLabs/resource-agents into last_2_fixes
Merge branch 'RA_323' of github.com:llaurent/resource-agents into last_2_fixes