With the same config:

I think I see part of what's happening here; it looks like the format for configuration-sync URIs removed the colon (:) between the host and path:
<PROTO>://<USER>:<PASS>@<HOST>:<PATH>
is now:
<PROTO>://<USER>:<PASS>@<HOST><PATH>

It looks like what this should be converted to is as follows:

trae@cr01b-vyos# show as-path-list 
 as-path-list DAL10 {
     rule 10 {
         action permit
         description "Allow anything from or via DAL10"
>        regex 4242420668_$
     }
 }
 as-path-list IBM {
     rule 10 {
         action permit
         description "Allow anything directly from IBM Cloud"
>        regex ^_42424206(68|70)_$
     }
 }
 as-path-list INT {
     rule 10 {
         action permit
         description "Allow anything from or via int"
>        regex 4242420666_$
     }
 }

It looks like with VyOS 1.3, one way to match AS path (or at least, the way I did it) was to use an escaped parenthesis [\)], but in 1.4+ it appears this way no longer works, and instead those escapes should probably be converted to underscores (_).

I'm seeing this on 1.4 as well, dockerized build 1.4-rolling-202401061915), configured following https://docs.vyos.io/en/sagitta/configuration/vpn/dmvpn.html with no other protocols/services.

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

PR https://github.com/vyos/vyatta-op/pull/87

I haven't had the chance to test this, but the following should be sufficient to replicate the behaviour:

The best option for now would be to delete those commands and re-implement them in a separate feature request if required.
https://github.com/vyos/vyatta-op/tree/current/templates/show/remote-config

PR https://github.com/vyos/vyatta-op/pull/86

PR https://github.com/vyos/vyatta-op/pull/86

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

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

@fdcastel The thing is, we don't have secrets_lines in the dictionary.
So, it is a wholly broken script and must be deleted or rewritten.

In rVYOSONEXee494c3a1dbfca3457bcaffe89d45971348e4848#958479, @sdev wrote:

Are you able to provide the dhcp config that fails migration? I wasn't able to re-create any migration problem in my tests

I'm having the same error. Even with NO ipsec configured. Just using DHCP.

In rVYOSONEXee494c3a1dbfca3457bcaffe89d45971348e4848#958453, @workingagain wrote:

when migrating from pre subnet-id builds to a subnet build will cause migration failed during initial startup due to missing subnet id.

Can confirm, short term testing worked.

I'm seeing the same problem. Latest 1.4 version from git.

Oops, I didn't see T5647! Sorry! I guess this one can be closed as a duplicate.

In T5932#172324, @marc_s wrote:

I take it RC2 will contain these new versions @Viacheslav?

Do static addresses/gateways work stable enough?

100% agree. I have submitted a similar feature request here:

I take it RC2 will contain these new versions @Viacheslav?

Seems you're right @indrajitr:

@Viacheslav sure, updated the OP

Always use "set commands" to make it easier for developers to reproduce it.

@samip537 You should use the peer group definition inside the v6-only stanza, like so:

neighbor wg1 {                                                                                           
    interface {                                                                                          
        v6only {                                                                                         
            peer-group BACKBONE                                                                          
            remote-as 4242420669                                                                         
        }                                                                                                
    }                                                                                                    
}