It would be nice if the healthcheck tool could list all the possible errors it reports on.
It would also be nice to have an option to pick which component to health check (instead of checking all areas). Like, just check replication, or config, or backends, or plugins, etc.
PoC patch that adds listing of checks. Uses lazy object proxy to cease from unnecessary allocation of the instance in case someone wants to just check the listing regardless the instance being real or not. <img alt="886a8d75fe1bb8519a5f72925c0b3c3d8e0d1f16.patch" src="/389-ds-base/issue/raw/files/56bbd0733be5cbbedf3a095adc2838019815cf56ea4364db889c02f2748019f5-886a8d75fe1bb8519a5f72925c0b3c3d8e0d1f16.patch" />
Metadata Update from @mhonek: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue priority set to: major - Issue set to the milestone: 1.4.1 (was: 1.4.0)
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1816851
https://pagure.io/389-ds-base/pull-request/50987
Commit 4a55322 fixes this issue
b3315a5..66cd2a9 389-ds-base-1.4.3 -> 389-ds-base-1.4.3 db11e8e..08eed33 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
Metadata Update from @mhonek: - Issue close_status updated to: None (was: Fixed)
Commit 4610b5f relates to this ticket
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/3801
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
Log in to comment on this ticket.