I’ve consistently encountered a bug when using file.managed with a source: salt://... definition on fedora-41-minimal. The operation fails with an error stating that the source file does not exist.
Initially, I assumed this was due to a compatibility issue—perhaps a Python update that broke support for this SaltStack version, which I’ve heard isn’t uncommon. As a workaround, I used the contents keyword with file.managed, which worked fine.
However, I recently tried debian-13-minimal and ran into the exact same issue—SaltStack cannot locate the salt:// file. debian-12-minimal works perfectly.
Could anyone confirm/deny that they have the same problem as me?
My default-mgmt-dvm template is based on debian-12-minimal, which I further minimized using this guide.
In the default-mgmt-dvm I installed qubes-core-agent-passwordless-root and qubes-mgmt-salt-vm-connector.
My wording was wrong in my last message; i installed qubes-core-agent-passwordless-root and qubes-mgmt-salt-vm-connector in the default-mgmt-dvm-template
There’s a known bug in the version of salt used in the Debian templates,
which makes them unsuitable for use as default-mgmt-dvm.
Change this to a Fedora based qube.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
There’s a known bug in the version of salt used in the Debian templates,
which makes them unsuitable for use as default-mgmt-dvm.
Change this to a Fedora based qube.
Could you please link to that bug report?
My default-mgmt-dvm is based on debian-12-xfce and it has been like that for a long time without (noticeable) issues.