From: Emanuele Di Pascale <emanuele@voltanet.io>
Date: Tue, 18 May 2021 13:52:44 +0000 (+0200)
Subject: pathd: fix render candidate-path bandwidth
X-Git-Tag: base_8.1~466^2
X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=ec957bbc2af02ea7bbaa65e852be912f35685495;p=matthieu%2Ffrr.git

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 <emanuele@voltanet.io>
---

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,