Nate Johnston efc04eec00 Look for ipv6 routes so ipv6-only jobs will not fail ... For change 739139 [1] PS 12, the neutron-tempest-plugin-scenario-linuxbridge died in devstack with "/opt/stack/devstack/functions-common:237 Failure retrieving default route device", which comes from "/opt/stack/devstack/lib/neutron-legacy:237:die_if_not_set". Looking at the worlddump.txt for that job [2] I see that there is a default ipv6 route; the vm was not configured with ipv4 networking. ip route -------- ip -6 route ----------- ::1 dev lo proto kernel metric 256 pref medium 2607:ff68:100:54::/64 dev ens3 proto kernel metric 256 expires 86380sec pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium default via fe80::f816:3eff:fe77:b05c dev ens3 proto ra metric 1024 expires 280sec hoplimit 64 pref medium Looking at the devstack code that throws the error [3] it looks like it only looks for a default route in the output of `ip route`, which does not include ipv6 information. This change should look in both the ipv4 and ipv6 route table. A similar check in the L3 setup code is also updated. [1] https://review.opendev.org/#/c/739139/ [2] https://d4eb7e3efe98cba79a4b-f4d168cdb20f40841821e4b213645c0f.ssl.cf2.rackcdn.com/739139/12/gate/neutron-tempest-plugin-scenario-linuxbridge/9a6b4f7/controller/logs/worlddump-latest.txt [3] https://opendev.org/openstack/devstack/src/branch/master/lib/neutron-legacy#L236 Closes-Bug: #1902002 Change-Id: I839e8c222368df98fec308cf41248a9dd0a8c187		2020-11-09 17:05:38 -05:00
..
l3	Look for ipv6 routes so ipv6-only jobs will not fail	2020-11-09 17:05:38 -05:00
metering	Neutron: Use generated configuration files if available	2015-11-30 16:44:18 +00:00