389-ds-base

#50806 Fix minor bugs in lib389 health checks
Closed: wontfix by mreynolds. Opened by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

For example, we currently check for file permissions 600 for the pin.txt, but IPA resets this to 400 which is fine, but we report this an error. In this case we need to check for 600 or "more restrictive", instead of hardcoding an exact permission level.

RI plugin checks do not take into account the plugin container scope

https://pagure.io/389-ds-base/pull-request/50807

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

New PR. This also addresses issue with RI plugin check and container scope.

https://pagure.io/389-ds-base/pull-request/50810

Metadata Update from @mreynolds:
- Issue tagged with: lib389

Commit caca64e7 relates to this ticket

Commit caca64e relates to this ticket

824abb843..02fdfa713 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

99772c9d6..903a41f22 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

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

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)
Metadata

lib389

None
None
None
None
None
Related Pull Requests
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.