Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1340626 - Support update of the HE OVF ad-hoc
Support update of the HE OVF ad-hoc
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.6.6
Unspecified Unspecified
urgent Severity high
: ovirt-4.0.2
: 4.0.2
Assigned To: Martin Sivák
sefi litmanovich
:
Depends On:
Blocks: 1343455 1343991
  Show dependency tree / graph
 
Reported: 2016-05-29 03:38 EDT by Roy Golan
Modified: 2016-11-15 06:06 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The configuration of the HE VM was saved but not propagated to the shared storage. Consequence: Hosted engine tooling did not see the updated configuration and had to wait for the normal OVF refresh cycle. Fix: The engine was fixed to push the configuration update to the storage domain immediately. Result: Hosted engine tooling on hosts should see the OVF with updated values almost instantly (meaning about a minute or so).
Story Points: ---
Clone Of:
: 1343991 (view as bug list)
Environment:
Last Closed: 2016-08-23 16:41:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
agent.log and engine.log (933.04 KB, application/x-gzip)
2016-08-02 06:55 EDT, sefi litmanovich 		no flags Details
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 51842 master MERGED core: Update the OVF store when hosted engine VM is edited 2016-10-05 08:10 EDT
oVirt gerrit 59968 None None None 2016-07-04 06:14 EDT
Red Hat Product Errata RHEA-2016:1743 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0 GA Enhancement (ovirt-engine) 2016-09-02 17:54:01 EDT

  None (edit)
Description Roy Golan 2016-05-29 03:38:21 EDT 
Description of problem:
 Once the HE VM config has been changed we must wait for the interval of OvfUpdateIntervalInMinutes to kick in. In HE scenario we would like to eagerly run this operation to prepare for the next run ASAP.

Version-Release number of selected component (if applicable):
 -relevant component is only ovirt-engine 3.6.6

How reproducible:
 100%

Steps to Reproduce:
 1. Update the HE VM
 2. Wait for the OvfUpdater to kick in
 3. See the fresh vm.conf under each HE host updated at /var/run/ovirt-hosted-engine/vm.conf

Actual results:
 - Must wait for OvfUpdater to perform the update

Expected results:
 - Immediately after finishing the Update VM command go and update the OVF
Comment 2 sefi litmanovich 2016-08-02 06:54:26 EDT 
So far failed to see the effect after hotpluging memory to the HE vm.

Set the agent.log to DEBUG level.
added memory to the vm (8192 instead of 4096), the change is reflected in the webadmin but fails in practice:

2016-08-02 06:17:38,094 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-32) [3c39f550] Correlation ID: 3c39f550, Call Stack: null, Custom Event ID: -1, Message: Failed to hot set memory to VM Hos
tedEngine. Underlying error message: unsupported configuration: maxMemory has to be specified when using memory devices 

OVF is expected to update with the new values anyway, but doesn't.
Attaching both engine log and agent log.. notice the 7 hour offset in the time stamp between the logs -> in engine log 06:00 would be 13:00.
Comment 3 sefi litmanovich 2016-08-02 06:55 EDT 
Created attachment 1186745 [details]
agent.log and engine.log
Comment 4 sefi litmanovich 2016-08-11 04:56:38 EDT 
Verified with rhevm-4.0.2.3-0.1.el7ev.noarch, ovirt-hosted-engine-ha-2.0.1-1.el7ev.noarch.
HE OVF does update ad-hoc, might take several minutes for it reflect in vm.conf.
Comment 7 errata-xmlrpc 2016-08-23 16:41:04 EDT 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHEA-2016-1743.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.