Bug 1718219

Description of problem:
every 60s, pacemaker monitors the health of the bundle resources by probing whether the hosting containers are still running (i.e. "docker inspect") and whether we can exec a command into them (i.e. "docker exec").
The probe has a default timeout of 20s since OSP 12, and has proved largely sufficient under idle or loaded environment.

in OSP15, however, when podman containers are hosted in a FS under IO load, some commands like "podman inspect" may last for an unbounded/unpredictable long time, which makes the probe time out. In that case, pacemaker considers the container dead and tries to force-restart it, which breaks the control plane's service availability. 

Version-Release number of selected component (if applicable):
resource-agents-4.2.0-2.fc30.x86_64

How reproducible:
This has been reproduced on bare metal and VM
With either slow SATA disk (BM) or fast SSD (VM)
When there's some IO load applied on the system

Steps to Reproduce:
1. deploy an Openstack, with HA control plane

2. run an simple IO load on one controller
echo 2 > /proc/sys/vm/drop_caches
sync
dd if=/dev/zero of=bigtestfile bs=1M

3. wait for at most 60s until pacemaker starts probing a podman container.
pcs status

Actual results:
probes fail, pacemaker restarts bundles and break control plane service on the node where the IO load runs.

Expected results:
pacemaker successfully runs the probe and the cluster keeps running normally


Additional info:
One of the root causes is the podman RA which needlessly calls podman commands multiple times. In this BZ we'd like to track the optimizations that we can do in the podman resource agent.