[OVSDB-449] ODL requires restart for OVSDB to allow new SSL connections Created: 06/Feb/18 Updated: 02/Apr/18 Resolved: 25/Mar/18 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | None |
| Affects Version/s: | Oxygen, Fluorine |
| Fix Version/s: | Oxygen-SR1, Fluorine |
| Type: | Bug | Priority: | Highest |
| Reporter: | Tim Rozet | Assignee: | Tim Rozet |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Description |
|
This environment is using SSL configuration for OVSDB. OpenDaylight is already up and configured to use SSL for OVSDB in this scenario. Each OVS node is configured with private key, cert, and CA cert. A rest call is then issued to add the OVS cert into the ODL trust store. After that, OVS manager is set with ssl prefix to connect to ODL. The result is I can see connections being initiated from OVS and ODL receiving traffic, however ODL never accepts the connection, unless rebooted. After reboot, everything works as expected. We should not need to reboot to connect a new switch. |
| Comments |
| Comment by Tim Rozet [ 06/Feb/18 ] |
|
Added karaf log which shows the problem, as well as reboot, and then OVSDB connects and OF manager gets set. |
| Comment by Sam Hague [ 02/Apr/18 ] |