Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1069228
Created attachment 866967 stacktrace.1393249880.txt Description of problem: I'm unable to remove ipahost (this is a two host FreeIPA installation) entry from either WEBUI or directly using ldapdelete. Using the former causes ns-slapd process to crash with segmentation fault. # ldapdelete -x -D "cn=Directory Manager" -W "fqdn=sauron.pipebreaker.pl+nsuni queid=9453e301-793511e3-a4d9a4f9-faae4520,cn=computers,cn=accounts,dc=pipebreak er,dc=pl" Enter LDAP Password: ldap_result: Can't contact LDAP server (-1) Version-Release number of selected component (if applicable): 389-ds-base-1.3.2.9-1.fc20.x86_64 Additional info: Stacktrace is attached.
The entry was possibly added on different replica at the same time. One thing strange is that the entry is not flagged as conflict and also has not nsuniqueid (RC of the crash).
A ldapsearch of the entry gives:
{{{ dn: fqdn=xxxxx+nsuniqueid=9453e301-793511e3-a4d9a4f9-faae4520, cn=computers,cn=accounts,SUFFIX cn: xxxx objectClass: ipaobject objectClass: nshost objectClass: ipahost objectClass: pkiuser objectClass: ipaservice objectClass: krbprincipalaux objectClass: krbprincipal objectClass: ieee802device objectClass: ipasshhost objectClass: top objectClass: ipaSshGroupOfPubKeys fqdn: xxxxx managedBy: fqdn=xxxx,cn=computers,cn=accounts,SUFFIX krbPrincipalName: host/xxxx@yyyy serverHostName: zzzz ipaUniqueID: a0cfb424-7935-11e3-940e-00163cb49c5b }}}
I generated conflict entries and deleted them successfully as follows: {{{ $ ldapdelete ... cn=git,ou=test,ou=projects,nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com cn=trac,ou=test,ou=projects,nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com ou=test,ou=projects,nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com ou=projects,nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com uid=test,ou=users,nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com ou=users,nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com
$ ldapsearch ... -b "nsuniqueid=80dd251a-e05711e3-bd6be368-143999b7+o=bees8,ou=organizations,o=example.com" dn No such object (32) Matched DN: ou=organizations,o=example.com }}}
I think the problem was fixed together with #47750. Closing this ticket for now.
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.2.17
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1050
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Duplicate)
Login to comment on this ticket.