-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to healthcheck to list all the lint reports #3801
Comments
Comment from mhonek (@kenoh) at 2019-12-03 14:46:19 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. |
Comment from mhonek (@kenoh) at 2019-12-03 14:46:20 Metadata Update from @kenoh:
|
Comment from mreynolds (@mreynolds389) at 2020-02-12 16:27:02 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-03-24 22:43:46 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-04-06 16:06:24 |
Comment from mhonek (@kenoh) at 2020-06-02 16:26:24 Commit 4a55322c fixes this issue |
Comment from mhonek (@kenoh) at 2020-06-02 17:18:50 Metadata Update from @kenoh:
|
Comment from spichugi (@droideck) at 2020-07-28 15:11:16 Commit 4610b5f6 relates to this ticket |
Description: Backport changes for healthcheck issues to branch 1.4.3 for healthcheck files only, fix print list_checks to log in lib389 and minor change to tests for dsidm and healthcheck to prevent failing. Relates: 389ds#3926 Relates: 389ds#3894 Relates: 389ds#3894 Relates: 389ds#3801 Relates: 389ds#4144 Relates: 389ds#4159 Reviewed by: mreynolds389, Firstyear, droideck, vashirov (Thanks!)
Description: Backport changes for healthcheck issues to branch 1.4.3 for healthcheck files only, fix print list_checks to log in lib389 and minor change to tests for dsidm and healthcheck to prevent failing. Relates: #3926 Relates: #3894 Relates: #3894 Relates: #3801 Relates: #4144 Relates: #4159 Reviewed by: mreynolds389, Firstyear, droideck, vashirov (Thanks!)
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50746
Issue Description
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.
The text was updated successfully, but these errors were encountered: