Ask Your Question
0

neutron-ovs-cleanup failure on juno rdo lacp bonded port

asked 2015-04-24 02:02:00 -0500

yee379 gravatar image

i'm getting an error with my rdo rerun after i created a lacp bond for my ovs-based compute nodes

my rdo/packstack config is:

CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan,flat,vlan
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan
CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS=openvswitch
CONFIG_NEUTRON_ML2_FLAT_NETWORKS=*
CONFIG_NEUTRON_ML2_VLAN_RANGES=vlannet:831:831,vlannet:1441:1441
CONFIG_NEUTRON_ML2_TUNNEL_ID_RANGES=
CONFIG_NEUTRON_ML2_VXLAN_GROUP=
CONFIG_NEUTRON_ML2_VNI_RANGES=60000:69999
CONFIG_NEUTRON_L2_AGENT=openvswitch
CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS=
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=vlannet:br-vlan
CONFIG_NEUTRON_OVS_BRIDGE_IFACES=
CONFIG_NEUTRON_OVS_TUNNEL_IF=
CONFIG_NEUTRON_OVS_VXLAN_UDP_PORT=4789

but when i run packstack, it complains about:

# systemctl status neutron-ovs-cleanup.service
neutron-ovs-cleanup.service - OpenStack Neutron Open vSwitch Cleanup Utility
   Loaded: loaded (/usr/lib/systemd/system/neutron-ovs-cleanup.service; enabled)
   Active: failed (Result: exit-code) since Thu 2015-04-23 23:48:04 PDT; 6min ago
  Process: 3359 ExecStart=/usr/bin/neutron-ovs-cleanup --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini --log-file /var/log/neutron/ovs-cleanup.log (code=exited, status=1/FAILURE)
 Main PID: 3359 (code=exited, status=1/FAILURE)

Apr 23 23:48:03 net-pool02 sudo[3370]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 get Inter...external_ids
Apr 23 23:48:03 net-pool02 sudo[3375]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 get Inter...-vlan ofport
Apr 23 23:48:03 net-pool02 sudo[3379]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 get Inter...external_ids
Apr 23 23:48:03 net-pool02 sudo[3382]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 get Inter...h-tun ofport
Apr 23 23:48:03 net-pool02 sudo[3385]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 list-ports br-ex
Apr 23 23:48:03 net-pool02 sudo[3388]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 get Inter...external_ids
Apr 23 23:48:04 net-pool02 ovs-vsctl[3390]: ovs|00001|vsctl|ERR|no row "bond0" in table Interface
Apr 23 23:48:04 net-pool02 systemd[1]: neutron-ovs-cleanup.service: main process exited, code=exited, status=1/FAILURE
Apr 23 23:48:04 net-pool02 systemd[1]: Failed to start OpenStack Neutron Open vSwitch Cleanup Utility.
Apr 23 23:48:04 net-pool02 systemd[1]: Unit neutron-ovs-cleanup.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

the /var/log/neutron/ovs-cleanup.log shows:

2015-04-23 01:13:28.303 28739 ERROR neutron.agent.linux.utils [-]
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=10', 'get', 'Interface', 'bond0', 'external_ids']
Exit code: 1
Stdout: ''
Stderr: 'ovs-vsctl: no row "bond0" in table Interface\n'
2015-04-23 01:13:28.304 28739 ERROR neutron.agent.linux.ovs_lib [-] Unable to execute ['ovs-vsctl', '--timeout=10', 'get', 'Interface', 'bond0', 'external_ids']. Exception:
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=10', 'get', 'Interface', 'bond0', 'external_ids']
Exit code: 1
Stdout: ''
Stderr: 'ovs-vsctl: no row "bond0" in table Interface\n'
2015-04-23 01:13:28.304 28739 CRITICAL neutron [-] RuntimeError:
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=10', 'get', 'Interface', 'bond0', 'external_ids']
Exit ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-04-24 10:58:41 -0500

jdexter gravatar image

It looks like you are doing the bonding from within OVS?

 Bridge br-ex
        Port "bond0"
            Interface "em1"
            Interface "em2"

Have you create the bond within the OS networking.

The way that I have had this work for me is to create the bond in network in the OS, then add the bond to the bridge mapping for for your provider.

So your packstack answer file would be

CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=vlannet:br-vlan CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-vlan:bond0

This would cause you to have the physical interface bond0 within br-vlan. Then OVS would handle creating the tagged connections being dumped on to the bond.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-04-24 02:02:00 -0500

Seen: 1,022 times

Last updated: Apr 24 '15