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
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.
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.
Verified in ovirt-ansible-cluster-upgrade-1.1.8-0.1.master.20180925135108.el7.noarch
QE verification bot: the bug was verified upstream
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.