out.txt
[CONTROLLER-104] Controller does not start up properly when it is used in a specific sequence with mininet Created: 21/Dec/13 Updated: 25/Jul/23 Resolved: 09/Jan/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
out.txt
|
| External issue ID: | 257 |
| Description |
|
1. Start up the controller 2. From mininet populate a topology 3. Shut down the controller (Exit with Ctrl + C) 4. In mininet exit the CLI (thus tearing down the toplogy) 5. Start up the controller - you will see a bunch of exceptions - the controller will not be functional at this point (See attached file out.txt for the exceptions) |
| Comments |
| Comment by Moiz Raja [ 21/Dec/13 ] |
|
Attachment out.txt has been added with description: log |
| Comment by Tomas Olvecky [ 09/Jan/14 ] |
|
I believe this has been fixed. Please retest. |