Description of problem:
currently when a Start/Stop operation is invoked, the default number of retries is 3 while the delay between retries is 60 sec.
That means that if when we initially check the status after a Start/Stop operation it does not reach on/off status we will have to wait 60 seconds to sample the status again
A shorter delay of 10 seconds while keeping the total default waiting time untouched (means modifying default number of retries to 18 will improve user experience in PM operations
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1.Run a system with 2 Hosts h1 & h2 , h1 has PM
2.turn vdsmd down on h1
3.h1 will be fenced by h2
4.sometimes it will take more than a minute to update h1 status
Actual results:
Status change is delay due to improper value of delay between retries
FenceStartStatusDelayBetweenRetriesInSec=60
FenceStartStatusRetries=3
FenceStopStatusDelayBetweenRetriesInSec=60
FenceStopStatusRetries=3
Expected results:
Status should be changed ASAP
Default config values should be changed to
FenceStartStatusDelayBetweenRetriesInSec=10
FenceStartStatusRetries=18
FenceStopStatusDelayBetweenRetriesInSec=10
FenceStopStatusRetries=18
Additional info: