-
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
ospfd: OSPF SR is not turned on - "segment-routing node-msd" always enabled by default #14910
Closed
1 of 2 tasks
Labels
Comments
Hi, I'm seeing what's wrong. Default value should not be written if Segment Routing is disabled. I'll have a look to correct the problem. Olivier |
@odd22 anything we can help you with? |
c-po
changed the title
ospfd: OSPF SR is not turned on - "segment-routing node-msd 5" always enabled by default
ospfd: OSPF SR is not turned on - "segment-routing node-msd" always enabled by default
Feb 8, 2024
Can also be reproduced within vtysh: Enable SR and MSD
Disable SR
MSD can no longer be removed
Even removing the entire OSPF process does not help
AssumptionIn |
c-po
added a commit
to c-po/frr
that referenced
this issue
Feb 8, 2024
This fixes the initial implementation of commit 7743f2f ("OSPFd: Update Segment Routing PR following review") where it wsa not possible to remove the "segment-routing node-msd" CLI nodes via vtysh once segment-routing got disabled. Closes FRRouting#14910 Signed-off-by: Christian Breunig <[email protected]>
c-po
added a commit
to c-po/frr
that referenced
this issue
Feb 8, 2024
This fixes the initial implementation of commit 7743f2f ("OSPFd: Update Segment Routing PR following review") where it wsa not possible to remove the "segment-routing node-msd" CLI nodes via vtysh once segment-routing got disabled. Closes FRRouting#14910
mergify bot
pushed a commit
that referenced
this issue
Feb 9, 2024
This fixes the initial implementation of commit 7743f2f ("OSPFd: Update Segment Routing PR following review") where it wsa not possible to remove the "segment-routing node-msd" CLI nodes via vtysh once segment-routing got disabled. Closes #14910 Signed-off-by: Christian Breunig <[email protected]> (cherry picked from commit ba45aa6)
mergify bot
pushed a commit
that referenced
this issue
Feb 9, 2024
This fixes the initial implementation of commit 7743f2f ("OSPFd: Update Segment Routing PR following review") where it wsa not possible to remove the "segment-routing node-msd" CLI nodes via vtysh once segment-routing got disabled. Closes #14910 Signed-off-by: Christian Breunig <[email protected]> (cherry picked from commit ba45aa6)
c-po
added a commit
to c-po/frr
that referenced
this issue
Feb 9, 2024
This fixes the initial implementation of commit 7743f2f ("OSPFd: Update Segment Routing PR following review") where it wsa not possible to remove the "segment-routing node-msd" CLI nodes via vtysh once segment-routing got disabled. Closes FRRouting#14910 Signed-off-by: Christian Breunig <[email protected]> (cherry picked from commit ba45aa6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
frr-reload.py
fails as OSPF process always installs a segment-routing config linesegment-routing node-msd 5
To Reproduce
** With vtysh **
Now start OSPF
This behavior manifests in un-reloadable configurations using
frr-reload
:Unloading config works:
/usr/lib/frr/frr-reload.py --reload --daemon ospfd --debug --stdout no-ospf.txt
Now start OSPF process using
frr-reload
:sudo /usr/lib/frr/frr-reload.py --reload --daemon ospfd --stdout ospf.txt
The first run is successful and you get:
Any subsequent run will result in:
Expected behavior
Reload completes
Screenshots
Versions
Additional context
The text was updated successfully, but these errors were encountered: