#50879 Directory manager may be able to delete tombstones
Closed: wontfix 4 years ago by firstyear. Opened 4 years ago by firstyear.

Issue Description

A user on the mailing lists has reported some issues when they delete tombstones. Tombstones shouldn't be able to be deleted by a user, so I decided to test this and I am able to indeed, delete tombstones.

I think we should consider blocking any delete/modification of tombstones even to directory manager.

@lkrispen What do you think?


No, I don't think so. Tombstones are purged regularily by the replication plugin itself, but we had issues when this had failed for some reasons or when an admin wanted to clear tombstones earlier - so being able to delete them can be useful.

Tombstones are artefacts to be eventually be used in conflict resolution, especially where concurrently an entry was deleted on one master and a child added to this entry on another. But this usually happens immediately and not late in the default 1 week time we keep tombstones. And even if the tombstone was deleted before this conflict is handled a template glue entry is created and replication will continue.
An admin also could configure an extremely small purge delay and get rid ofthe tombstones before they might be needed.

In summary I do not see a need to change the current behaviour

Metadata Update from @lkrispen:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

4 years ago

Ahhh I didn't know about the glue entry, I thought the tombstone was the marker to represent that the entry did exist and was part of the delete lifecycle. In that case, I'll close as invalid.

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 years ago

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

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: fixed)

3 years ago

Login to comment on this ticket.

Metadata