[NETCONF-133] "Transaction ... is no longer running" after user sends invalid data. Created: 26/Jan/16 Updated: 15/Mar/19 Resolved: 12/Feb/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Andrej Mak |
| 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: | 5096 |
| Description |
|
Tested on: stable/beryllium After user sends invalid data to the "modules" node of ODL's NETCONF configutation and after that request errors out (uncleanly, see <?xml version="1.0" encoding="UTF-8" standalone="no"?> (the "DOM-31" in the <error> element can vary). |
| Comments |
| Comment by Ryan Goulding [ 02/Feb/16 ] |
|
Is this still present? |
| Comment by Jozef Behran [ 03/Feb/16 ] |
|
The "invalid data" are for example the following file in Gerrit: It contains a complete request which, when sent to ODL, will trigger the bug. The bug is still there as of today. A Sandbox test run just finished on build 3866 and the bug can still be seen there. |
| Comment by Ryan Goulding [ 03/Feb/16 ] |
|
Is the workaround just to start a new session? I ask since this sounds pretty bad, but I am not sure if its the type of thing we should raise to a critical/blocker level. Thanks for your feedback, Jozef. |
| Comment by Tomas Cere [ 03/Feb/16 ] |
|
New session should fix it, the problem is that the failure of the commit is not correctly handled. |
| Comment by Andrej Mak [ 04/Feb/16 ] |