Flows can't generate when restarted ovs-agent

[changzhi]

I deleted ovs bridge named 'br-int' by 'ovs-vsctl del-br br-int'. Then I restart ovs-agent. Bridge 'br-int' was created by ovs-agent. But flows can't generate by ovs-agent.

When I execute 'ovs-vsctl show', this is output:

[root@server-233 ~]# ovs-vsctl show
7b1afcdf-e1ca-4917-b97b-a53103b44dc3
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-int
        fail_mode: secure
        Port "tap1c3f7bf4-46"
            Interface "tap1c3f7bf4-46"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "int-ovsbr3"
            Interface "int-ovsbr3"
                type: patch
                options: {peer=nonexistent-peer}
    Bridge "ovsbr3"
        Port "phy-ovsbr3"
            Interface "phy-ovsbr3"
                type: patch
                options: {peer=nonexistent-peer}
        Port "ovsbr3"
            Interface "ovsbr3"
                type: internal
    Bridge br-tun
        fail_mode: secure
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-e84ab4c4-1a"
            Interface "qg-e84ab4c4-1a"
                type: internal
        Port "fg-17319993-76"
            Interface "fg-17319993-76"
                type: internal
        Port "p3p1.102"
            Interface "p3p1.102"
    ovs_version: "2.4.0"

[changzhi (changzhi)]

The ovs-agent log file output these content:

2016-05-21 23:04:57.114 129458 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor Interface name,ofport,external_ids --format=json]: None
2016-05-21 23:04:57.115 129458 ERROR neutron.agent.linux.async_process [-] Process [ovsdb-client monitor Interface name,ofport,external_ids --format=json] dies due to the error: None

[Hirofumi Ichihara (ichihara-hirofumi)]

What neutron version?

[changzhi (changzhi)]

stable Liberty

In my opinion, we should restart all Neutron agents such dhcp-agent, l3-agent, etc if someone deleted any ovs bridge. Right?

[Hirofumi Ichihara (ichihara-hirofumi)]

I tested the issue but I cannot reproduce it. Can you reproduce it with master?

[changzhi (changzhi)]

Thanks for your reply. ;-)

I think that there may be two questions.

1. Patch port can not be created when restarted ovs agent. And I find the same bug just like me at this bug report: https://bugs.launchpad.net/neutron/+bug/1528894. I follow this patch link and I have solved this problem. ;-)

2. I deleted any ovs bridge, just like this command "ovs-vsctl del-br br-int". Then I restarted ovs agent. All ports attached br-int were gone and all flows are gone. So I restart the "l3 agent", "dhcp agent", etc. All ports(such as tap-xxx, qr-xxx) can attached br-int before can reattached to the br-int again. But qvo devices can not go back any more. Only I can do is to migrate all vms in this compute node.

So my question is, what should we do if anyone deletes any ovs bridge? Do we have to restart all agents and migrate all vms in this node? Is there any friendly method?

Thanks ;-)

[changzhi (changzhi)]

Oh, flows in the br-int locate http://paste.openstack.org/show/498020/ when I restart all agents in this node. ;-)

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]

[shihanzhang (shihanzhang)]

@changzhi, maybe you use ovs native interface for ovs-agent, but don't install python-ryu

[Sam (samuelbenas)]

I am experiencing the same problem after a hardware router failure required a restart of network services on a neutron/compute node. The other compute nodes are fine. /var/log/neutron/openvswitch-agent.log contains:

2016-11-17 08:46:15.253 81290 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor Interface name,ofport,external_ids --format=json]: None
2016-11-17 08:46:15.255 81290 ERROR neutron.agent.linux.async_process [-] Process [ovsdb-client monitor Interface name,ofport,external_ids --format=json] dies due to the error: None