mgr/cephadm: improving logging to send errors to stderr

[rkachach]

Adding logic to use a special logging configuration during bootstrap operation. Basically in this case we will use
a normal behavior:

• stdout: for debug and info
• stderr: for errors and warnings

During all other operations (when cephadm is called from the mgr) we will continue using the current configuration:

• stdout: for JSON output only
• stderr: for error, debug, info, etc

This way we don't break the current/default functionality and we improve the logging during the bootstrap operation following a normal behavior to handle debug/error messages that any Linux/Unix user may expect.

Fixes: https://tracker.ceph.com/issues/47905

Signed-off-by: Redouane Kachach rkachach@redhat.com

Related PRs:
#41216
#37712

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Component impact
  • Affects Dashboard, opened tracker ticket
  • Affects Orchestrator, opened tracker ticket
  • No impact that needs to be tracked
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includes unit test(s)
  • Includes integration test(s)
  • Includes bug reproducer
  • No tests

Show available Jenkins commands

• jenkins retest this please
• jenkins test classic perf
• jenkins test crimson perf
• jenkins test signed
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test dashboard cephadm
• jenkins test api
• jenkins test docs
• jenkins render docs
• jenkins test ceph-volume all
• jenkins test ceph-volume tox
• jenkins test windows

[sebastian-philipp]

Please refer to #41216 and #37712 and #38995

[rkachach]

Please refer to #41216 and #37712 and #38995

Do you mean add references to these PRs in the description of my PR?

[sebastian-philipp]

Please refer to #41216 and #37712 and #38995

Do you mean add references to these PRs in the description of my PR?

I'd read those linked PRs.

[rkachach]

Please refer to #41216 and #37712 and #38995

Do you mean add references to these PRs in the description of my PR?

I'd read those linked PRs.

I see, thanks for mentioning them. Before implementing my PR I have already read one of the PRs you referenced (#37712) so I was aware of the issues related with JSON output. My PR fixes are meant to fix the case of bootstrap without impacting the normal cephadm behavior (at least that's the intention behind the changes).

[rkachach]

jenkins test api

[adk3798]

jenkins test api

[adk3798]

Definitely completes the ask laid out in the tracker. One open question

[adk3798]

jenkins test api

[adk3798]

http://pulpito.front.sepia.ceph.com/adking-2022-04-08_22:17:12-orch:cephadm-wip-adk-testing-2022-04-08-1434-distro-basic-smithi/

2 failures:

• 1 caused by https://tracker.ceph.com/issues/49287
• workunits/cephadm/test_cephadm.sh failure caused by another PR in this run.