Page MenuHomeVyOS Platform

VRF and BGP neighbor local-as error
Closed, ResolvedPublicBUG

Description

Add VRF and set local-as for the peer

vyos@r14# show vrf 
 name foo {
     protocols {
+        bgp {
+            local-as 65001
+            neighbor 192.0.2.5 {
+                local-as 65002 {
+                }
+                remote-as 65001
+            }
+        }
     }
     table 1010
 }
[edit]
vyos@r14#

Commit:

vyos@r14# commit
[ vrf name foo protocols bgp ]

WARNING: BGP neighbor "192.0.2.5" requires address-family!
VyOS had an issue completing a command.


Report time:      2022-07-22 10:42:01
Image version:    VyOS 1.4-rolling-202207200217
Release train:    sagitta

Built by:         [email protected]
Built on:         Wed 20 Jul 2022 02:17 UTC
Build UUID:       2634b8b4-1c16-4606-bb8d-49da92dbc252
Build commit ID:  69a74e6399904b

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  QEMU
Hardware model:   Standard PC (Q35 + ICH9, 2009)
Hardware S/N:     
Hardware UUID:    4d6f4d29-1ae8-446f-8d2b-3decd9da64c7

Traceback (most recent call last):
  File "/usr/libexec/vyos/conf_mode/protocols_bgp.py", line 377, in <module>
    apply(c)
  File "/usr/libexec/vyos/conf_mode/protocols_bgp.py", line 368, in apply
    frr_cfg.commit_configuration(bgp_daemon)
  File "/usr/lib/python3/dist-packages/vyos/frr.py", line 480, in commit_configuration
    raise ConfigurationNotValid(f'Config commit retry counter ({count_max}) exceeded')
vyos.frr.ConfigurationNotValid: Config commit retry counter (5) exceeded



[[vrf name foo protocols bgp]] failed
Commit failed
[edit]
vyos@r14#

Details

Difficulty level
Easy (less than an hour)
Version
VyOS 1.4-rolling-202207200217
Why the issue appeared?
Other
Is it a breaking change?
Stricter validation
Issue type
Bug (incorrect behavior)

Event Timeline

Commit fails b/c of frr-reload output: 200 % Local-AS allowed only for EBGP peers - we should add an appropriate verify() stage I guess.

c-po triaged this task as Normal priority.
c-po changed Difficulty level from Normal (likely a few hours) to Easy (less than an hour).
c-po changed Why the issue appeared? from Will be filled on close to Other.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Stricter validation.