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

Bug 1343455

Summary:	FIXME: please reduce the OVF_STORE update timeout with 'engine-config -s OvfUpdateIntervalInMinutes=1'
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Jiri Belka <jbelka>
Component:	General	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED WONTFIX	QA Contact:	Jiri Belka <jbelka>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0.0	CC:	bugs, dfediuck, mavital, michal.skrivanek, sbonazzo, stirabos, ylavi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-27 14:13:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1340626
Bug Blocks:

Description Jiri Belka 2016-06-07 11:25:38 UTC

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:

Comment 1 Jiri Belka 2016-06-07 11:26:39 UTC

it is not also clear what would happen after this 5 minutes if the user won't do anything - failure, success, guess...

Comment 2 Michal Skrivanek 2016-06-08 04:37:36 UTC

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

Comment 3 Simone Tiraboschi 2016-06-08 08:07:49 UTC

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.

Comment 4 Red Hat Bugzilla Rules Engine 2016-06-08 12:24:29 UTC

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.

Comment 5 Simone Tiraboschi 2016-06-27 14:13:33 UTC

Design change, we are not going anymore to edit the engine VM to switch the disk.