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
plugopts from config file not mentioned in "effective options" debug log #2663
Comments
|
I apologize for confusion - the bug is in not printing plugin options only, the above example shows a correct behaviour. Proper reproducer: (same happens when updating the default |
|
Two findings:
This can be solved by using
|
|
|
Ah, ok - looks like I had a separate change in my local branch that actually resolved it. If in That being said, I don't think this is really the best fix for this on its face, but I am struggling to find a better approach. |
|
Hmm.. that ignores cmdline options: try in your case " |
First, provide a special-case handling for plugin options specified in sos.conf in `SoSOptions.to_args().has_value()` that allows for plugin options to be included in the "effective options now" log message. Second, move the logging of said message (and thus the merging of preset options, if used), to being _prior_ to the loading of plugin options. Combined, plugin options specified in sos.conf will now be logged properly and this logging will occur before we set (and log the setting of) those options. Resolves: sosreport#2663 Signed-off-by: Jake Hunsaker <jhunsake@redhat.com>
First, provide a special-case handling for plugin options specified in sos.conf in `SoSOptions.to_args().has_value()` that allows for plugin options to be included in the "effective options now" log message. Second, move the logging of said message (and thus the merging of preset options, if used), to being _prior_ to the loading of plugin options. Combined, plugin options specified in sos.conf will now be logged properly and this logging will occur before we set (and log the setting of) those options. Resolves: sosreport#2663 Signed-off-by: Jake Hunsaker <jhunsake@redhat.com>
Currently, sos report prints a debug:
before the config file is evaluated. We dont know what particular options were really used at the end.
Shall not we (maybe rename the "effective"? and ..) add a debug similar to above that will print options after all options processing is done, incl. config file?
Reproducer:
(or have the default
/etc/sos/sos.confof the same content)The text was updated successfully, but these errors were encountered: