[OVSDB-355] Regression in Connection reconciliation functionality Created: 29/Jul/16 Updated: 01/Aug/16 Resolved: 01/Aug/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.Open_vSwitch |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Vishnoi | Assignee: | Anil Vishnoi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6304 |
| Description |
|
Connection reconciliation does not trigger when user connects to the switch through controller and then switch disconnects from the controller. After enabling the checkstyle, we started catching the specific exceptions rather than all the exceptions through Exception. During retry, connection task encounter ConnectionException, but caller method does not catches that exception and it kills the reconciliation thread, so it does not retry the connection after first |
| Comments |
| Comment by A H [ 29/Jul/16 ] |
|
A patch for this bug was submitted: https://git.opendaylight.org/gerrit/#/c/42756/ To better assess the impact of this bug and fix, could someone from your team please help us identify the following: Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note and fix in future Beryllium SR4? |
| Comment by A H [ 01/Aug/16 ] |
|
Have we verified if the bug has been fixed in the latest build for Beryllium SR3? |
| Comment by Anil Vishnoi [ 01/Aug/16 ] |
|
stable/beryllium : https://git.opendaylight.org/gerrit/42756 |