RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
- Updating from openldap 2.4.39 to 2.4.40 causes LDAP database to be blank.

Version-Release number of selected component (if applicable):
- openldap-2.4.39-8.el6

How reproducible:


Steps to Reproduce:
1. yum update openldap
2.
3.

Actual results:
- Blank database

Expected results:
- Database is not blank

Additional info:

Closing this as I am unable to reproduce with multiple attempts.

I also encountered this issue. I tracked it down to this block from the preinstall script from the RPM (rpm -q --scripts openldap-servers):

# move or copy to backup directory
                        find -maxdepth 1 -type f \( -name alock -o -name "*.bdb" -o -name "__db.*" -o -name "log.*" \) \
                                | xargs -I '{}' $backupcmd '{}' $backupdir
                        cp -af DB_CONFIG $backupdir &>/dev/null

So basically, the databases files from /var/lib/ldap get backed up to /var/lib/ldap/backup.NNNNNNNNNNN/ if the openldap version number changes.

I found this a bit unsettling from a user point of view. Maybe could a notice get printed out to warn the user ?

Striker, what do you think ? Can this bugreport maybe be reopened with wishlist severity ? Thanks !

Marc, so that you are aware, a new BZ was opened for RFE to add notification of the database backup:
https://bugzilla.redhat.com/show_bug.cgi?id=1261651