log_see_lines_at_the_bottom.txt
[SFC-77] Failed to put OVSDB bridge and termination points into CONFIG data store Created: 06/Jul/15 Updated: 04/Aug/15 Resolved: 04/Aug/15 |
|
| Status: | Resolved |
| Project: | sfc |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tomas Cechvala | Assignee: | Tomas Cechvala |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
log_see_lines_at_the_bottom.txt
|
| External issue ID: | 3940 |
| Priority: | High |
| Description |
|
SfcSffToOvsMappingAPI -> INFO -> Cannot build OvsdbBridgeAugmentation. Missing OVS Node augmentation on SFF SFF1. This happens when Service-Function-Forwarder is put into config DS ( http://pastebin.com/Fs8JAXuc) onDataChange method is triggered in SfcOvsSffEntryDataListener in which OvsdbBridgeAugmentation gets resolved. This process involves reading from network topology in OPERATIONAL datastore (http://controllerIp:port/restconf/operational/network-topology:network-topology/topology/ovsdb:1). The problem is, that those data are not rendered from OVS right away. It takes a while to have them present. So if anyone tries to write Service-Function-Forwarder data to OPERATIONAL sooner, Node augmentation can not be read. |
| Comments |
| Comment by Tomas Cechvala [ 06/Jul/15 ] |
|
Please, see last lines. |
| Comment by Tomas Cechvala [ 06/Jul/15 ] |
|
Attachment log_see_lines_at_the_bottom.txt has been added with description: Karaf log |
| Comment by Tomas Cechvala [ 06/Jul/15 ] |
|
sorry for my typo: ...to write Service-Function-Forwarder data to CONFIG, not OPERATIONAL. |
| Comment by Reinaldo Penno [ 10/Jul/15 ] |
|
Can you please clarify in which scenario this happen? You tried to create a SFF or what? |
| Comment by Tomas Cechvala [ 10/Jul/15 ] |
|
Yes, I set OVS manager on VM and then created SFF by this REST call http://pastebin.com/Fs8JAXuc. It takes some time until manager gets connected to ODL. Until that moment, data in topology http://controllerIp:port/restconf/operational/network-topology:network-topology/topology/ovsdb:1 are not present. So when I inserted SFF via REST, onDataChanged method was called in SfcOvsSffEntryDataListener to create OVSDB augmentations to CONF DS so a vSwitch can be created on VM. Resolving OVSDB augmentations involves reading from topology in operational DS. When those data are not present yet, augmentations fail to be resolved and vSwitch on the VM is not created. |
| Comment by Tomas Cechvala [ 11/Jul/15 ] |