[SFC-30] SF selection algorithm shortest-path causes failure when creating RSP Created: 22/May/15  Updated: 25/May/18  Resolved: 25/May/18

Status: Verified
Project: sfc
Component/s: General
Affects Version/s: unspecified
Fix Version/s: Oxygen

Type: Bug
Reporter: Brady Johnson Assignee: Keith Burns
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: GIF File ScreenHunter_01 May. 25 09.27.gif    
External issue ID: 3338
Priority: High

 Description   

Ahmed Medhat (a.medhat.h@gmail.com) is using SFC for his doctorate and found that the shortest-path algorithm causes a failure when creating a Rendered Service Path.

This problem should be fixed in both beryllium master and in stable/lithium.

Creating a simple RSP with the following simplified config:

SFC [TcpProxy, TcpProxy]
SFP [transport=mac]
SFs [2SFs]
SFFs [2 SFFs, 1 SF each]

When creating the RSP via RCP, I get the following errors in the log:

2015-05-22 12:52:08,911 | INFO | qtp873483290-642 | SfcProviderRenderedPathAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | Selected SF Schdedule Type: class org.opendaylight.yang.gen.v1.urn.intel.params.xml.ns.yang.sfc.sfst.rev150312.ShortestPath
2015-05-22 12:52:08,932 | ERROR | SFC-9 | SfcProviderAbstractAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | Invocation exception createRenderedServicePathEntry, message: null
2015-05-22 12:52:08,933 | ERROR | qtp873483290-642 | SfcProviderRenderedPathAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | Could not create RSP. System state inconsistent. Deleting and add SFP sfc-path1 back
2015-05-22 12:52:08,936 | ERROR | SFC-13 | SfcProviderServiceForwarderAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | org.opendaylight.sfc.provider.api.SfcProviderServiceForwarderAPI.deletePathFromServiceForwarderState(SfcProviderServiceForwarderAPI.java:712): Rendered Service Path sfc-path1 does not exist
2015-05-22 12:52:08,939 | ERROR | SFC-14 | SfcProviderServiceFunctionAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | org.opendaylight.sfc.provider.api.SfcProviderServiceFunctionAPI.deleteServicePathFromServiceFunctionState(SfcProviderServiceFunctionAPI.java:942): Rendered Service Path sfc-path1 does not exist
2015-05-22 12:52:08,940 | ERROR | SFC-15 | SfcProviderServiceForwarderAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | org.opendaylight.sfc.provider.api.SfcProviderServiceForwarderAPI.deletePathFromServiceForwarderState(SfcProviderServiceForwarderAPI.java:712): Rendered Service Path sfc-path1 does not exist
2015-05-22 12:52:08,940 | ERROR | qtp873483290-642 | SfcProviderRenderedPathAPI | 284 - org.opendaylight.sfc.provider - 0.1.0.SNAPSHOT | Failed to create RSP for SFP sfc-path1

 Comments   
Comment by Yi Yang [ 25/May/15 ]

The shortest path

Comment by Yi Yang [ 25/May/15 ]

The shortest path algorithm needs you to build a complete SFs and SFFs netwrok topology, you should ensure every SFF has a correct SFF dictionary which includes SFFs it connects to. For your case, you should fill in SFF dictionary of two SFFS by json, REST APIs or SFC UI. This must be done manually.

By the way, https://git.opendaylight.org/gerrit/#/c/19994/ is part of future plan for automatic SFF-to-SFF connection build, it is a big picture we can consider in the future.

So please fill in every SFF's SFF dictionary then retry.

Comment by Yi Yang [ 25/May/15 ]

SFC UI for SFF dictionary

Comment by Yi Yang [ 25/May/15 ]

Attachment ScreenHunter_01 May. 25 09.27.gif has been added with description: SFC UI for SFF dictionary

Comment by Yi Yang [ 01/Jun/15 ]

Ahmed, please close this bug if this isn't an issue any more for you.

Comment by Keith Burns [ 11/Oct/15 ]

This bug is marked for Lithium RC2 and has no owner. I'll take it for now so it stops hitting our screens as we look for bugs to fix.

Can we confirm this is still an issue? Temp changing to Lithium-3

Comment by Brady Johnson [ 11/Feb/16 ]

Moving to Boron.

Comment by Brady Johnson [ 25/May/18 ]

I tested this in Fluorine, and it is no longer a problem. That is, its possible to create a 2-SF RSP as explained in the problem report with the SF Selection Algorithm set to ShortestPath, and there are no errors in the logs, and flows are pushed to the bridge as expected.

Generated at Wed Feb 07 20:38:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.