Bug 1147218

Summary: Fencing stop/start retry/delay configuration are not exposed to engine-config
Product: Red Hat Enterprise Virtualization Manager Reporter: Eli Mesika <emesika>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Antonin Pagac <apagac>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: gklein, lsurette, oourfali, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ovirt-3.6.0-rc   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The following configuration parameters controls the delay/retry for stop/start power management operations FenceStopStatusDelayBetweenRetriesInSec (10) FenceStopStatusRetries (18) FenceStartStatusDelayBetweenRetriesInSec (10) FenceStartStatusRetries (18) Consequence: Up to now, the values for those parameters was static Fix: Expose those keys to the engine-config tool Result: The values of those keys are now customable via the engine-config tool
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-20 01:11:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eli Mesika 2014-09-28 07:32:25 UTC 
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:
Comment 1 Antonin Pagac 2015-04-29 09:00:42 UTC 
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