This is perhaps a warning/FYI if, like me, you’ve been using Ansible to configure VyOS on the rolling release. I’ve moved from a 2024 Rolling release to the later 2025-08-11 version, and found my changes were lost after a reboot. This never happened before on the 2024 Rolling release.
The fix, make sure you use save: true in your task -
- name: Add config
vyos_config:
save: true
I’ve pushed configs out ~1000’s of times using Ansible for a project I’m working on and never had an issue, until moving to the 2025 Rolling release.
Hi Andy,
The auto-save setting is False by default, and the documentation clearly states that:
save:
description:
- The C(save) argument controls whether or not changes made to the active configuration
are saved to disk. This is independent of committing the config. When set
to True, the active configuration is saved.
type: bool
default: no
It has been for a while. I suspect that VyOS might have taken care of auto-save before and now it is not
Thats my assumption. I’m just highlighting here as it’s a change. It’s not a complaint, and I recognise the documentation for the Ansible VyOS support does say that save: false is default.
I’m simply highlighting something others may get caught by, like me.