Description of problem: The following configuration parameters controls the delay/retry for stop/start power management operations FenceStopStatusDelayBetweenRetriesInSec (10) FenceStopStatusRetries (18) FenceStartStatusDelayBetweenRetriesInSec (10) FenceStartStatusRetries (18) The values in brackets are the default values so currently we are waiting for the desired status for 3 min while pooling it each 10 sec for 18 times. In some cases (for example a host that is very slow), we have to enhance those d faults. Those values should be exposed to engine-config in order to be easily change if required. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. engine-config --all | grep Fence DisableFenceAtStartupInSec: 300 version: general FenceQuietTimeBetweenOperationsInSec: 180 version: general FenceProxyDefaultPreferences: cluster,dc version: general 2. 3. Actual results: The delay/retry keys for start/stop can not be accessed from engine-config Expected results: The delay/retry keys for start/stop should be accessed from engine-config Additional info:
Verified in 3.6.0-1 engine-config --all | grep Fence DisableFenceAtStartupInSec: 300 version: general FenceQuietTimeBetweenOperationsInSec: 180 version: general FenceProxyDefaultPreferences: cluster,dc version: general FenceKdumpDestinationAddress: version: general FenceKdumpDestinationPort: 7410 version: general FenceKdumpMessageInterval: 5 version: general FenceKdumpListenerTimeout: 90 version: general CustomFenceAgentMapping: version: general CustomFenceAgentDefaultParams: version: general CustomFenceAgentDefaultParamsForPPC: version: general CustomVdsFenceOptionMapping: version: general CustomVdsFenceType: version: general CustomFencePowerWaitParam: version: general FenceStartStatusRetries: 18 version: general FenceStartStatusDelayBetweenRetriesInSec: 10 version: general FenceStopStatusRetries: 18 version: general FenceStopStatusDelayBetweenRetriesInSec: 10 version: general