Red Hat Bugzilla – Bug 989396
[Admin Portal] Setting config value DefaultWindowsTimeZone has no effect
Last modified: 2014-01-21 17:29:05 EST
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):
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
changed TZ (DefaultWindowsTimeZone) is not taken into account
the application should not cache these kind of values?
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.
need to clear config cache on re-login?
(In reply to Jiri Belka from comment #0)
> seems relevant to BZ844429 but it's quite inactive. If it is duplicate,
> close it.
closing. bug 844429 will be "reactivated".
*** This bug has been marked as a duplicate of bug 844429 ***
[see bug 844429] it seems that we are already reloading the configuration values upon login, and DefaultWindowsTimeZone should be no different. re-opening for investigation.
- from initial investigation, it doesn't look like there is a global configuration loading problem here - problem seems to be specific to TimeZone -> moving to 'virt'.
- there is a chance that Bug 988259 is related (or at least its fix).
@Greg - if this is the case, please assign this BZ to Bug 988259 assignee, copy the relevant oVirt gerrit External Tracker(s) from Bug 988259 to this BZ and move it to MODIFIED (assuming all relevant patches were already merged).
It just seems like the DefaultWindowsTimeZone doesn't do anything at all. It doesn't pre-select the drop down. I can't create a Windows VM with an empty time zone (in an attempt to let it get set to the default.)
My guess is it's related to the problems in bug 988259. Don't see a cache problem. Assigning to bug 988259 assignee.
comment #5 is right. I set 'Israel Standard Time' and new Windows 7 64bit VM has empty TZ in VM properties/database. (I restarted engine, even I used completely clean FF profile.)
checked on is18, Still Default time zone not updated for a new VM, though changed by rhevm-config, and restarted ovirt-engine service.
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.
that's not the point of this bug. The typo checking will be fixed in 3.4. Otherwise the problem seems to be resolved when you use correct time zone in the rhevm-config
I retested it on is21, and found it is working OK in the following flow:
1. Change DefaultWindowsTimeZone to "Israel Standard Time"
2. Service ovirt-engine restart
3. Create a new windows VM, and see that default time zone update to "Israel Standard Time"
Closing - RHEV 3.3 Released