b1d226a158
With the release of Jaeger 1.59.0 we started getting errors in the quickstart job due to a lack of tracing data in Jaeger. Without logs for the jaeger service it is hard to say why this is happening. Collect those logs so that we can debug further. Change-Id: Ifedf063612622bbe3bd0faee79042617e2498a14
29 lines
1.4 KiB
YAML
29 lines
1.4 KiB
YAML
- hosts: all
|
|
tasks:
|
|
- name: Create logs directory
|
|
file:
|
|
state: directory
|
|
path: "{{ ansible_user_dir }}/logs"
|
|
mode: 0755
|
|
- name: Save podman log files
|
|
shell: |
|
|
set +e
|
|
podman logs zuul-tutorial_gerrit_1 > {{ ansible_user_dir }}/logs/gerrit.log 2>&1
|
|
podman logs zuul-tutorial_gerritconfig_1 > {{ ansible_user_dir }}/logs/gerritconfig.log 2>&1
|
|
podman logs zuul-tutorial_zk_1 > {{ ansible_user_dir }}/logs/zk.log 2>&1
|
|
podman logs zuul-tutorial_mysql_1 > {{ ansible_user_dir }}/logs/mysql.log 2>&1
|
|
podman logs zuul-tutorial_scheduler_1 > {{ ansible_user_dir }}/logs/scheduler.log 2>&1
|
|
podman logs zuul-tutorial_web_1 > {{ ansible_user_dir }}/logs/web.log 2>&1
|
|
podman logs zuul-tutorial_executor_1 > {{ ansible_user_dir }}/logs/executor.log 2>&1
|
|
podman logs zuul-tutorial_node_1 > {{ ansible_user_dir }}/logs/node.log 2>&1
|
|
podman logs zuul-tutorial_launcher_1 > {{ ansible_user_dir }}/logs/launcher.log 2>&1
|
|
podman logs zuul-tutorial_logs_1 > {{ ansible_user_dir }}/logs/logs.log 2>&1
|
|
podman logs zuul-tutorial-tracing_jaeger_1 > {{ ansible_user_dir }}/logs/jaeger.log 2>&1
|
|
exit 0
|
|
- name: Copy podman log files to executor
|
|
synchronize:
|
|
mode: pull
|
|
src: "{{ ansible_user_dir }}/logs/"
|
|
dest: "{{ zuul.executor.log_root }}/container_logs/"
|
|
verify_host: true
|