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                                                                         
        }                                                                                                
    }                                                                                                    
}

@MattK provide a simple example of "set" commands to reproduce

Quite likely the following relevant patches are not present in 1.4-rc1:

• https://github.com/vyos/vyos-1x/commit/975ce1c71352e319abef59e9e63de2c3fca2f281
• https://github.com/vyos/vyos-1x/commit/3d9f381964e53fe0ce6456724660727283802f48

Hello, this task has a bug. Do I open a new task or comment here?

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

My only comment here would be to hesitate when putting in restrictions; as Doug Gwyn once said:

Unix was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.

I just did a test - without the VLAN interfaces added, the VLAN traffic is still offloaded.
So the CLI should be updated to prevent VLAN's from being added (since it doesn't make any sense to add them, since they work when the parent interface is added)

We have a decision to leave it as it is.
@c-po closed the task T4487
So close it as wontfix.

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

We don't need append
We should use leafNode type /multi for example https://github.com/vyos/vyos-1x/blob/4c29922cc0baa9c127391b58e82b76f69e1e2dce/interface-definitions/include/bgp/afi-l2vpn-common.xml.i#L43

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

In testing before PR:
https://github.com/vyos/vyos-1x/compare/current...jestabro:serial-console-config-mode

PR for 1.4 https://github.com/vyos/vyos-1x/pull/2810

@fdcastel Thanks for confirming

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2809

Also working with 1.5 / circinus:

The issue is only on boot, if after booting you run the load command, it loads fine and commit works without any issues.

Booting now gives this:

Fixed! Thanks guys!

During a boot that raises the migration error, can you alter the grub boot command to add vyos-config-debug? See https://docs.vyos.io/en/latest/contributing/debugging.html#kernel

Just thinking aloud - could it be the period that is causing issues with the loading?

It is still a bug and was reproduced in T5926

Just a question: Would it be nice if this feature could also be combined with the commit-confirm?
e.g. like commit-confirm soft 20

This issue seems to appear only with 1.3 but not with 1.4

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

Backported: https://github.com/vyos/vyos-documentation/pull/1237

please mark as won't fix

Description updated; as this may have been a transient issue while supporting tools were merged, close and reopen if recurrence.

I expected the load the image in the background (during the commit), without op-mode.
That's why it was initially opened.
But we must use the load images from op-mode first because otherwise, we have some bugs.

@troggie Add please an example of working config accel-pp.conf wit those options
Otherwise, I'll mark it as wontfix.
Thanks.

Not reproduced
Re-open it with all steps to reproduce, including scripts that generate your config.
The Load is used anywhere and never has issues like this.
Close it for now.

VyOS 1.3 runs salt 3003.5
VyOS 1.4 runs salt 3005.4+ds-1
VyOS 1.5 runs salt 3005.4+ds-1

This is expected behavior.