Description of problem: When updating oVirt Node, we are bumping up against the timeout, and upgrades sometimes fail. Especially on systems with slower disks, or as problems are fixed in Node which increases the upgrade time, failing to upgrade from engine is a more likely scenario Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install oVirt Node NGN 4.1.1 2. Upgrade to oVirt Node 4.1.2 on a system with slow disks Actual results: Upgrade fails sometimes at 300s. Succeeds every time at 600s. Expected results: Upgrade succeeds. Additional info:
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
(In reply to Ryan Barry from comment #0) > Description of problem: > When updating oVirt Node, we are bumping up against the timeout, and > upgrades sometimes fail. Especially on systems with slower disks, or as > problems are fixed in Node which increases the upgrade time, failing to > upgrade from engine is a more likely scenario > > Version-Release number of selected component (if applicable): > > > How reproducible: > > > Steps to Reproduce: > 1. Install oVirt Node NGN 4.1.1 > 2. Upgrade to oVirt Node 4.1.2 on a system with slow disks > > Actual results: > Upgrade fails sometimes at 300s. Succeeds every time at 600s. The issue here is that the same timeout is used for all SSH connection timeout, so if we increase timeout to 10 minutes it may also in some cases increase timeout to detect failure during SSH Soft Fencing, which could make HA VMs be restarted later. So I'd prefer only to increase SSHInactivityTimeoutSeconds for Upgrade action and use 2 * SSHInactivityTimeoutSeconds as a value for SSH timeout during upgrade
ok, ovirt-engine-4.1.3.4-0.1.el7.noarch tested while upgrading to rhvh-4.1-0.20170609.0+1