Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Modifications cannot be performed on the default olcDatabase={-1}Frontend due to the olcDatabase attribute being incorrect as opposed to the distinguished name.
Default install shows:
dn: olcDatabase={-1}frontend
olcDatabase: frontend
Should be:
dn: olcDatabase={-1}frontend
olcDatabase: {-1}frontend
Version-Release number of selected component (if applicable):
openldap-servers-2.4.39-3.el7.x86_64
How reproducible:
On first installation of openldap-servers package/Always.
Steps to Reproduce:
1. Install openldap-servers
2. Attempt to modify olcDatabase={-1}Frontend
Actual results:
[root@library ldif]# ldapmodify -xWD "cn=config" -f ~/stuff
Enter LDAP Password:
modifying entry "olcDatabase={-1}frontend,cn=config"
ldap_modify: Naming violation (64)
additional info: value of naming attribute 'olcDatabase' is not present in entry
Expected results:
modifying entry "olcDatabase={-1}frontend,cn=config"
(No errors)
Additional info:
This is corrected by manually editing /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{-1\}frontend.ldif - Which is discouraged.
This is also similar to bug: 1132094, which states that the ldif is also missing an important objectClass.
Description of problem: Modifications cannot be performed on the default olcDatabase={-1}Frontend due to the olcDatabase attribute being incorrect as opposed to the distinguished name. Default install shows: dn: olcDatabase={-1}frontend olcDatabase: frontend Should be: dn: olcDatabase={-1}frontend olcDatabase: {-1}frontend Version-Release number of selected component (if applicable): openldap-servers-2.4.39-3.el7.x86_64 How reproducible: On first installation of openldap-servers package/Always. Steps to Reproduce: 1. Install openldap-servers 2. Attempt to modify olcDatabase={-1}Frontend Actual results: [root@library ldif]# ldapmodify -xWD "cn=config" -f ~/stuff Enter LDAP Password: modifying entry "olcDatabase={-1}frontend,cn=config" ldap_modify: Naming violation (64) additional info: value of naming attribute 'olcDatabase' is not present in entry Expected results: modifying entry "olcDatabase={-1}frontend,cn=config" (No errors) Additional info: This is corrected by manually editing /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{-1\}frontend.ldif - Which is discouraged. This is also similar to bug: 1132094, which states that the ldif is also missing an important objectClass.