Great work, thanks for checking that case too.

If possible, can you try duplicating with more than one vni configured, then delete one of them? I'm pretty sure I tried that case a few weeks ago on an older 1.4 rolling with same issue. This was just the minimum config to reproduce.

New source release, not in Debian yet: https://github.com/acassen/keepalived/releases/tag/v2.3.1

I thought the fix was merged post-2.2.8 and that we were waiting for next upstream release, or is my understanding of the build process wrong?
https://github.com/vyos/vyos-build/blob/a9cc581827e9a0ba1646b16ed07170e4ec2ca34e/packages/keepalived/Jenkinsfile#L27

Working on 1.4-rolling. Thanks for the awesome work.

Using the same router/config I noted previously, I see an "empty" config per T6084.

admin@removed# cat /run/opennhrp/opennhrp.conf
# Created by VyOS - manual changes will be overwritten

I then modified the nhrp vyos config and saved, and the opennhrp.conf was re-populated. Upon reboot, the file reverted to "empty".

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

That doesn't seem to insert missing leaf nodes, so I rebuilt the installation by copy/paste of commands from existing VM, and it migrated the routes as expected upon upgrade to 1.4-rc2.

Well, it didn't start on 1.3.2, so I don't know how the empty leaf nodes could have disappeared over time.

So, the problem seems to be with empty leaf nodes missing from my baseline config.

Performed these steps:

• clean, checkout 1.3.5, build, push to internal web host
• rollback VM to 1.3.2 working baseline
• save vyos132.cfg
• add system image https://removed/vyos-1.3.5-private-amd64.iso
• reboot
• compare 1, no changes to config as expected
• add system image https://cdn.vyos.io/1.4.0-rc1/vyos-1.4.0-rc1-amd64.iso
• reboot
• compare 1, confirm routes dropped per T5947 description
• load vyos132.cfg
• compare 1, observe routes have been migrated as expected, below

1.4.0-rc2 also has opennhrp service stop after vyos startup. Can you please add a 1.4 tag to this issue?

I lost my legacy LTS access, so I'll have to build 1.3-latest to test that.

Performed these steps:

• rollback VM to 1.3.2 working baseline
• save vyos132.cfg
• add system image https://cdn.vyos.io/1.4.0-rc1/vyos-1.4.0-rc1-amd64.iso
• reboot
• compare 1, confirm routes dropped per T5947 description
• load vyos132.cfg
• compare 1, observe routes have been migrated as expected, below

Agreed, if it had migrated correctly, I'd see new entries under protocols static; however, the config comparison I posted doesn't have those replacement entries, and my ipv6 (lack of) connectivity confirms it didn't migrate as expected.

I was unable to duplicate the behavior with 1.4.0-rc1. Performed add system image https://cdn.vyos.io/1.4.0-rc1/vyos-1.4.0-rc1-amd64.iso) with above configuration, and nhrp came up on reboot. So it's common to 1.4 and 1.5, but only since sometime in December (post rc1)?

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.