Bug 974982
| Summary: | make rhevm-config to set TZ | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> | |
| Component: | ovirt-engine | Assignee: | Martin Betak <mbetak> | |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.3.0 | CC: | acathrow, adahms, cpelland, iheim, jkt, jraju, lpeer, mbetak, michal.skrivanek, pstehlik, Rhev-m-bugs, rhodain, yeylon | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | virt | |||
| Fixed In Version: | is3 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, it was not possible to set the engine time zone using engine-config. With this update, engine-config can now be used to configure the time zone via two keys: DefaultWindowsTimeZone for Windows virtual machines, and DefaultGeneralTimeZone for all other virtual machines.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 984945 (view as bug list) | Environment: | ||
| Last Closed: | 2014-01-21 17:27:38 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 984945 | |||
|
Description
Jiri Belka
2013-06-17 10:11:27 UTC
trivial. And better be backported to 3.2.z merged to master: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=45fac42e8ea56f74a256e5a1f8507a2405850e24 Ok, is3, included in /etc/ovirt-engine/engine-config/engine-config.properties Hello team ,
I do not find the UI consistently showing the right value .
(For rhevm-3.2.3-0.43.el6ev.noarch )
For example:
# rhevm-config -s DefaultWindowsTimeZone="Israel Standard Time"
# rhevm-config -s DefaultGeneralTimeZone="Israel Standard Time"
# engine-service restart
I notice in New VM window , for Unassigned vms 'default:null' &
for windows vm , it show the right tz 'default: (GMT+02:00)......'
Although in many other scenarios , both Unassigned as well as windows
VMs do not show the right timezone .
For example :
rhevm-config -s DefaultWindowsTimeZone="Central European Time"
# rhevm-config -s DefaultGeneralTimeZone="Central European Time"
# psql -U engine -c " SELECT * from vdc_options where option_name like 'Default%TimeZone';"
Password for user engine:
option_id | option_name | option_value | version
-----------+------------------------+-----------------------+---------
44 | DefaultWindowsTimeZone | Central European Time | general
45 | DefaultGeneralTimeZone | Central European Time | general
In this case both VMs windows & non-windows VMs gives 'default:null' in new
VM option .
So my query is , Is this bugzilla for the same issue ? or
should I open a new bugzilla ?
Thanks,
Regards,
Jaison R
Hi Jaison, in rhevm-config we store timezones separately for windows and non-windows systems because windows uses different format than the standardized rest of the world :-) In your case you should do # rhevm-config -s DefaultWindowsTimeZone="Israel Standard Time" # rhevm-config -s DefaultGeneralTimeZone="Asia/Jerusalem" What we are missing right now is the validation of entered timezones; that is why you see default: null - an incorrect timezone was set via rhevm-config. You should not be even able to set "Israel Standard Time" to DefaultGeneralTimeZone. Please feel free to open a bug for that. Best Regards Martin This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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/RHSA-2014-0038.html |