Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1947403

Summary:	Increase reboot timeout to 10 min.
Product:	[oVirt] ovirt-engine	Reporter:	Dana <delfassy>
Component:	Tools.Config	Assignee:	Dana <delfassy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Guilherme Santos <gdeolive>
Severity:	high	Docs Contact:
Priority:	high
Version:	future	CC:	bugs, mperina
Target Milestone:	ovirt-4.4.6	Flags:	pm-rhel: ovirt-4.4+
Target Release:	4.4.6.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-14 07:27:56 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 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