From bfe35108e235b4b9fbccae36b5f1c319f75b1e98 Mon Sep 17 00:00:00 2001 From: Emanuele Di Pascale Date: Tue, 18 May 2021 15:52:44 +0200 Subject: [PATCH] pathd: fix render candidate-path bandwidth the config for dynamic candidate paths with bandwidth preferences was using a different order of keywords (required bandwidth X) than the corresponding command (bandwidth X required). This confuses frr-reload, and possibly users too. Make both use the same order. Signed-off-by: Emanuele Di Pascale --- pathd/path_cli.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pathd/path_cli.c b/pathd/path_cli.c index 172737c9d4..da41c96414 100644 --- a/pathd/path_cli.c +++ b/pathd/path_cli.c @@ -1195,9 +1195,10 @@ void cli_show_srte_policy_candidate_path(struct vty *vty, dnode, "./constraints/bandwidth/value"); required = yang_dnode_get_bool( dnode, "./constraints/bandwidth/required"); - vty_out(vty, " %sbandwidth", - required ? "required " : ""); + vty_out(vty, " bandwidth"); config_write_float(vty, bandwidth); + if (required) + vty_out(vty, " required"); vty_out(vty, "\n"); } if (yang_dnode_exists(dnode, -- 2.39.5