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.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2594.html
Description of problem: If a MODRDN operation is made to an entry that has a managed type present, the links pointing to the renamed entry will not be updated to use the new DN. Version-Release number: 389-ds-base-1.3.4.0-18.el7.x86_64 How reproducible: Always Steps to Reproduce: 1) Enable Linked Attributes plug-in; ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 cn=Linked Attributes,cn=plugins,cn=config changetype: modify replace: nsslapd-pluginEnabled nsslapd-pluginEnabled: on 2) Create the plug-in instance; ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: cn=Manager Link,cn=Linked Attributes,cn=plugins,cn=config changetype: add objectClass: top objectClass: extensibleObject cn: Manager Link linkType: directReport managedType: manager 3) Add two entries; ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: uid=employee1,ou=People,dc=example,dc=com changetype: add objectClass: extensibleobject objectClass: inetorgperson objectClass: organizationalPerson objectClass: person objectClass: top cn: Employee 1 sn: Employee 1 uid: employee1 dn: uid=manager1,ou=People,dc=example,dc=com changetype: add objectClass: extensibleobject objectClass: inetorgperson objectClass: organizationalPerson objectClass: person objectClass: top cn: manager 1 sn: manager 1 uid: manager1 4) Execute link operation; ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: uid=manager1,ou=People,dc=example,dc=com changetype: modify add: directreport directreport: uid=employee1,ou=People,dc=example,dc=com 5) Execute MODRDN operation on the uid=employee1,ou=People,dc=example,dc=com. ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: uid=employee1,ou=People,dc=example,dc=com changetype: modrdn newrdn: uid=employee2 deleteoldrdn: 1 Actual results: ldapsearch -h localhost -p 389 -D "cn=Directory manager" -w Secret123 -b ou=people,dc=example,dc=com # employee2, People, example.com dn: uid=employee2,ou=People,dc=example,dc=com objectClass: extensibleobject objectClass: inetorgperson objectClass: organizationalPerson objectClass: person objectClass: top cn: Employee 3 sn: Employee 3 manager: uid=manager1,ou=people,dc=example,dc=com uid: employee2 # manager1, People, example.com dn: uid=manager1,ou=People,dc=example,dc=com objectClass: extensibleobject objectClass: inetorgperson objectClass: organizationalPerson objectClass: person objectClass: top cn: manager 1 sn: manager 1 directreport: uid=employee1,ou=People,dc=example,dc=com uid: manager1 Expected results: ldapsearch -h localhost -p 389 -D "cn=Directory manager" -w Secret123 -b ou=people,dc=example,dc=com # employee2, People, example.com dn: uid=employee2,ou=People,dc=example,dc=com objectClass: extensibleobject objectClass: inetorgperson objectClass: organizationalPerson objectClass: person objectClass: top cn: Employee 3 sn: Employee 3 manager: uid=manager1,ou=people,dc=example,dc=com uid: employee2 # manager1, People, example.com dn: uid=manager1,ou=People,dc=example,dc=com objectClass: extensibleobject objectClass: inetorgperson objectClass: organizationalPerson objectClass: person objectClass: top cn: manager 1 sn: manager 1 directreport: uid=employee2,ou=People,dc=example,dc=com uid: manager1 Additional info: If we try to repair it with fixup-linkedattrs.pl or "cn=fixup linked attributes task", then "manager" attribute will be deleted from the uid=employee2,ou=People,dc=example,dc=com. And "directreport" will stay the same in the uid=manager1,ou=People,dc=example,dc=com. Also it will be impossible to delete "directreport" after that. ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: uid=manager1,ou=People,dc=example,dc=com changetype: modify delete: directreport modifying entry "uid=manager1,ou=People,dc=example,dc=com" ldap_modify: Server is unwilling to perform (53) additional info: Linked Attrs Plugin: Failed to update link to target entry (uid=employee1,ou=People,dc=example,dc=com) error 32