Bug 1024271

Summary: Free/Busy Information returns wrong time
Product: Red Hat Enterprise Linux 6 Reporter: Jiri Koten <jkoten>
Component: evolution-exchangeAssignee: Matthew Barnes <mbarnes>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: fabiano, fidencio, mcrha, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: evolution-exchange-2.32.3-19.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1029538 (view as bug list) Environment:
Last Closed: 2017-03-21 09:09:01 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:
Bug Depends On:    
Bug Blocks: 1029538, 1363705, 1366206    
Attachments:
Description Flags
ews patch none

Description Jiri Koten 2013-10-29 09:44:57 UTC
Description of problem:
When scheduling meeting, evolution can query Free/Busy time for meeting attendees. But it returns wrong time, it seems to be shifted by two ours in my case.

I'm using EWS backend and MS Exchange 2010 server.

Version-Release number of selected component (if applicable):
evolution-exchange-2.32.3-16.el6
evolution-data-server-2.32.3-18.el6
evolution-2.32.3-30.el6

How reproducible:
100%

Steps to Reproduce:
1. On first account create an appointment - make sure it shows time as busy
2. On second account schedule a meeting request with first account as required participant an choose the same time as the app. created in the first step
3. Query Free/Busy Time 

Actual results:
It shows wrong time, doesn't show that the participant is busy at the given time

Expected results:
It shows that participant is busy 


Additional info:

Comment 1 Fabiano FidĂȘncio 2013-10-29 12:29:23 UTC
It was closed upstream recently[0]. I do believe that Milan had this commit back ported to RHEL 6.5, as commit: ca3bb358ef5784450c930dcf8889e129eecc9461

[0]: https://git.gnome.org/browse/evolution-ews/commit/?id=85eae2d7e225320fbf6f81d67d172cdafd094944

Also, I think this bug is duplicated of #1018301

Comment 2 Milan Crha 2013-11-04 20:50:17 UTC
(In reply to Fabiano FidĂȘncio from comment #1)
> It was closed upstream recently[0]. I do believe that Milan had this commit
> back ported to RHEL 6.5, as commit: ca3bb358ef5784450c930dcf8889e129eecc9461
> 
> [0]:
> https://git.gnome.org/browse/evolution-ews/commit/
> ?id=85eae2d7e225320fbf6f81d67d172cdafd094944
> 
> Also, I think this bug is duplicated of #1018301

Right, the upstream fix was added within evolution-exchange-2.32.3-15.el6, as part of bug #1018301.

(In reply to Jiri Koten from comment #0)
> When scheduling meeting, evolution can query Free/Busy time for meeting
> attendees. But it returns wrong time, it seems to be shifted by two ours in
> my case.

I see, the times are expected in UTC, thus there might be some issue with timezone correction.

Comment 3 Milan Crha 2013-11-12 07:24:25 UTC
Created attachment 822774 [details]
ews patch

for evolution-ews;

Because the Free/Busy is expected in UTC, but EWS' calendar backend has set other than that 'default_timezone', it applies the shift from UTC twice, once in the backend, the other time in the evolution's UI. RHEL7 (3.8.5) doesn't seem to be affected, same as 3.10/3.11 is not affected, because it doesn't change the backend's default_timezone anymore. I'll apply the change to 3.10/3.11 anyway, to have sources in sync.

Comment 4 Milan Crha 2013-11-12 07:36:18 UTC
Upstream commits in evolution-ews: a018dda on master (3.11.2+), 0416799 on gnome-3-10 (3.11.3+).

(In reply to Milan Crha from comment #3)
> RHEL7 (3.8.5) doesn't seem to be affected

Thinking of it, maybe you can clone the bug for rhel7 as well, if for nothing then to be sure and to have code in sync.

Comment 10 errata-xmlrpc 2017-03-21 09:09:01 UTC
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.

https://rhn.redhat.com/errata/RHBA-2017-0581.html