Bug 2383281

Summary:	389_Directory_Server_3.2.0
Product:	[Fedora] Fedora	Reporter:	Aoife Moloney <amoloney>
Component:	Changes Tracking	Assignee:	Pierre Rogier <progier>
Status:	ON_QA ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	vashirov, zbyszek
Target Milestone:	---	Flags:	progier: needinfo-
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:
Bug Blocks:	2309208

Description Aoife Moloney 2025-07-24 18:37:08 UTC

This is a tracking bug for Change: 389_Directory_Server_3.2.0
For more details, see: https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0

Starting from 389-ds-base version 3.2.0, the directory server no longer supports the deprecated BerkeleyDB, so the LDMB database must be used. Users still using BerkeleyDB will have to migrate their data.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Aoife Moloney 2025-08-19 21:12:24 UTC

Dear change owner, this is a reminder that your change is required to be 100% code complete by August 26, which is the start of beta freeze. Please provide a status update on your change in the Incomplete Changes Report if you are not able to move your change to 'ON_QA' before this date. If you need to defer your change to the next Fedora release, please let me know and I will reassign this bug and the change page. Thank you kindly.

Comment 2 Aoife Moloney 2025-08-19 22:32:08 UTC

Hi @progier, apologies but this bug autoassigned to me for some reason. Can you provide a status update on how this change is going please? All F43 changes need to be 100% code complete by 26 Aug before we go into Beta freeze. If this one is good to go, feel free to change the status to ON_QA or CLOSED. Thanks!

Comment 3 Pierre Rogier 2025-08-21 10:48:00 UTC

Hi @amoloney,
FYI: the code was pushed in Fedora before the mass rebuild, I see it on Rawhide so IMHO we are code complete.

Comment 4 Zbigniew Jędrzejewski-Szmek 2025-09-02 19:14:07 UTC

FESCo discussed this today and voted:
AGREED: The 389 DS Change must be split into two separate ones, one for the feature release
        and one for the database migration. The existing Change approval for the database
        migration remains approved for Fedora 43. The 3.2.0 feature release is deferred to
        Fedora 44. (+6, 0, 0)

Comment 5 Viktor Ashirov 2025-09-03 08:22:36 UTC

I've updated https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0 to reflect that the change is backported to 3.1.3.

Comment 6 Pierre Rogier 2025-09-15 13:38:45 UTC

To split the change, I renamed the page to https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.1.3 for the fedora 43 bdb removal
We still have to create a new 3.2.0 page for F44 to announce the new release