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
PR - Issue 49640 - Cleanup plugin bootstrap logging #2881
Comments
Comment from spichugi (@droideck) at 2018-07-03 08:21:56 rebased onto 7ecfefe478266fae0fb6dd792342a2df50a5597f |
Comment from mreynolds (@mreynolds389) at 2018-07-10 16:55:55 Is this logging line redundant from what you did in plugin.c? |
Comment from spichugi (@droideck) at 2018-07-10 17:05:33
I was thinking that it can potentially help with the debugging. But we use TRACE log level rarely because it's really noisy... So if you think it is too much redundant, I'll remove it. |
Comment from mreynolds (@mreynolds389) at 2018-07-10 17:08:33 Good point, ack |
Comment from spichugi (@droideck) at 2018-07-10 17:19:13 rebased onto 2fa0408 |
Comment from spichugi (@droideck) at 2018-07-10 17:20:13 Pull-Request has been merged by droideck |
Patch |
Cloned from Pagure Pull-Request: https://pagure.io/389-ds-base/pull-request/49822
Bug Description: We add PBKDF2_SHA256 password storage schema two times. During:
It causes the error to appear during the startup.
Fix Description: Make plugin_setup() function report the error to TRACE log level
if the plugin already exists. We will report the error in ERR log level during
the config bootstrap anyway (code path for the 1st option from bug description).
For 2nd option, report the error to TRACE if it is 'already exist' issue
and to ERR if it is any other case.
Make the plugin_setup returns more consistent.
Resolves: #2699
Reviewed by: ?
The text was updated successfully, but these errors were encountered: