-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
isisd: 'tiebreaker' command line funtionality is inconsistent with its implementation #16593
base: master
Are you sure you want to change the base?
Conversation
2815b50
to
ccfbdf2
Compare
|
@donaldsharp I modified the ISIS code, and this OSPF unit test does not involve ISIS configuration. Therefore, is this CI error a false alarm? Could you please trigger the CI again? Thank you. |
please apply the frrbot style suggestions |
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.
Can you please change the PR/commit title to be a short sentence? move any details to the body of the commit.
ccfbdf2
to
25eb516
Compare
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.
code looks okay ... waiting on title change, etc.
25eb516
to
ae69fca
Compare
Sorry, I have changed it. Is this OK? |
We need to get these done -- https://github.com/FRRouting/frr/pull/16593/checks?check_run_id=29461002987 once those are done I'll work on figuring out what is happening with the ci failure ... |
…s implementation The command fast-reroute lfa tiebreaker [downstream | lowest-backup-metric | node-protecting] index (1-255) [level-1 | level-2] will overwrite configurations with the same index but different types. This is because the index is set as the key in frr-isisd.yang. However, the lfa_tiebreaker_cmp function uses a tuple (index, type) as the key. Therefore, the yang file should be modified to stay in sync with the business logic. Test Scenario: On RouterA, first configure fast-reroute lfa tiebreaker downstream index 100 level-1, then configure fast-reroute lfa tiebreaker lowest-backup-metric index 100 level-1, and check the configuration: ! router isis 10 fast-reroute lfa tiebreaker lowest-backup-metric index 100 level-1 exit ! Signed-off-by: baozhen-H3C <[email protected]>
a36482d
to
7d56480
Compare
@Jafaral can you take another look at this? |
isisd: The command fast-reroute lfa tiebreaker [downstream | lowest-backup-metric | node-protecting] index (1-255) [level-1 | level-2] will overwrite configurations with the same index but different types. This is because the index is set as the key in frr-isisd.yang. However, the lfa_tiebreaker_cmp function uses a tuple (index, type) as the key. Therefore, the yang file should be modified to stay in sync with the business logic.
Test Scenario:
On RouterA, first configure fast-reroute lfa tiebreaker downstream index 100 level-1, then configure fast-reroute lfa tiebreaker lowest-backup-metric index 100 level-1, and check the configuration:
!
router isis 10
fast-reroute lfa tiebreaker lowest-backup-metric index 100 level-1
exit
!
Signed-off-by: baozhen-H3C [email protected]