https://forum.vyos.io/t/ospf-not-forming-neigborship-after-upgrading-from-1-3-3-to-1-4/14187 may also be related...

confirmed fixed in 1.5-rolling-202403240925

Just in case it helps, after a migration from 1.3 to 1.4.0-epa2, the migrated config ends up as:-

See T6131 for a report of the VTUN/OSPF issue with a simple lab config, which occurs separately from a migration.

Given that Chrony only allows one bind address, versus ntpd which allows multiple, a "wontfix" sounds like the correct answer! :-)

Just to observe that this is not added on every occasion - see for example my update today in https://vyos.dev/T6076 where it was not added when the migration succeeded.

Testing further today, I have managed to get two close configs: one migrates and the other does not.

https://vyos.dev/T6076 is also similar...

Now trying to migrate a second router, with different config. I have corrected the mistakes I could see in the config and have removed policy route config with tcp flags.

Thanks - yes - there were in fact 3 "passive-interface" entries for old interfaces, which I should have tidied. Having deleted them, the migration completed.

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

Thanks for that.

Thank you most kindly for the information. Adding:-

With apologies (not having used Phabricator before), I think I may not have filed this bug report correctly. I also did not intend to "triage" it when filing it, as this should be done by a responsible adult! :-)