As the root reason for fty-core#343, fty-core#337, fty-core#331 and nearby fixes, the bios-csv export happens to print its tntnet-originated INFO, DEBUG and similar messages to stdout so they end up as the content of CSV file.
Initial fixes were to reduce the tool's logging level when collecting diagnostic data, so we do not have non-error messages there, but the correct fix would be to print the log lines to stderr and flush only CSV data to stdout. Not sure where the fix would be technically - in the tool, in fty-common-logging, in its config... but the result needs to be done.
As the root reason for fty-core#343, fty-core#337, fty-core#331 and nearby fixes, the
bios-csv exporthappens to print its tntnet-originated INFO, DEBUG and similar messages tostdoutso they end up as the content of CSV file.Initial fixes were to reduce the tool's logging level when collecting diagnostic data, so we do not have non-error messages there, but the correct fix would be to print the log lines to
stderrand flush only CSV data tostdout. Not sure where the fix would be technically - in the tool, in fty-common-logging, in its config... but the result needs to be done.