Bug 1069096
| Summary: | sysprep timezone is not working when create pool from template. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yoshinori Takahashi <hkim> |
| Component: | ovirt-engine | Assignee: | Roy Golan <rgolan> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | aburden, acathrow, hkim, iheim, lpeer, mavital, michal.skrivanek, ofrenkel, Rhev-m-bugs, sherold, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | 3.4.0-0.13.beta3 | Doc Type: | Bug Fix |
| Doc Text: |
* In Red Hat Enterprise Virtualization 3.3, if a virtual machine pool with a specific time zone was created from a Windows 2008 template, the time zone setting was represented as the Microsoft Time Zone Index integer rather than a human-readable string. Now, the time zone in the sysprep.inf file is saved in plain text and it is possible again to create virtual machine pools with different time zones from the same template.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-09 15:04:44 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: | |||
|
Comment 1
Omer Frenkel
2014-02-25 11:59:37 UTC
Takahashi-san, easy way round this is to drop a file with an override value for win 2008 (or whatever OS you want to override its values) /etc/ovirt-engine/osinfo.conf.d/10-windows-timezone-fix.properties and restart the engine for the change to take effect. 10-windows-timezone-fix.properties: os.windows_2008.isTimezoneTypeInteger.value = false os.windows_2008x64.isTimezoneTypeInteger.value = false os.windows_2008R2x64.isTimezoneTypeInteger.value = false pending backport to 3.4 Verified in rhevm-3.4.0-0.13.beta3.el6ev.noarch (av6). Verification steps: 1. Create new windows 2008 R2 VM 2. Install rhev-tools and seal the VM - do the "sysprep" procedure. 4. Create template from VM. 5. Create pool from the template with JST time zone "Tokyo Standard Time". **) 6. Run pool vm and then check its timezone setting 7. Check for <TimeZone> in file A:\sysprep.inf **) Beware of bug 1088440, where the sysprep.inf file always contains the time zone set in VM dialog / System side-tab. It ignores time zone set in VM dialog / Initial Run side-tab as well as in the Run Once dialog. Results: 6. The VM has time zone set to Tokyo Standard Time. In Windows the "Date and Time" dialog says: (UTC+09:00) Osaka, Sapporo, Tokyo 7. The time zone in sysprep.inf file is saved in plain text, not integer number. It contains: <TimeZone>Tokyo Standard Time</TimeZone> This behavior is defined in the default OS info configuration file shipped with RHEVM: # grep -r isTimezoneTypeInteger /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties os.windows_xp.isTimezoneTypeInteger.value = true os.windows_2003.isTimezoneTypeInteger.value = true os.windows_2008.isTimezoneTypeInteger.value = false os.windows_2003x64.isTimezoneTypeInteger.value = true os.windows_7.isTimezoneTypeInteger.value = false os.windows_2008x64.isTimezoneTypeInteger.value = false 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-0506.html |