Ask Your Question

Deleting broken ovs tunnels [closed]

asked 2014-03-04 14:32:56 -0500

ssosothi gravatar image

Hello, I've been fixing my ovs_neutron_plugin.ini and now I have a couple of broken gre-* tunnels under my br-tun bridge.

I would like to delete these entries as these still causes ovs to output logs which distracts me from continuing my fix.

I've tried ovs-vsctl del-port gre-1 on both my network and compute node, however, the tunnels still return after a reboot.

Thank you for your help

Here's my current list of tunnels on my compute node

root@gold:~# ovs-vsctl show
    Bridge br-tun
        Port "gre-2"
            Interface "gre-2"
                type: gre
                options: {in_key=flow, local_ip="", out_key=flow,}
        Port br-tun
            Interface br-tun
                type: internal
        Port "gre-1"
            Interface "gre-1"
                type: gre
                options: {in_key=flow, local_ip="", out_key=flow,}
        Port "gre-4"
            Interface "gre-4"
                type: gre
                options: {in_key=flow, local_ip="", out_key=flow, remote_ip=""}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge "br-eth0"
        Port "phy-br-eth0"
            Interface "phy-br-eth0"
        Port "eth1"
            Interface "eth1"
        Port "br-eth0"
            Interface "br-eth0"
                type: internal
    Bridge br-int
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-eth0"
            Interface "int-br-eth0"
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap20420387-0d"
            tag: 1
            Interface "tap20420387-0d"
    ovs_version: "1.10.2"

And here's a tunnel I want to delete

root@gold:~# ovs-vsctl list Interface "gre-1"
_uuid               : 2b5b55e9-d41c-437d-9e46-bab24a735e3a
admin_state         : []
cfm_fault           : []
cfm_fault_status    : []
cfm_health          : []
cfm_mpid            : []
cfm_remote_mpids    : []
cfm_remote_opstate  : []
duplex              : []
external_ids        : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
lacp_current        : []
link_resets         : []
link_speed          : []
link_state          : []
mac                 : []
mac_in_use          : []
mtu                 : []
name                : "gre-1"
ofport              : -1
ofport_request      : []
options             : {in_key=flow, local_ip="", out_key=flow,}
other_config        : {}
statistics          : {}
status              : {}
type                : gre
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by ssosothi
close date 2014-03-04 21:15:12.491911

2 answers

Sort by ยป oldest newest most voted

answered 2014-03-04 16:14:46 -0500

darragh-oreilly gravatar image

I'm afraid your only option at this time is to manually remove the offending rows from the neutron database. I think the table name is ovs_tunnel_endpoints when using the OVS plugin. Then the agents will need to be restarted.

edit flag offensive delete link more

answered 2014-03-04 21:14:39 -0500

ssosothi gravatar image

Thank you, that worked perfectly. I just had to run `DELETE FROM ovs_tunnel_endpoints WHERE id=1` in the neutron database.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2014-03-04 14:32:56 -0500

Seen: 1,825 times

Last updated: Mar 04 '14