Bug 1550621 - Windows guest in PST timezone differs
Summary: Windows guest in PST timezone differs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Michal Skrivanek
QA Contact: Vitalii Yerys
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-01 16:18 UTC by netrepairca
Modified: 2018-03-29 11:11 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.2.2.4
Clone Of:
Environment:
Last Closed: 2018-03-29 11:11:37 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 88402 0 master MERGED core: remove duplicate PST timezone mapping 2020-07-02 08:56:12 UTC
oVirt gerrit 88420 0 ovirt-engine-4.2 MERGED core: remove duplicate PST timezone mapping 2020-07-02 08:56:12 UTC
oVirt gerrit 88425 0 ovirt-engine-4.1 MERGED core: remove duplicate PST timezone mapping 2020-07-02 08:56:12 UTC

Description netrepairca 2018-03-01 16:18:13 UTC 
Description of problem:


Version-Release number of selected component (if applicable): oVirt 4.2


How reproducible:


Steps to Reproduce:
1. Create new Windows VM (tested 7, 10, 2008r2)on hosted engine or self-hosted
2. Set System>General-Hardware Clock Time Offset to GMT-8:00 PST in VM Config
3. Set timezone to PST within Windows.

Actual results: Will receive error, "Actual timezone in the guest differs from the configuration"


Expected results: No error message.


Additional info: This only seems to happen on Windows VMs in PST timezone. (ex. If config and VM is set to EST there is no error.)
Comment 1 Michal Skrivanek 2018-03-02 11:44:33 UTC 
already reported in bug 1548174
Comment 2 Michal Skrivanek 2018-03-02 16:28:06 UTC 
would you be able to verify with a testing 4.2 build? which build do you have exactly? (check rpm -q ovirt-engine)
Comment 3 netrepairca 2018-03-03 18:05:18 UTC 
(In reply to Michal Skrivanek from comment #2)
> would you be able to verify with a testing 4.2 build? which build do you
> have exactly? (check rpm -q ovirt-engine)

Yes, Currently on ovirt-engine-4.2.1.7-1.el7
Comment 4 Michal Skrivanek 2018-03-03 19:54:46 UTC 
(In reply to netrepairca from comment #3)
> (In reply to Michal Skrivanek from comment #2)
> > would you be able to verify with a testing 4.2 build? which build do you
> > have exactly? (check rpm -q ovirt-engine)
> 
> Yes, Currently on ovirt-engine-4.2.1.7-1.el7

can you try to upgrade to a testing 4.2.2 build? just add/replace this as a baseurl in yum.repos: http://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-on-demand-el7-x86_64/23/artifact/exported-artifacts/
and upgrade as usual with yum update, engine-setup.
Please engine-backup/restore just in case...
Comment 5 netrepairca 2018-03-05 22:18:36 UTC 
Yes, the problem seems resolved in this build. Thanks
Comment 6 Michal Skrivanek 2018-03-06 09:15:30 UTC 
great, thanks for confirmation, it's going to be in the next 4.2.2 build (RC or final). If you plan to keep using the current setup please update to it once released
Comment 7 Vitalii Yerys 2018-03-16 16:40:33 UTC 
Verified with:
Software Version:4.2.2.4-0.1.el7
Comment 8 Sandro Bonazzola 2018-03-29 11:11:37 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.