Bug 665967

Summary: Free/busy fetch broken
Product: Red Hat Enterprise Linux 6 Reporter: ritz <rkhadgar>
Component: openchangeAssignee: Matthew Barnes <mbarnes>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: ddumas, jkoten, lnovich, mcrha, myllynen, saime, tlavigne, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openchange-1.0-6.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 04:58:47 UTC Type: ---
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: 883017    
Bug Blocks: 782183, 835616, 840699, 960054, 1019901    
Attachments:
Description Flags
patch based on upstream code
none
openchange-1.0-freebusy.patch none

Description ritz 2010-12-28 06:53:08 UTC
Description of problem:
From customer
> I expect to be able to use scheduling when proposing a meeting. While
> there is a function for Free/Busy times for meeting attendees, there is
> no free/busy times displayed. Perhaps this is a configuration issue. I
> looked for help on this and found no information for setting anything
> special for Exchange servers for this function to work in Evolution.


Additional info:
related issue - 
https://bugzilla.redhat.com/show_bug.cgi?id=247800#c56
upstream - 
https://bugzilla.gnome.org/show_bug.cgi?id=601486

Comment 1 ritz 2010-12-28 13:06:30 UTC
Created attachment 470951 [details]
patch based on upstream code

Proposed patch based on upstream code. Needs review/test.

Comment 3 Suzanne Logcher 2011-01-05 19:49:29 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated 
in the current release, Red Hat is unfortunately unable to 
address this request at this time.  This request has been 
proposed for the next release of Red Hat Enterprise Linux.
If you would like it considered as an exception in the 
current release, please ask your support representative.

Comment 5 RHEL Program Management 2011-07-06 01:09:32 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 14 RHEL Program Management 2012-12-14 07:09:28 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 17 Milan Crha 2013-05-09 10:11:32 UTC
The patch is part of 0.32.2, thus I'm marking this as a dependency of bug #883017.

Comment 22 Laura Novich 2013-06-16 09:52:44 UTC
Marking this with DOCS_SCOPED - as this issue will not be documented in the Virtualization Administration Guide

Comment 26 Milan Crha 2013-10-15 07:32:23 UTC
I'm moving this to openchange, because the related fix belongs there. Note that the server doesn't update free-busy information immediately, thus it's possible that an outdated information is received due to server's behaviour. The information received by evolution-ews seems to be more accurate (not talking about slowness of evolution-mapi).

Comment 27 Milan Crha 2013-10-15 07:33:19 UTC
Created attachment 812374 [details]
openchange-1.0-freebusy.patch

Comment 31 errata-xmlrpc 2013-11-21 04:58:47 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.

http://rhn.redhat.com/errata/RHSA-2013-1540.html