summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJulia Kreger <juliaashleykreger@gmail.com>2022-07-20 07:23:59 -0700
committerJulia Kreger <juliaashleykreger@gmail.com>2022-07-20 11:02:39 -0700
commit8c95131d81c1b12adb7e0fd758bc236017d20db7 (patch)
tree5a0823116832db54306d4355183becab80890981
parent565e3c4bffc6dbda8602316590de9b19183bbcd6 (diff)
downloadironic-8c95131d81c1b12adb7e0fd758bc236017d20db7.tar.gz
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
-rw-r--r--playbooks/ci-workarounds/get_extra_logging.yaml8
1 files changed, 8 insertions, 0 deletions
diff --git a/playbooks/ci-workarounds/get_extra_logging.yaml b/playbooks/ci-workarounds/get_extra_logging.yaml
index 29454585a..3e9115fae 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