[GBP-169] NSHC1 incorrectly set for Source VNID Created: 30/Jun/15  Updated: 17/Aug/15  Resolved: 17/Aug/15

Status: Resolved
Project: groupbasedpolicy
Component/s: Integration:SFC
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Keith Burns Assignee: Keith Burns
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: 3903
Priority: High

 Description   

It appears that the remote VNID for symmetric chain is set for all C1 values (both RSPs), yet VNID is set correctly.

Suspect this was introduced as a "regression" when refactoring, as tests worked, but mainly due to SFCOFL2 copying VNID->VNID post C1->VNID, where VNID is set correctly.

I can almost recall the actual IF test where I messed up the rebase, so shouldn't be hard to fix.



 Comments   
Comment by Keith Burns [ 10/Aug/15 ]

MASTER: https://git.opendaylight.org/gerrit/#/c/25079/
Lithium: https://git.opendaylight.org/gerrit/#/c/25080/

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