[SFC-54] Setting an SF on an SFP hop with an SF type different than the corresponding SFC hop should fail Created: 14/Jun/15  Updated: 19/Oct/17  Resolved: 07/Feb/17

Status: Resolved
Project: sfc
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Brady Johnson Assignee: Diego Granados
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 3712
Priority: Normal

 Description   

If an SFC is defined as follows:

SFC-1
[Firewall, TcpProxy, DPI]

And an SFP is defined using that SFC, as follows:

SFP (uses SFC-1]
[SF of type NAT, SF of type Header Enrichment, SF of type Firewall]

Notice that the SF types at each hop are of a different type than specified in the SFC, then there should be a failure, but there is none.

A correct SFP would be as follows:

SFP (uses SFC-1)
[SF1 of type Firewall, SF2 of type TcpProxy, SF3 of type DPI]



 Comments   
Comment by Keith Burns [ 12/Oct/15 ]

Shlomi,

Are you working on this bug? If not, I'd like to take it please.

Comment by Shlomi Alfasi [ 12/Oct/15 ]

I'm not working on that. You can take it

Comment by Diego Granados [ 12/Jan/17 ]

Keith,

I'm working on a fix for this bug, can I take it?

Comment by Diego Granados [ 07/Feb/17 ]

https://git.opendaylight.org/gerrit/#/c/50559/

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