follow up bug to add validation as per: --- Additional comment from Martin Betak on 2013-10-24 08:16:08 EDT --- Ok, so the problem was the typo in the timezone "IsrEAl Standard Time" and since the engine falls back to GMT when the timezone entered via engine-config is invalid it looks like the value hasn't changed. Posted a patch to add timezone validation to engine-config. +++ This bug was initially created as a clone of Bug #989396 +++ Description of problem: Some values which are changeable with rhevm-config (ie. DefaultWindowsTimeZone) look cached in client's browser and are not refreshed after engine is restarted and the user is re-logged into Admin Portal again. Refreshing the app in browser works but this step is - I think - not documented as mandatory. Version-Release number of selected component (if applicable): sf19 How reproducible: 100% Steps to Reproduce: 1. login into Admin Portal, create new VM, check its TZ in VM properties 2. log out 3. rhevm-config -s DefaultWindowsTimeZone="Isreal Standard Time" 4. login into Admin Portal, create new VM, check its TZ in VM properties Actual results: changed TZ (DefaultWindowsTimeZone) is not taken into account Expected results: the application should not cache these kind of values? Additional info: seems relevant to BZ844429 but it's quite inactive. If it is duplicate, close it. If one must refresh browser after each change with rhevm-config, please state it and put it in docs.
Verified on ovirt version: ovirt-engine-3.4.0-0.7.beta2.el6.noarch [root@dhcp163-53 ~]# engine-config -s DefaultWindowsTimeZone="IsrEAl Standard Time" Cannot set value IsrEAl Standard Time to key DefaultWindowsTimeZone. IsrEAl Standard Time is not a valid time zone for Windows OS. Please enter a value like 'GMT Standard Time' or 'Israel Standard Time'
Closing as part of 3.4.0