Details
-
Bug
-
Status: Resolved
-
Medium
-
Resolution: Done
-
Carbon
-
None
-
None
-
Operating System: All
Platform: All
-
9147
-
Highest
Description
Our current deployment has three controllers, each with an odl instance and a neutron/n-odl instance. The neutron/n-odl instances connect to odl via a VIP. In the deployment we have all webwsocket connections are established against odl0 but the neutron port events that trigger the flow creation and set the operational port status to ACTIVE occur on odl2 which is the "leader". This means that the websocket event is generated on odl2 only...but no one is listening for websocket events on odl2...so the port never gets set to ACTIVE in neutron and the VM remains in BUILD state forever and ever.
---------------------------- --------------------------- ----------------------------
| --------------------- | --------------------- | --------------------- | ||||||||
| odl0 | odl1 | odl2 | ||||||||
| port created here | ||||||||||
| --------- |
--------------------- | --------------------- | ||||||||
| ^ | ||||||||||
| websocket--------------------------- |
||||||||||
| --------- |
--------- |
---------- |
||||||||
| neutron/n-odl | neutron/n-odl | neutron/n-odl | ||||||||
| --------------------- | --------------------- | --------------------- | ||||||||
---------------------------- --------------------------- ----------------------------
