Open Stack

Hi Eren,

I created it using ovs-vsctl,

I have recreated the entire networks and then still could not see the br-x
and br-int  )when I do ifconfig.

when i do ifconifg -a i do see them.

below is what I see

 ovs-vsctl show
89744d4a-f9e5-4fe1-b35e-81af9aaa0bac
    Bridge br-int
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port "tap1f2ed78e-f1"
            tag: 4095
            Interface "tap1f2ed78e-f1"
                type: internal
        Port "gw-cea73d4a-1c"
            tag: 4095
            Interface "gw-cea73d4a-1c"
                type: internal
        Port "tapbedd14b9-c1"
            tag: 4095
            Interface "tapbedd14b9-c1"
                type: internal
        Port "qr-58d11b25-de"
            tag: 4095
            Interface "qr-58d11b25-de"
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "vlan410"
            Interface "vlan410"
        Port "qg-c57b4514-3e"
            Interface "qg-c57b4514-3e"
                type: internal
    ovs_version: "2.1.3"


I seee the br-int and br-ex in the ifconfig -a the state is down ( no ip
for them)

the l3-agent log says below:

2015-06-17 14:27:31.966 24566 ERROR neutron.agent.l3_agent
[req-97b56678-b1e8-4de7-a838-86ebbe240ae8 None] Failed synchronizing
routers due to RPC error
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent Traceback (most
recent call last):
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent   File
"/usr/lib/python2.7/site-packages/neutron/agent/l3_agent.py", line 865, in
_sync_routers_task
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent     context,
router_ids)
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent   File
"/usr/lib/python2.7/site-packages/neutron/agent/l3_agent.py", line 76, in
get_routers
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent
topic=self.topic)
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent   File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/proxy.py",
line 129, in call
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent     exc.info,
real_topic, msg.get('method'))
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent Timeout: Timeout
while waiting on RPC response - topic: "q-l3-plugin", RPC method:
"sync_routers" info: "<unknown>"
2015-06-17 14:27:31.966 24566 TRACE neutron.agent.l3_agent
2015-06-17 14:27:31.967 24566 WARNING neutron.openstack.common.loopingcall
[req-97b56678-b1e8-4de7-a838-86ebbe240ae8 None] task run outlasted interval
by 58.01159 sec
2015-06-17 14:27:31.968 24566 WARNING neutron.openstack.common.loopingcall
[req-97b56678-b1e8-4de7-a838-86ebbe240ae8 None] task run outlasted interval
by 20.012439 sec
2015-06-17 14:28:08.075 24566 INFO neutron.openstack.common.service
[req-97b56678-b1e8-4de7-a838-86ebbe240ae8 None] Caught SIGTERM, exiting
2015-06-17 14:28:08.833 25336 INFO neutron.common.config [-] Logging
enabled!
2015-06-17 14:28:08.914 25336 INFO neutron.openstack.common.rpc.impl_qpid
[req-7208d75e-f246-4932-9bf3-208e70c4c38f None] Connected to AMQP server on
10.0.0.125:5672
2015-06-17 14:28:08.916 25336 INFO neutron.openstack.common.rpc.impl_qpid
[req-7208d75e-f246-4932-9bf3-208e70c4c38f None] Connected to AMQP server on
10.0.0.125:5672
2015-06-17 14:28:08.939 25336 INFO neutron.openstack.common.rpc.impl_qpid
[req-7208d75e-f246-4932-9bf3-208e70c4c38f None] Connected to AMQP server on
10.0.0.125:5672
2015-06-17 14:28:08.943 25336 INFO neutron.agent.l3_agent
[req-7208d75e-f246-4932-9bf3-208e70c4c38f None] L3 agent started
2015-06-17 14:28:14.669 25336 INFO neutron.agent.linux.interface
[req-7208d75e-f246-4932-9bf3-208e70c4c38f None] Device qg-c57b4514-3e
already exists
2015-06-17 14:28:15.374 25336 WARNING neutron.openstack.common.loopingcall
[req-7208d75e-f246-4932-9bf3-208e70c4c38f None] task run outlasted interval
by 0.523636 sec


No error in neutron log:


Nova log says


2015-06-17 14:47:03.014 25349 ERROR nova.compute.manager
[req-6b58be6c-2d97-4f91-b50c-5f64634f7e22 4ca4e46cf5564ce5b158bf2eef161618
6341291002db49b8ae6baa6e6c6455f3] [instance:
e7def19a-5d8e-439b-b68e-0d883c66f96a] Error: Unexpected
vif_type=binding_failed


can somebody suggest ?


Thanks,
Dev










On Wed, Jun 17, 2015 at 2:56 AM, Eren Türkay <erent at skyatlas.com> wrote:

> On 17-06-2015 02:08, pra devOPS wrote:
> > Stderr: 'ovs-ofctl: br-int is not a bridge or a socket\n'
>
> I think this error is clear. br-int seems to be created in a wrong way.
> How did
> you create this interface?
>
> --
> Eren Türkay, System Administrator
> https://skyatlas.com/ | +90 850 885 0357
>
> Yildiz Teknik Universitesi Davutpasa Kampusu
> Teknopark Bolgesi, D2 Blok No:107
> Esenler, Istanbul Pk.34220
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150617/ff976dd9/attachment.html>