Fixed in the latest version:1.4-rolling-202103230217

PR: https://github.com/vyos/vyos-build/pull/153

I'm not really sure what the issue is. I can narrow it down to this:

Can you share more examples/configs?
How can we reproduce it?

@Asteroza With Vyos, any service should be turned off by default unless it is explicitly configured by the user

This affects downstream clients as well

There are genuine use cases, especially for small/home networks. But UPnP is a literal minefield of problems, and on top of that has had some serious security issues in the past due to fundamental design. If you were going to do this, I would want it off by default.

@Viacheslav The issue persists in vyos-1.3.0-rc2-amd64.iso

The root of the problem here is changed place for custom options and the ability to configure options that should be applied differently, depending on the place. In other words, "Additional OpenVPN options" becomes "Additional OpenVPN options. You must use the syntax of openvpn.conf in this text-field", but actually these variants are not fully equal and cannot be converted directly.

@francis try please vyos-1.3.0-rc2-amd64.iso
https://community.vyos.net/get/snapshots/

Another solution it include "user" defined file for options
An example CLI

set interfaces openvpn vtun10 openvpn-option-include '/config/openvpn/included.conf'

@c-po, you cherry-picked the wrong commit: equuleus needs the fix from current, not crux.

In T3418#90244, @c-po wrote:

The first error is related to T2759 and can be ignored.

For the second one, can you please provide your full BGP config by pasting the content of show configuration commands | match bgp\|policy

Post the migration of the script from /opt/vyatta/bin/vyos-strip-config.pl to /usr/libexec/vyos/strip-private.py, the strip-private seems to be not working when the ipv6 address is configured to an interface.

@jack9603301 It is not a matter of different codes, but rather what python libraries have been provided so far: the focus has been on abstracting the config session, in several directions, and previously there had not been a use case for reading config settings from op mode.

This is still an issue with 1.2.7-epa1

The first error is related to T2759 and can be ignored.

This is still a issue i build a new image with https://github.com/vyos/vyos-1x/commit/911fe645928750f3ce38061a94c9b6db50db0749 and it was spitting out errors :/

Sorry, I have a question, why are there different codes for operation mode fetch configuration tree and configuration mode fetch configuration tree? Is it because of the uncertainty of the mode of action in the user's actions (such as the possibility of abruptly terminating the command)?

Service still with no description VyOS 1.3-beta-202103170443

PR https://github.com/vyos/vyos-1x/pull/778