Closed krihal closed 8 months ago
When doing a 'validate push' or 'commit' the device might return an error. Now this is what I see in the CLI:
debian@khn-dev[/]# validate push Transaction 3 failed Unexpected reply from juniper2 in state PUSH-VALIDATE: debian@khn-dev[/]#
If I look in the backend debug I can see the real error message, this must be shown in the CLI too:
Oct 19 06:14:39: Recv from juniper1: <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/22.3R0/junos" message-id="4"> * Reloading keepalived configuration...... ...fail! <nc:rpc-error> <nc:error-type>protocol</nc:error-type> <nc:error-tag>operation-failed</nc:error-tag> <nc:error-severity>error</nc:error-severity> <nc:error-path> [edit] </nc:error-path> <nc:error-info> <junos:source-daemon>rpd</junos:source-daemon> <nc:bad-element> policy-options </nc:bad-element> </nc:error-info> <nc:error-message> Policy error: Policy peering-in referenced but not defined. <----------------------------- That is the information I need </nc:error-message> </nc:rpc-error> <nc:rpc-error> <nc:error-type>protocol</nc:error-type> <nc:error-tag>operation-failed</nc:error-tag> <nc:error-severity>error</nc:error-severity> <nc:error-path> [edit protocols bgp group test neighbor 1.1.1.1] </nc:error-path> <nc:error-info> <junos:source-daemon>rpd</junos:source-daemon> <nc:bad-element> import </nc:bad-element> </nc:error-info> <nc:error-message> BGP: import list not applied </nc:error-message> </nc:rpc-error> <nc:rpc-error> <nc:error-type>protocol</nc:error-type> <nc:error-tag>operation-failed</nc:error-tag> <nc:error-severity>error</nc:error-severity> <nc:error-message> configuration check-out failed </nc:error-message> </nc:rpc-error> </nc:rpc-reply>
debian@khn-dev[/]# commit Transaction 6 failed Error syntax error, expecting <rpc> or </rpc> in state PUSH-EDIT of device juniper1
When doing a 'validate push' or 'commit' the device might return an error. Now this is what I see in the CLI:
If I look in the backend debug I can see the real error message, this must be shown in the CLI too: