Bug 436046
Summary: | openldap-servers RPM unnecessarily does dump / restore of database | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Frode Nordahl <frode> |
Component: | openldap | Assignee: | Jan Safranek <jsafrane> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | CC: | christoph.maser, jplans |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 20:53:41 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: |
Description
Frode Nordahl
2008-03-04 23:22:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. I've applied the scripts from Fedora Rawhide, i.e.: - The openldap-servers package update should do the automatic database dump/restore when really needed, i.e. when BDB version changes (and it _shouldn't_ change during RHEL 5 lifetime). - When the openldap minor version changes (2.3.x -> 2.4.x), the db_upgrade should be called automatically (again, highly unlikely in RHEL 5). - All these automatic operations are done only on BDB database stored in default directory, i.e. /var/lib/ldap. You must care about your databases manually if you have them somewhere else. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0090.html |