389-ds-base

#50015 Provide plugin to simulate plugin failures
Closed: wontfix by spichugi. Opened by lkrispen.

Closed: wontfix
Reopen Issue

Issue Description

Ticket #49967 deals with a problem where a plugin failure caused an entrycache corruption and further failures. It was hard to reproduce this specific plugin failure and the idea was reaised to develop a specific plugin which could trigger failure on demand.

I had provided an initial version of such a plugin in that ticket, but it requres a separate ticket to extend and review that plugin and find the right place where it should live.
My suggestionh would be not to deliver it with the server during installation but have it as part of the test environment.
fail.c

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.4.1

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4 (was: 1.4.1)

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

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
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.