Page MenuHomeVyOS Platform

FRR config
Closed, ResolvedPublicBUG

Description

Since 1.4-rolling-202101140417 (this is last one working), 1.4-rolling-202101151916 and 1.4-rolling-202101160217 don't work, loading FRR configuration results in errors for me:

First:

[ protocols bgp XY neighbor YZ remote-as internal ]
'internal' is not a valid integer number

AS being internal / external used to work.

Second, after replacing "internal" with number:

VyOS had an issue completing a command.

We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):

When reporting problems, please include as much information as possible:

  • do not obfuscate any data (feel free to contact us privately if your business policy requires it)
  • and include all the information presented below

Report Time: 2021-01-16 08:40:19
Image Version: VyOS 1.4-rolling-202101160217
Release Train: sagitta

Built by: [email protected]
Built on: Sat 16 Jan 2021 02:18 UTC
Build UUID: 3f86b3bd-c38c-4f0d-9a05-90ca2c153776
Build Commit ID: 76f293633fb5fe

Architecture: x86_64
Boot via: installed image
System type: bare metal

Hardware vendor: Supermicro
Hardware model: Super Server
Hardware S/N: 0123456789
Hardware UUID: 00000000-0000-0000-0000-ac1f6b6d1132

Traceback (most recent call last):

File "/usr/libexec/vyos/conf_mode/protocols_bgp.py", line 165, in <module>
  apply(c)
File "/usr/libexec/vyos/conf_mode/protocols_bgp.py", line 141, in apply
  frr_cfg.commit_configuration(daemon='bgpd')
File "/usr/lib/python3/dist-packages/vyos/frr.py", line 411, in commit_configuration
  reload_configuration('\n'.join(self.config), daemon=daemon)
File "/usr/lib/python3/dist-packages/vyos/frr.py", line 186, in reload_configuration
  raise CommitError(f'Configuration FRR failed while commiting code: {repr(output)}')

vyos.frr.CommitError: Configuration FRR failed while commiting code: ''

Details

Difficulty level
Unknown (require assessment)
Version
1.4-rolling-202101160217
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)