The FRR apply function was called when omitting the skip_frr parameter, which is the case when saving the host network configuration via the Web UI, leading to an enabled FRR daemon after saving the network configuration.
In a follow-up we should also consider checking if the previous configuration contained FRR entities, but the new one doesn't and disable the FRR daemon in this case. pve-manager: Stefan Hanreich (1): api: network: default to not regenerating the frr configuration PVE/API2/Network.pm | 7 ++++--- bin/pve-sdn-commit | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-) pve-network: Stefan Hanreich (1): sdn: api: rename parameter from skip-frr to regenerate-frr src/PVE/API2/Network/SDN.pm | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) Summary over all repositories: 3 files changed, 10 insertions(+), 11 deletions(-) -- Generated by git-murpp 0.8.0 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
