There is already a task opened for this error:

https://github.com/vyos/vyos-1x/pull/4442

In VMware vSphere, in multiple devices these log messages are seen after upgrading to 1.4.1 version:

This below specific configuration was allowed in 1.3.8 but not in 1.4.1 anymore, if defined it needs to be migrated in this format: "set system syslog host 10.29.113.213 port '9001'"

I was not able to reproduce the issue, please check in the latest rolling release.
After removing the disabled option, the strongswan service is reloaded and the connection established immediately.

@dmbaturin I have not seen issue without scripting, what I meant is the problem occurs when the config is modified. When I tested with the configured script, it checks the reachability of an ip address if unreachable then it calls to commit the changes so when this condition was not met, the issue was not reproduced.

This PR https://github.com/vyos/vyos-1x/pull/3311 has fixed the issue.
Tested in 1.4.0 and latest rolling release. 1.5-rolling-202409250007

The issue is not found in 1.3.8 version but found in 1.4.0 and latest 1.5 rolling release.

Tested in the latest version 1.5-rolling-202408200022, the renaming migration works and the configuration:

@Harliff , please create a new bug report and share your config.boot file and mention any messages printed on your console while upgrade in the task description

Tested in 1.4.0 version and did not receive the error:

@Viacheslav, Thank you for the hint. After further analysis, these are the findings from the tests done in the lab running 1.4.0 version on both sides with server/client setup.

@Viacheslav, For site-to-site or server/client mode, when used cipher option as none then also issue is noticed. When you commit, it gives this warning:

I tested in the latest rolling version and the traceback error is not received anymore and the tunnel ip column shows n/a but with multiple entries.
It still shows the disconnected client and I assume it should not show disconnected clients

The feature is present in 1.4 and 1.5:

Tested in different possibilities:

Tested in VyOS 1.5-rolling-202402280022 and it works now :

The issue is raised in this forum query: https://forum.vyos.io/t/commit-archive-doesnt-accept-symbols-in-password/13817
Remote host having password with special character is not accepted using with scp command

Works in this version 1.5-rolling-202402160022

I also see this behavior when switching between images in 1.4.0-rc3" and sometimes default-boot setting does not work.

Tested in latest 1.5-rolling-202401190024 release, the commit fails when duplicate static-mapping is configured as expected.

Tested in 1.3.5, the issue still exist as stated by @fernando