clarkb noted in #openstack-infra that even though we see the WARN message "WARN: failed: route add -net "0.0.0.0/0" gw "10.1.0.1"" in the cirros console log, we also later see:
=== network info ===
if-info: lo,up,127.0.0.1,8,::1
if-info: eth0,up,10.1.0.13,28,fe80::f816:3eff:fe08:fa26
ip-route:default via 10.1.0.1 dev eth0
ip-route:10.1.0.0/28 dev eth0 src 10.1.0.13
ip-route:169.254.169.254 via 10.1.0.1 dev eth0
which seems to show the route was added.
I had been thinking the 100% failure rate with the WARN message meant that it's related, but it might not be because the cirros console log is only collected if a job fails. So even if the WARN message is often emitted on successful job runs, we wouldn't be able to see it in a logstash query.
clarkb noted in #openstack-infra that even though we see the WARN message "WARN: failed: route add -net "0.0.0.0/0" gw "10.1.0.1"" in the cirros console log, we also later see:
=== network info === 0.0.1,8, ::1 10.1.0. 13,28,fe80: :f816:3eff: fe08:fa26 10.1.0. 0/28 dev eth0 src 10.1.0.13 169.254. 169.254 via 10.1.0.1 dev eth0
if-info: lo,up,127.
if-info: eth0,up,
ip-route:default via 10.1.0.1 dev eth0
ip-route:
ip-route:
which seems to show the route was added.
I had been thinking the 100% failure rate with the WARN message meant that it's related, but it might not be because the cirros console log is only collected if a job fails. So even if the WARN message is often emitted on successful job runs, we wouldn't be able to see it in a logstash query.