Re: [openstack-dev] [Neutron]The components timing problem

2018-01-23 Thread Frank Wang
Hi, Yeah, rabbitmq server on the same host. rabbitmq service was stopped a little while to try to reproduce a problem. Do you mean report_state always running even the rabbitmq connection is down? It sounds unreasonable. Thanks, Frank At 2018-01-23 17:58:58, "Sławomir Kapłoński"

Re: [openstack-dev] [Neutron]The components timing problem

2018-01-23 Thread Sławomir Kapłoński
Hi, Problem which You have here is that Your agent can't connect to rabbitmq. Because of that rpc message with report_state is timeouted and that is the reason of this error. Is Your rabbitmq server on same host with ovs agent? Is rabbitmq server works properly? — Best regards Slawek

Re: [openstack-dev] [Neutron]The components timing problem

2018-01-23 Thread Frank Wang
Hi Sławomir, Thanks for you quick response. I'm using Ocata, Here is the exception stack. e: [Errno 111] ECONNREFUSED. Trying again in 14 seconds. Client port: None 2018-01-23 17:37:45.387 8636 ERROR oslo.messaging._drivers.impl_rabbit [-] [7b611083-b03c-4aaa-bb2f-a8f6cb89ab15] AMQP

Re: [openstack-dev] [Neutron]The components timing problem

2018-01-23 Thread Sławomir Kapłoński
Hi, If both ovs agent and neutron-server reconnect to rabbitmq then it should report state properly again IMO. Can You maybe send more details about Your issue? What OpenStack version You are running, exact stack trace of exception which You get and so on. — Best regards Slawek Kaplonski

[openstack-dev] [Neutron]The components timing problem

2018-01-23 Thread Frank Wang
Hi All, I'm really newbie about OpenStack Neutron, Please correct me if I say something wrong. There was a question I'd like to consult. AMQP is the messaging bus between neutron-server and *agents. we usually use rabbitmq as the back-end of messaging bus. The problem I encountered is