+++ This bug was initially created as a clone of Bug #974982 +++ Description of problem: BZ972739 introduced/correct TZ handling but one cannot define it via rhevm-config without editing engine.properties. Version-Release number of selected component (if applicable): sf18 How reproducible: 100% Steps to Reproduce: 1. rhevm-config -s DefaultWindowsTimeZone="Israel Standard Time" 2. 3. Actual results: not possible, rhevm-config does not know the key Expected results: push it to engine.properties so rhevm-config can be used to override value for TZs Additional info: --- Additional comment from Michal Skrivanek on 2013-06-19 05:18:32 EDT --- trivial. And better be backported to 3.2.z --- Additional comment from Michal Skrivanek on 2013-06-23 10:26:43 EDT --- merged to master: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=45fac42e8ea56f74a256e5a1f8507a2405850e24 --- Additional comment from Jiri Belka on 2013-06-28 04:37:27 EDT --- Ok, is3, included in /etc/ovirt-engine/engine-config/engine-config.properties
ok, sf19. But be aware changing TZ in VM properties after a VM is started does not work as one would expect. TZ is changed but the VM's qemu-kvm process still starts with same offset because it is taken from utc_diff column in vm_dynamic table. This is expected behavior for 3.2. there's also little annoying issue about cached TZ value in client's browser - BZ989396.
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. http://rhn.redhat.com/errata/RHBA-2013-1149.html