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

Bug 1619199

Summary:	Default timeout for upgrade flow is too short
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Petr Kubica <pkubica>
Component:	cluster-upgrade	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.1.6	CC:	amashah, lsvaty, michal.skrivanek, mperina, ratamir
Target Milestone:	ovirt-4.2.7	Keywords:	Automation, AutomationBlocker, ZStream
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ lsvaty: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-cluster-upgrade-1.1.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1643036 (view as bug list)		Environment:
Last Closed:	2018-11-02 14:31:15 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:
Bug Depends On:
Bug Blocks:	1643036

Description Petr Kubica 2018-08-20 10:16:44 UTC

Description of problem:
Default timeout for whole upgrade is 1200s which should be enough for installing packages but in upgrade process there are also migrating VMs from upgraded host and from version 4.2 also rebooting the host at the end of upgrade. Rebooting process of physical host could take up to 10 minutes.
From this point of view 1200s is too short time for upgrading a machine.

This bug was found on clean hosted engine without running VMs except hosted_engine VM

All parts of upgrading (moving to maintenance - migrating, upgrading, rebooting) should be considered in default timeout

note: Time to moving into maintenance could be calculated from number of running VM on upgraded host.


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

Comment 1 Michal Skrivanek 2018-08-21 05:16:11 UTC

It should rather watch progress and bail out in case the VMs cannot migrate away, or reboot takes longer than 15mins, or pkgs download takes more than x, etc.

Comment 2 Martin Perina 2018-08-27 13:23:37 UTC

Let's change the default to 60 minutes, because there is no reliable way how to compute correct timeout. If 60 minutes is not enough, users needs to set their own timeout.

Comment 3 Petr Kubica 2018-09-27 10:41:50 UTC

Verified in 
ovirt-ansible-cluster-upgrade-1.1.8-0.1.master.20180925135108.el7.noarch

Comment 4 Raz Tamir 2018-10-04 12:30:23 UTC

QE verification bot: the bug was verified upstream

Comment 7 Sandro Bonazzola 2018-11-02 14:31:15 UTC

This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.