-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ACL] Add Tunnel Next Hop redirect support #3399
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Vivek Reddy <[email protected]>
Unrelated UT failure. Not seen on local machine @lolyu Are you familiar on why this might fail? |
Signed-off-by: Vivek Reddy <[email protected]>
NVM, interestingly only seen on bullseye environment. Fixed the problem |
Signed-off-by: Vivek Reddy <[email protected]>
@bingwang-ms for viz |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
return SAI_NULL_OBJECT_ID; | ||
m_redirect_target_next_hop = target; | ||
m_pAclOrch->m_neighOrch->increaseNextHopRefCount(nh); | ||
return m_pAclOrch->m_neighOrch->getNextHopId(nh); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like logic is changed. Previously it returned NULL OBJECT if hasnexthop
failed. Should we keep the old behaviour?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This field can take many variants, it can be Port, Lag, NH IP, NHG and now Tunnel NH.
Previous logic is incorrect as if get NH fails, it should try to check if it is one of other variants instead of returning SAI_NULL_OBJECT_ID
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
What I did
Why I did it
How I verified it
Details if related