After some investigation, it can be advised, that the described issue is to do with netcomm_cli module implementation used by VyOS Ansible Galaxy - namely, the ansible_net_version is set for a connection and stays so until reconnects and re-reads the modified hostname.
As such, this is currently outside of the collection's control.
That said, the issue can be easily avoided by reading ansible_facts mid-playbook:
Example Playbook:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 11 2025
Here's the PR: https://github.com/vyos/vyos.vyos/pull/401
It was increased from 5 to 60
https://github.com/vyos/vyos-1x/commit/92631e7516bfe8aebc0332d41c17ba92c93ab7bb
Mar 10 2025
Refer to this pull request;
https://github.com/vyos/vyos-1x/pull/4387
In T7220#217503, @carlos wrote:So I guess this is very low priority for you guys, but it is very critical for me, so quick question, do you accept PR from general public? If yes, I might go ahead and take a look in how to get this done :)
In the meantime I'll setup a post-commit hook.
Mar 8 2025
PR #4385
Mar 7 2025
After deep investigation with @zsdc, we found that the issue can be here https://github.com/FRRouting/frr/blob/f3a7077df01176164c0bb5775ecb886cf233089e/ldpd/neighbor.c#L629
Mar 6 2025
So I guess this is very low priority for you guys, but it is very critical for me, so quick question, do you accept PR from general public? If yes, I might go ahead and take a look in how to get this done :)
It appears this is by design, FRR creates kernel routes with metric 20
vtysh show ip route, shows correct route
Is there anyone else we should tag on this ticket?
Mar 5 2025
Is resolved in VyOS 2025.03.05-0017-rolling.
I am running on VyOS 1.5-rolling-202503030030 , and this error has fixed