karaf_log.txt
[GBP-198] Invalid tunnel destination for NodeID : null Created: 15/Oct/15 Updated: 19/Oct/17 Resolved: 06/Jul/16 |
|
| Status: | Resolved |
| Project: | groupbasedpolicy |
| Component/s: | Renderer:OfOverlay |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tomas Cechvala | 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: |
karaf_log.txt
|
| External issue ID: | 4479 |
| Description |
|
Happens occasionally when running GBPSFC symm/asymm demo. PolicyEnforcer cannot read next-hop destination (see log in the attachment). REST data are sent to ODL one by one. Some of the processes which were triggered by data change event may take so long, that they don't finish before different process is triggered. In this case rendered-service-path had not been created by SFC plugin before PolicyEnforcer was looking it. |
| Comments |
| Comment by Tomas Cechvala [ 15/Oct/15 ] |
|
Attachment karaf_log.txt has been added with description: Default log level |
| Comment by Tomas Cechvala [ 06/Jul/16 ] |
|
This was fixed in demos by waiting for ovsdb-connection with SFFs. |