I opened the PR for our custom build of the package in vyos-build as well: https://github.com/vyos/vyos-build/pulls. I was waiting on testing results from anyone, but I went and tested it myself. The basic functionality works, I couldn't test the above bug. If it's merged and the new package build is added to CI, the above debian PR isn't needed (or our custom build isn't).

I ran into this today after upgrading to latest 1.3 rolling image. All interfaces were added and appeared to have the correct macs (the output of ip link matched what was in the config), but the physical interfaces to which they corresponded weren't right. I found this by looking at the link state of each interface and saw that two if them were swapped. The interface that should be eth2 was physically eth4 and vice versa, but the macs it was showing in ip link was wrong for that physical card, as if it were set to the other interface's mac erroneously.
I got the cards to detect properly after 2 reboots.

I installed 1.3-rolling-202003190217 today and verified that it contains the following lines now:

I seem to experience the same in a VRRP setup using VyOS 1.3-rolling-202003110613. I will try to gather more information along with a sample config file.

Some tests results

vyos@R8:~$ show configuration commands | match mpls
set protocols mpls ldp discovery transport-ipv4-address '2.2.2.2'
set protocols mpls ldp interface 'eth1'
set protocols mpls ldp interface 'eth2'
set protocols mpls ldp router-id '2.2.2.2'
vyos@R8:~$ show mpls ldp neighbor 
AF   ID              State       Remote Address    Uptime
ipv4 10.0.0.1        OPERATIONAL 10.0.0.1        00:00:22
ipv4 3.3.3.3         OPERATIONAL 10.0.255.2      00:00:33
vyos@R8:~$ show mpls ldp interface 
AF   Interface   State  Uptime   Hello Timers  ac
ipv4 eth1        ACTIVE 00:00:51 5/15           1
ipv4 eth2        ACTIVE 00:00:52 5/15           1

2 PR for basic MPLS implementation
https://github.com/vyos/vyos-build/pull/90
https://github.com/vyos/vyos-1x/pull/247

Could you describe your "dream syntax" for it?
The op mode node.def's simply don't have a concept of value help in vyatta-cfg, only comp_help (<completionHelp> in XML terms).

https://salsa.debian.org/pkg-netfilter-team/pkg-conntrack-tools/-/merge_requests/1
if he merge the PR, we can use it!

There is yet no intention to add such command. Usually all description strings are rendered into the appropriate configuration file or are added to the interface as alias used by SNMP monitoring. What you wish to do is actually commenting on your configuration. Please refer to the user-guide about the comment command.

A description field is required to understand what this is for.

https://github.com/vyos/vyos-documentation/pull/220

What exactly do you mean with "description"?

@hagbard This problem is back on a rolling built on the 14th. Fix again was to run

https://github.com/vyos/vyos-1x/commit/5cb0059353e94dc11aa116e4aa8ce0422c4f3534 should fix the issue. The op-mode commands may need to be refactored in general and split into it's own structures.

Template VyOS for Zabbix 4.x version with SNMPv2 checks.
No need to install any additional programs.

In which version FRR has been upgraded to 7.3?

+1 for closing - never heard of this issue again and we upgraded to FRR 7.3

Still not working as expected

Reopened, confirmed broken again.

@kroy @rherold can we mark this as fixed?

@syncer https://github.com/vyos/vyos-1x/commit/dad110ce666edae42ac18c59a800bda503589f27 are only CLI modifications (validation to be be precise), no code changes at all which would change the functionality, in my opinion it can be backported as is.