Page MenuHomePhorge
Create Task
Maniphest T8379

Upgrade path from Ubuntu 18.04 or the future of kolab packages
Open, Needs TriagePublic
Actions

Description

There has been a problem with the upgrade path for the ds-389 package in Ubuntu for several years and it is clear that Canonical is not going to fix this. My narrow question is, is there any way to work around this to enable upgrading a Kolab install from the now unsupported 18.04?

My larger question is that I have had to move and reinstall my Kolab server twice before because there was no upgrade path from either the debian or ubuntu versions I was on at the time. In general is there a distribution that Kolab is committing to supporting? Is it going to remain possible to run my own hosted Kolab going into the future?

Details

Ticket Type
Task

Related Objects

Event Timeline

emunson created this task.Jul 5 2024, 7:44 PM
Spenneberg subscribed.Jul 8 2024, 3:01 PM
Spenneberg added a comment.Jul 16 2024, 2:33 PM

Hi there,
I was just able to successfully upgrade from CentOS 7 to Almalinux 9. Everything seems to be working the in place upgrade of the 389ds and the cyrus imapd were a bit of a hassle, but after testing it several times based on backups it worked ok. I can share my list of commands.

emunson added a comment.Jul 21 2024, 1:11 PM

Please do, that might help me get the 389ds update for ubuntu functioning and get me off of 18.04 finally.

ghane subscribed.Jul 22 2024, 4:08 PM

389ds update issue resides on Ubuntu, it is not a Kolab issue.

389ds has a change from Perl to Python scripts, please read the 389ds manual for further information and changes.

Missing link! Your reference of Canonical and 389-ds upgrade citation?

The install path with known errors and fixes for Debian is in T7247, this should also fit for Ubuntu.
As it is an old thread, many things are fixed, but it is a good reference for upcoming errors and their fixes.

LDIF export/import could be the workaround you're looking for. On last chance doing a full disaster recovery of LDAP with your LDIF exports.

For origin packages (cyrus, 389-ds, mysql v mariadb) read the distributors upgrade guides.

emunson added a comment.Jul 25 2024, 9:27 PM

Sorry, I didn't mean to imply otherwise on the 389ds issue, I knew it was upstream that was broken but also that it is required for Kolab and has been stopping an update to 20.04.

For reference, here is the Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1895410 AFAIK, there is no workaround for the 389-ds upgrade failure and given that the bug in question has been open for 4 years, I don't suspect it is going to be fixed. I will attempt to export of my LDAP server force the upgrade (probably by removing and reinstalling 389-ds) and see if that gets me working again.

pasik subscribed.Nov 26 2024, 10:33 PM
emunson mentioned this in T8416: Kolab Ubuntu 20.04 and newer repos are missing packages.Jan 30 2025, 2:19 PM

So the 389-ds packages are a mess in Ubuntu. The tools and scripts needed to update the on disk formats are not built and when I enable them they are broken. I am not sure if the upstream source is broken or it comes from the patches applied by Debian or Ubuntu. The only thing that I found worked was moving the contents of /var/lib/dirsrv and /etc/dirsrv to a backup, then upgrade from 18.04 to 20.04 and return the contents before rebooting. There were several other hiccups in the process as kolab packaging for Ubuntu newer than 18.04 is broken and missing packages, see: https://git.kolab.org/T8416