Is this going into 3.6.8 in the coming days?
Failed to verify with bla bla, ovirt-hosted-engine-ha-1.3.5.8-1.el7ev.noarch.rpm, vdsm-4.17.34-1.el7ev.noarch. STEPS: 1. Installed ovirt-hosted-engine-setup and rhevm-appliance. 2. Deployed hosted-engine using appliance. 3. Upgraded the engine to latest build - bla bla. 4. Added storage domain to the env - hosted engine vm appears in the system. 5. Set agent.log to DEBUG mode. 6. Set OvfUpdateIntervalInMinutes=1 and restart engine. 7. See in agent.log that the agent communicates with ovf store and fetches vm's configurations as it should. 8. Set OvfUpdateIntervalInMinutes=60 again in order for the update of the ovf occur not due to interval but due to the vm's update. 9. restart engine again. 10. wait a few moments then in the engine update the HE vm and add more memory (action shouldn't fail and DB should show the new value although in practice the action is blocked for HE, but configuration should change nonetheless). 11. In engine log I see 'ProcessOvfUpdateForStoragePoolCommand' being called immediately after change. 12. wait a few minutes and look for the change in the ovf in agent.log and vm.conf - nothing is changed. 13. Set again OvfUpdateIntervalInMinutes=1 and restart engine - after 1 minutes the ovf is updated as it should have been earlier with the new memory value. Will attach engine and agent logs.
Created attachment 1196455 [details] agent angd engine log
sorry - in comment 2 - bla bla was place holder for rhevm-3.6.9-0.1.el6.noarch
Verified with HE rhevm-3.6.10.1-0.1.el6.noarch host: vdsm-4.17.37-1.el7ev.noarch ovirt-hosted-engine-ha-1.3.5.9-2.el7ev.noarch ovirt-hosted-engine-setup-1.3.7.3-1.el7ev.noarch Verified according to the description, the HE vm's OVF is updated immediately as expected.
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-2017-0108.html