openstack/ironic
Code Issues Proposed changes

CI: Save routing table information for troubleshooting

Browse Source 
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
This commit is contained in:
Julia Kreger 2022-07-20 07:23:59 -07:00
parent 565e3c4bff
commit 8c95131d81
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
playbooks/ci-workarounds/get_extra_logging.yaml
View File

@ -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