On 11/17/2016 03:14 AM, zhi wrote:
Hi, all

I build a devstack which code from master branch. By default the OVS version is
2.0.2 when install devstack. So I reinstall the OVS 2.6.0.

I meet an exception in OVS agent when all OVS services runs okay. Exception
shows below:

2016-11-17 15:47:29.175 ERROR neutron.agent.linux.utils
[req-2393c604-1938-4841-9ea9-8f691e6c2262 None None] Exit code: 1; Stdin:
hard_timeout=0,idle_timeout=0,priority=0,table=71,cookie=10671737546270118050,actions=drop;
Stdout: ; Stderr: ovs-ofctl: br-int is not a bridge or a socket

The error is saying br-int doesn't exist, and from your output below it doesn't. Try running:

# ovs-vsctl add-br br-int

-Brian


I want to know why OVS agent tells me these info. All the OVS services run okay.
I use " ovs-vsctl show " to ensure OVS services and the output is right.

The detailed output when excute " ovs-vsctl show ":

root@devstack:~/openvswitch-2.6.0# ovs-vsctl show
6e695086-6663-4fd0-b713-5a12605c92cb
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633 <http://127.0.0.1:6633>"
            is_connected: true
        fail_mode: secure
        Port br-ex
            Interface br-ex
                type: internal
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
... ...

I think that OVS runs okay.

Did I miss some configuration or something about neutron or OVS?


Hope for your reply. :-)


Thanks
Zhi Chang


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to