From 8c95131d81c1b12adb7e0fd758bc236017d20db7 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Wed, 20 Jul 2022 07:23:59 -0700 Subject: [PATCH] CI: Save routing table information for troubleshooting Presently, we don't save the state of the routing table, which means troubleshooting the ipv6 job failures is difficult because we just have no way of knowing what is truly going on with the traffic flow. Possibly, we may be encountering a case where router advertisements are overrriding route table entries, and the only way to know is to see the final state of the table. Change-Id: Ib15cd21e47e3b884bae2cb956f9113e73034391b --- playbooks/ci-workarounds/get_extra_logging.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/playbooks/ci-workarounds/get_extra_logging.yaml b/playbooks/ci-workarounds/get_extra_logging.yaml index 29454585ad..3e9115fae9 100644 --- a/playbooks/ci-workarounds/get_extra_logging.yaml +++ b/playbooks/ci-workarounds/get_extra_logging.yaml @@ -6,3 +6,11 @@ - name: Get network connection information for ironic process shell: "netstat -apn > {{ zuul_output_dir }}/logs/post-job-network-connections.txt" become: yes + - name: Get routing table, IPv4 + shell: "ip -4 route > {{ zuul_output_dir }}/logs/post-job-network-routes-v4.txt" + ignore_errors: True + become: yes + - name: Get routing table, IPv6 + shell: "ip -6 route > {{ zuul_output_dir }}/logs/post-job-network-routes-v6.txt" + ignore_errors: True + become: yes