-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Vtysh copy to running config has no effect #16057
Comments
This is not behavior that has ever been programmed and is not expected to ever work. If you want to reload frr.conf you need to issue |
@donaldsharp So this is just missing an implementation and there are no future plans to create one? I find not doing what the CLI suggests without any kind of feedback less than ideal, especially since I could not find any FRR specific documentation for this. |
I told you the implementation, use |
Not really a viable "implementation" if FRR is not run by an init daemon like systemd. |
…plemented correctly in FRR FRRouting/frr#16057
…plemented correctly in FRR FRRouting/frr#16057
…plemented correctly in FRR FRRouting/frr#16057
* Add testcontainers dependency * Add stamina dev dependency * Add `frr_container_vtysh` module scope fixture using testcontainers * Replace pytest-docker fixture with frr_container_vtysh, adding fixture to reset FRR config * Remove `pytest-docker` * Fix typo "intance" * Remove function container scope config * Use full file path for volume mapping * Use master tag as FRRouting image fallback instead of latest * Allow for unlimited attempts within timeout window * Create privileged FRRouting container * Reset FRR BGP configuration manually since the copy command is not implemented correctly in FRR FRRouting/frr#16057 * Remove all BGP statements using regex * Regex search config to check if prefixes are configured since the FRR CLI does not return deterministic results
Description
copy /etc/frr/frr.conf running-config
runs without error, but has no effect on the current running configuration.Version
How to reproduce
Starting frr,
/etc/frr/frr.conf
with below content is loaded.sh run
reports the following configTo change the running config, I'll configure an example static prefix
2001:db8::/32
.Resulting in the following running config.
Exiting the configuration context, running
copy /etc/frr/frr.conf running-config
runs but has not effect on the current running configuration.Expected behavior
I would expect the running configuration to match the startup / saved configuration.
Actual behavior
The running configuration is unchanged.
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: