5531e8bbbc
Undercloud deployment starts logging into its log file too late, omitting log records from undercloud_config, preflight checks. This is a problem as we want to log at least the commands used for undercloud install/upgrade. Ideally, messages in stdout/stderr should not miss the log file. Fix this via the added custom undercloud_log_file config (use --log-file for standalone CLI). Use those to configure logging to a file. Fix missing formatting, like timestamps and source, for undercloud config and preflight checks. Write preflight/install/upgrade logs into the same logfile. Move the load oslo config method into shared utilities. Add the configure logging shared utility for the classless modules (w/o oslo_log supported). Such modules can mimic oslo_log behavior defined for the main deployment modules derived from openstack client classes, which support logging to files natively and are not affected by the subject issue. With an exception made for those classless modules allowing them to log INFO+ be default. So operators will have the pre-flight check notes logged, for example. Change-Id: I340be11bc9471df22f038629679634c3542d34d6 Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
12 lines
461 B
YAML
12 lines
461 B
YAML
---
|
|
security:
|
|
- |
|
|
Undercloud and tripleo standalone deployments support logging
|
|
into a log file. In ``undercloud.conf`` the log file path may be
|
|
defined via `undercloud_log_file`. For the standalone
|
|
deployments, use the ``--log-file`` commmand line argument.
|
|
|
|
By default, undercloud pre-flight/installation/upgrade logs
|
|
will be written into ``install-undercloud.log`` in the current dir
|
|
(wherefrom the client command is executed).
|