#47785 Inconsistent removal of a suffix and database
Closed: wontfix Opened by nhosoi.

Description of problem:

  1. Stop the server
  2. Update the nsslapd-db-locks in dse.ldif
  3. Create the entries (users and groups)
  4. Start the server
  5. modify referential integrity to postoperation
  6. Run the test
  7. Remove the suffix at the end
  8. Modify the referential integrity plugin type back to betxnpostoperation
  9. Restart the server

Multitude of effects occurred. There were several messages from CoS cache such
as
cos_cache_change_notify: modified entry is NULL--updating cache just in case,
referential integrity plugin didn't log any error messages, removing ldbm entry
and mapping tree entry resulted in 'ldap_delete: Operation not allowed on
non-leaf (66)' visible in log, access log shows that all subentries such as
indexes were deleted.
After the start/restart, error log contained message 'Detected Disorderly
Shutdown last time Directory Server was running, recovering database.'
The ldbm entry for a backend and a mapping tree entry to a suffix were present
in the directory, the suffix was listed as a naming context.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.1.6-25


Metadata Update from @nhosoi:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.3 - 8/14 (August)

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/1116

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

Metadata