Bug 1947403 - Increase reboot timeout to 10 min.
Summary: Increase reboot timeout to 10 min.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Tools.Config
Version: future
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.6
: 4.4.6.4
Assignee: Dana
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-08 12:15 UTC by Dana
Modified: 2021-05-14 07:27 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.4.6.4
Doc Type: Release Note
Doc Text:
By default we are waiting a certain amount of time defined by engine-config option ServerRebootTimeout before we consider that a hypervisor finished rebooting. Before oVirt 4.4.6 this timeout has been set to 5 minutes, but from 4.4.6 we are increasing the default to 10 minute. If this is not enough and hypervisors in your setup requires more time to finish rebooting, then please use below commant: engine-config -s ServerRebootTimeout=NNN where NNN is number of seconds which engine waits until it tries to connect to the hypervisor after a reboot. ovirt-engine service needs to be restarted after above change to take effect.
Clone Of:
Environment:
Last Closed: 2021-05-14 07:27:56 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 114283 0 master MERGED core: Increase default timeout to reboot a host 2021-04-14 10:31:01 UTC

Description Dana 2021-04-08 12:15:21 UTC 
Description of problem:
The default value is currently set to 5 min. and should be increased to 10 min.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Guilherme Santos 2021-05-10 15:49:45 UTC 
Verified on:
ovirt-engine-4.4.6.6-0.10.el8ev.noarch

Steps:
1. Restart a host on webadmin UI
2. Before the host finish restarting, plug it off (turning it off completely).
3. Wait 10+ min and checked host status on UI

Results:
host got non responsive status after 10min
Note You need to log in before you can comment on or make changes to this bug.