Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1598718
Description of problem: doing an import when the backend name is exactly "default" fails and imports only the root entry. How reproducible: always. Steps to Reproduce: 1. create a backend with name default: dn: cn=secAuthority\3DDefault,cn=mapping tree,cn=config cn: secAuthority=Default objectClass: top objectClass: extensibleObject objectClass: nsMappingTree nsslapd-state: backend nsslapd-backend: default dn: cn=default,cn=ldbm database,cn=plugins,cn=config cn: default objectClass: extensibleObject objectClass: nsBackendInstance objectClass: top numSubordinates: 4 nsslapd-suffix: secAuthority=Default nsslapd-cachesize: -1 nsslapd-cachememsize: 67108864 nsslapd-readonly: off nsslapd-require-index: off nsslapd-directory: /var/lib/dirsrv/slapd-nslcd/db/default nsslapd-dncachememsize: 67108864 2. import this file: cat mysec.ldif version: 1 # entry-id: 1 dn: secAuthority=Default objectClass: top secAuthority: Default # entry-id: 2 dn: cn=Users,secAuthority=Default objectClass: container objectClass: top cn: Users Actual results: [06/Jul/2018:05:58:54.155501053 -0400] - INFO - import_main_offline - import default: Beginning import job... [06/Jul/2018:05:58:54.157457181 -0400] - INFO - import_main_offline - import default: Index buffering enabled with bucket size 76 [06/Jul/2018:05:58:54.358709382 -0400] - INFO - import_producer - import default: Processing file "/root/mysec.ldif" [06/Jul/2018:05:58:54.361343422 -0400] - INFO - import_producer - import default: Finished scanning file "/root/mysec.ldif" (1 entries) [06/Jul/2018:05:58:54.663126377 -0400] - INFO - import_monitor_threads - import default: Workers finished; cleaning up... [06/Jul/2018:05:58:54.865608097 -0400] - INFO - import_monitor_threads - import default: Workers cleaned up. [06/Jul/2018:05:58:54.868463718 -0400] - INFO - import_main_offline - import default: Cleaning up producer thread... [06/Jul/2018:05:58:54.870880927 -0400] - INFO - import_main_offline - import default: Indexing complete. Post-processing... [06/Jul/2018:05:58:54.872821273 -0400] - INFO - import_main_offline - import default: Generating numsubordinates (this may take several minutes to complete)... [06/Jul/2018:05:58:54.877320870 -0400] - INFO - import_main_offline - import default: Generating numSubordinates complete. [06/Jul/2018:05:58:54.879220836 -0400] - INFO - ldbm_get_nonleaf_ids - import default: Gathering ancestorid non-leaf IDs... [06/Jul/2018:05:58:54.881249929 -0400] - INFO - ldbm_get_nonleaf_ids - import default: Finished gathering ancestorid non-leaf IDs. [06/Jul/2018:05:58:54.896250662 -0400] - ERR - ldbm_ancestorid_new_idl_create_index - Nothing to do to build ancestorid index [06/Jul/2018:05:58:54.898235990 -0400] - INFO - ldbm_ancestorid_new_idl_create_index - import default: Created ancestorid index (new idl). [06/Jul/2018:05:58:54.900606981 -0400] - INFO - import_main_offline - import default: Flushing caches... [06/Jul/2018:05:58:54.902665707 -0400] - INFO - import_main_offline - import default: Closing files... [06/Jul/2018:05:58:54.917758717 -0400] - INFO - dblayer_pre_close - All database threads now stopped [06/Jul/2018:05:58:54.920131450 -0400] - INFO - import_main_offline - import default: Import complete. Processed 1 entries in 0 seconds. (0.00 entries/sec)
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1598718
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.8 (was: 0.0 NEEDS_TRIAGE)
8fa838a master
d8d57c9..8720370 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
https://pagure.io/389-ds-base/pull-request/49831
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2889
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: fixed)
Login to comment on this ticket.