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

@fernando I think you mixed up ospf vs ospfv3.

Still broken in 1.4.0-epa1 (self-built).

If the peer reconnects after the first disconnect - does the local VTI interface go "UP" again?

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

The motivation here was from T5660, for which it was not needed. However, a version of the constructions in the branch above will be useful for development of the modern commit algorithm and comparison with the idiosyncrasies of legacy (T5492). Put on hold for now.

PR https://github.com/vyos/vyos-1x/pull/2157 closed due to long standing conflicting files.

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

You don't have eth0.150

is it possible to extend this feature to json api of vyos?

Rebooting the failed image (I did not redo the upgrade - the failed image remained on the router) produces:-

itconsult@ha-r02a:~$ cat /tmp/vyos-configd-script-stdout

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

I don't know what testing you might want to do, but for me it now works as expected.

Gotcha, thanks!

The configuration checks are the 'verify' stage of the respective config mode script; general structure here:
https://docs.vyos.io/en/sagitta/contributing/development.html#configuration-script-structure-and-behaviour

What is the content of
/tmp/vyos-configd-script-stdout ?

In T5991#178350, @jestabro wrote:

I raised this issue for discussion last week, and am testing more 'lenient' verification in cases such as above; I'll add results and plans here, as available.

I raised this issue for discussion last week, and am testing more 'lenient' verification in cases such as above; I'll add results and plans here, as available.

That commit has the side effect that using sudo or even just committing some configurations will return "sudo: unable to resolve host vyos: System error" every time. Applications that rely on the system hostname will also not be able to reach localhost if the hostname is not a FQDN.

Thanks for that.

1.4 https://github.com/vyos/vyos-1x/pull/3062
1.5 https://github.com/vyos/vyos-1x/pull/3061

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

Firewall failed migration due to incorrect subnet, 1.3 firewall did not correctly validate those fields. Correcting source address on rule 30 on TO-ROUTER chain should migrate the firewall properly.

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

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

PR for global solution extends the local solution in T5839:
https://github.com/vyos/vyos-1x/pull/2659