Not all tripleo ansible operator logs are captured in CI

[Bogdan Dobrelya]

For example tripleo_container_image_build_log seems missing in the captured CI logs [1]:

2020-10-23 16:55:30.543328 | primary | TASK [tripleo.operator.tripleo_container_image_build : Run tripleo container image build] ***
2020-10-23 16:55:30.543345 | primary | Friday 23 October 2020 16:55:30 +0000 (0:00:00.589) 0:15:31.387 ********
2020-10-23 18:38:11.883321 | primary | fatal: [undercloud]: FAILED! => {
2020-10-23 18:38:11.883369 | primary | "changed": false
2020-10-23 18:38:11.883378 | primary | }

but there is no logs provided

[1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_eda/759433/1/check/tripleo-ci-centos-8-content-provider-ussuri/edab0db/job-output.txt

The full list of log files default paths should be added to the collect-logs role:

 tripleo_container_image_build_log
 tripleo_container_image_prepare_log
 tripleo_deploy_log
 tripleo_overcloud_cell_export_log
 tripleo_overcloud_config_download_log
 tripleo_overcloud_container_image_build_log
 tripleo_overcloud_container_image_prepare_log
 tripleo_overcloud_container_image_tag_discover_log
 tripleo_overcloud_container_image_upload_log
 tripleo_overcloud_credentials_log
 tripleo_overcloud_delete_log
 tripleo_overcloud_deploy_log
 tripleo_overcloud_external_update_run_log
 tripleo_overcloud_external_upgrade_run_log
 tripleo_overcloud_ffwd_upgrade_converge_log
 tripleo_overcloud_ffwd_upgrade_prepare_log
 tripleo_overcloud_ffwd_upgrade_run_log
 tripleo_overcloud_generate_fencing_log
 tripleo_overcloud_image_build_log
 tripleo_overcloud_netenv_validate_log
 tripleo_overcloud_node_extract_provisioned_log
 tripleo_overcloud_node_import_log
 tripleo_overcloud_node_provide_log
 tripleo_overcloud_node_provision_log
 tripleo_overcloud_node_unprovision_log
 tripleo_overcloud_raid_create_log
 tripleo_overcloud_update_converge_log
 tripleo_overcloud_update_prepare_log
 tripleo_overcloud_update_run_log
 tripleo_overcloud_upgrade_converge_log
 tripleo_overcloud_upgrade_prepare_log
 tripleo_overcloud_upgrade_run_log
 tripleo_undercloud_backup_log
 tripleo_undercloud_install_log
 tripleo_undercloud_minion_install_log
 tripleo_undercloud_minion_upgrade_log
 tripleo_undercloud_upgrade_log

[Bogdan Dobrelya (bogdando)]

Note that there is a wildcard https://opendev.org/openstack/ansible-role-collect-logs/src/branch/master/defaults/main.yml#L91 that is expected to match for that log file, but it wasn't, see that has ended up being in https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_eda/759433/1/check/tripleo-ci-centos-8-content-provider-ussuri/edab0db/logs/undercloud/home/zuul/index.html

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/759663

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/759663
Committed: https://git.openstack.org/cgit/openstack/ansible-role-collect-logs/commit/?id=0025e656e7d8f944ec8bc2da7ab52b035256c2d9
Submitter: Zuul
Branch: master

commit 0025e656e7d8f944ec8bc2da7ab52b035256c2d9
Author: Bogdan Dobrelya <email address hidden>
Date: Mon Oct 26 12:03:43 2020 +0100

    Fix rsync mode filters to allow *.log files

    With the current defaults, there is no *.log files matching the
    templated rsync filter from the nested dirs. While the nested dirs
    itself are allowed to the filter, but have nothing matching because of
    that.

    Allow *.log files into that filter in order to collect logs properly.
    Additionally, exclude redundant or not much useful paths:
      - overlay*
      - root
      - console*primary.log
      - anaconda*
    since the former increases the size of collected logs by ~35M, while
    beeing mostly useless. And the others contain redundant things
    or junk.

    Depends-On: https://review.opendev.org/760335
    Change-Id: I3548e3b89c0654acca68c1dfe7a266172d3f2621
    Closes-bug: #1901508
    Signed-off-by: Bogdan Dobrelya <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ansible-role-collect-logs 1.2.0 release.