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
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.
Created attachment 1186745 [details] agent.log and engine.log
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.
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