Description of problem: IMO this is not good: ~~~ [WARNING] FIXME: please reduce the OVF_STORE update timeout with 'engine-config -s OvfUpdateIntervalInMinutes=1', this script will wait 5 minutes. ~~~ IMO this is useless, isn't it possible to do it transparently to user? I would expect that this is least hard thing to do (in comparison with all magick with images...). Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.0.0-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. hosted-engine --upgrade-appliance 2. observe 3. Actual results: a manual action is required from user Expected results: [WARNING] FIXME: please reduce the OVF_STORE update timeout with 'engine-config -s OvfUpdateIntervalInMinutes=1', this script will wait 5 minutes. should not appear, it should be done transparently to user Additional info:
it is not also clear what would happen after this 5 minutes if the user won't do anything - failure, success, guess...
Hm, does it control the frequency of all vms update in ovf store? Then we must not do that often as it is a heavy operation. Certainly not every minute. It's ok if this change is temporary only during the HE deployment
when https://gerrit.ovirt.org/#/c/51842/ will go in, we'll can simply remove this since we'll not need anymore to wait for the OvfUpdater to kick in.
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.
Design change, we are not going anymore to edit the engine VM to switch the disk.