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
If this grep doesn't match, the task returns a failure and it causes
the job to abort with POST_FAILURE. I think more info is generally
helpful and you can always grep "netstat" on the file manually; thus
remove the grep to avoid suprious failure.
Change-Id: I189a0a8be25cb12e946d8ac58667b287f9698064
A recent magnum bug (https://storyboard.openstack.org/#!/story/2008494)
when running with uwsgi has yielded an interesting question if Ironic
is orphaning rpc clients or not. Ironic's code is slightly different
but also very similar, and similar bugs have been observed in the past
where the python garbage collection never cleans up the old connection
objects and effectively orphans the connection.
So we should likely at least try to collect some of the information
so we can determine if this is the case in our CI jobs. Hence this
change and attempt to collect that data after running CI.
Change-Id: I4e80c56449c0b3d07b160ae6c933a7a16c63c5c5
This patch adds a post run playbook that collects info about the
tftpd daemon from journald to be available at the end of the
CI process.
Change-Id: I1dd11a8804b976e3abc42a43102c1b52fbe03f5a
The multinode jobs are failing because the br-infra bridge
is not being setup. It is not being setup because somewhere
in the infra, the multi-node-bridge role is never established
as a requirement. Realistically, only ironic does this, but
we need to ensure it is present.
Change-Id: Ia1dcc68d7e75a931e01829ce23da36c978a70765