-
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
ospf6d: fix argument processing in the "area ... range" command #9108
ospf6d: fix argument processing in the "area ... range" command #9108
Conversation
* When the "cost" argument isn't present, the default cost should be used instead of preserving the previously configured one (if any); * When the "not-advertise" argument isn't present, the "not-advertise" flag should be unset regardless if it was previously configured or not. Configuration commands should be deterministic and work in the same way regardless of the current state. Signed-off-by: Renato Westphal <[email protected]>
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULContinuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20417/ This is a comment from an automated CI system. |
Signed-off-by: Renato Westphal <[email protected]>
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20420/ This is a comment from an automated CI system. |
@Mergifyio backport stable/8.0 |
Command
|
ospf6d: fix argument processing in the "area ... range" command (backport #9108)
used instead of preserving the previously configured one (if any);
flag should be unset regardless if it was previously configured or
not.
Configuration commands should be deterministic and work in the same
way regardless of the current state.
Signed-off-by: Renato Westphal [email protected]