Files

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

services

Look for ipv6 routes so ipv6-only jobs will not fail

2020-11-09 17:05:38 -05:00

bigswitch_floodlight

fix a typo

2018-09-20 10:47:16 +08:00

brocade

Don't set external_network_bridge by default

2017-02-10 06:39:04 +00:00

cisco

Removed neutron_plugin_configure_debug_command functions

2017-02-10 06:39:04 +00:00

embrane

Namespace XTRACE commands

2015-11-27 15:36:04 +11:00

linuxbridge_agent

Remove bridge-utils/brctl usage

2020-04-30 10:09:47 +10:00

ml2

[OVN] Move OVN module from Neutron to DevStack

2020-08-11 15:47:01 +01:00

nuage

Stop configuring '[DEFAULT] firewall_driver' for nova

2020-01-16 09:27:54 +00:00

openvswitch

Namespace XTRACE commands

2015-11-27 15:36:04 +11:00

openvswitch_agent

Create OVS bridge even if OVS_BRIDGE_MAPPINGS is not empty

2019-12-18 08:09:11 +00:00

ovn_agent

Add possibility to not compile ovs and ovn if that's disabled

2020-09-21 12:59:16 +02:00

ovs_base

Revert "Revert "remove external_network_bridge option""

2019-02-27 14:57:22 +00:00

README.md

Removed neutron_plugin_configure_debug_command functions

2017-02-10 06:39:04 +00:00

README.md

Neutron plugin specific files

Neutron plugins require plugin specific behavior. The files under the directory, lib/neutron_plugins/, will be used when their service is enabled. Each plugin has lib/neutron_plugins/$Q_PLUGIN and define the following functions. Plugin specific configuration variables should be in this file.

filename: $Q_PLUGIN
- The corresponding file name MUST be the same to plugin name $Q_PLUGIN. Plugin specific configuration variables should be in this file.

functions

lib/neutron-legacy calls the following functions when the $Q_PLUGIN is enabled

neutron_plugin_create_nova_conf : optionally set options in nova_conf
neutron_plugin_install_agent_packages : install packages that is specific to plugin agent e.g. install_package bridge-utils
neutron_plugin_configure_common : set plugin-specific variables, Q_PLUGIN_CONF_PATH, Q_PLUGIN_CONF_FILENAME, Q_PLUGIN_CLASS
neutron_plugin_configure_dhcp_agent
neutron_plugin_configure_l3_agent
neutron_plugin_configure_plugin_agent
neutron_plugin_configure_service
neutron_plugin_setup_interface_driver
has_neutron_plugin_security_group: return 0 if the plugin support neutron security group otherwise return 1
neutron_plugin_check_adv_test_requirements: return 0 if requirements are satisfied otherwise return 1