Bug 1423657 - Add value to engine-config to set timeout after successful fence start
Summary: Add value to engine-config to set timeout after successful fence start
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Ondra Machacek
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-17 14:15 UTC by Petr Matyáš
Modified: 2017-05-23 08:13 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:13:28 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: ovirt-4.2+
rule-engine: blocker+
mgoldboi: planning_ack+
mperina: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 75577 0 master MERGED pm: Wait for host to boot when executing start operation 2017-04-20 10:55:05 UTC
oVirt gerrit 75722 0 ovirt-engine-4.1 MERGED pm: Wait for host to boot when executing start operation 2017-04-21 08:01:10 UTC

Description Petr Matyáš 2017-02-17 14:15:06 UTC 
Description of problem:
Now it's about 2 minutes before fencing mechanism tries to fence the host again, but my host takes about 3-4 minutes to boot, this results in fencing the host again and again.

Version-Release number of selected component (if applicable):
4.1.1-1

How reproducible:
always

Steps to Reproduce:
1. have a host that takes more than 2 minutes to boot
2. fence the host
3.

Actual results:
repeated fencing

Expected results:
one successful fence

Additional info:
Comment 1 Martin Perina 2017-02-17 14:40:03 UTC 
It make sense to wait a bit after successful power management start operation in fencing flow before we allow host monitoring to try to contact the host. We are using ServerRebootTimeout (by default 5 minutes) during install host flow when restart of the host is required.

So I'd use the same config value ServerRebootTimeout inside power management start flow:

1. Set host status to Reboot
2. Execute power management start
3. If start was successfully, wait until ServerRebootTimeout interval pass
4. Set host status to Maintenance or NonResponsive (depending of a way how StartVdsCommand was invoked)
Comment 2 Petr Matyáš 2017-04-26 15:14:15 UTC 
Verified on 4.1.2-1
Note You need to log in before you can comment on or make changes to this bug.