Investigate kolab2 to kolab3 conversion issues
Closed, ResolvedPublic8 Story Points


A migration led to a lot of invalid kolab objects. Figure out why they were created in the first place and how to deal with them


Ticket Type

Event Timeline

mollekopf created this task.Mar 7 2016, 9:49 AM
mollekopf edited a custom field.Mar 7 2016, 10:05 AM
mollekopf raised the priority of this task from 60 to High.Mar 7 2016, 10:06 AM

An event has been transformed with empty created date:




The full message looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<event version="1.0" >
 <start-date>2012-10-10T14: 00:00Z</start-date> <summary>test</summary> <organizer> <display-name>Display Name</display-name> <smtp-address></smtp-address> </organizer> <attendee> <display-name>Test Test</display-name> <smtp-address></smtp-address> <status>accepted</status> <request-response>false</request-response> <invitation-sent>false</invitation-sent> <role>required</role> </attendee> <show-time-as>busy</show-time-as> <end-date>2012-10-10T16:00:00Z</end-date>

Which is not even valid xml (the event closing tag is missing.
Also, creation-date and last-modification-date MUST be UTC date-times, not date-only values.

libkolabxml has been enhanced to detect invalid creation dates. Also, kolab-format has been enhanced to not write out objects that had an error during conversion.

mollekopf moved this task from Backlog to Review on the Sprint 201610 board.Mar 7 2016, 5:05 PM
mollekopf closed this task as Resolved.Mar 14 2016, 1:55 PM
vanmeeuwen reopened this task as Open.Mar 29 2016, 5:11 PM
vanmeeuwen added a subscriber: vanmeeuwen.

The tests clearly start failing with this commit added.

mollekopf closed this task as Resolved.Apr 2 2016, 1:52 AM