Bug 1992014

Cause: If a fence agent meta-data request fails, Pacemaker previously would consider that result final. While this would be the best response for a permanent issue such as a nonconforming agent, the failure could be transient, for example when Pacemaker is enabled at boot and heavy CPU and/or I/O load at boot causes the meta-data request to time out. Consequence: Pacemaker would not know if the fence agent supports unfencing or other optional features, and would act as if it did not, which could cause unfencing failures and other issues. Fix: If Pacemaker is unable to obtain fence agent meta-data on the first try, it will now periodically retry. Result: Although problems could still occur during a short time window, the meta-data will be obtained when feasible if the failure was transient, and the issues should be recoverable.