I’m trying to apply configuration with salt, and no matter what I do it errors out. I’ve looked at these topics: `fedora-39` as `management_dispvm` and `salt`: `ERROR (exception Failed to copy Salt configuration to disp-mgmt-fedora-39)` Error on updating multiple templates (Failed to copy Salt configuration) and searched the web, but the only error messages I can find are just the one, so my search has been limited. I’ve tried to increase storage on the mgmt vm, used both Debian and Fedora templates, and tested different configuration files. The disp-mgmt- vm shuts down as soon as it turns on, and I’m stuck. All my system configurations are salt, and only dom0 configuration works.
We can’t help you with your problem without more details. Please provide the context and the error messages.
The error message is Error (exception Failed to copy Salt configuration to disp-mgmt-{vm}) with {vm} being the name of the VM I’m trying to configure. /var/log/qubes/mgmt-{vm}.log doesn’t give any useful information, but I’d be happy to look elsewhere I can find logs. Part of my problem is a lack of information. I appreciate your help.
Which state? What are the qubes involved and their (disposable) templates? Try to run it with -l debug at the end of the command.
What version of Qubes?
What template is used for default-mgmt-dvm?
What template is used as/by the target?
Does it affect every state?
What is the output using --show-output in the qubesctl call?
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
R4.3, as in title.
I’ve tried fedora-42-xfce, debian-13, and the former with kernelopt ‘selinux=0’.
fedora-43-minimal (I have used minimal templates extensively for years.)
As far as I can tell, yes. I’ve tested pkg.install, file.managed, and file.recurse. I’ve also tried running state.highstate with the top file enabled, and state.apply targeting specific qubes with specific .sls states.
I did, and neither of these gave me anything. The logs just said <date> <time> calling 'state.highstate'... (or 'state.highstate -l debug).
I did figure out after reinstalling and doing things one thing at a time that this error triggers only after my dom0 states, which is weird since it’s all cosmetic: adding a couple programs, setting Vim as default editor, WM tweaks, setting a theme, etc. I’m going to reinstall again and pinpoint which one it is. I’ll update then.
1 Like
Post the sls files.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
What about this one? Is it maybe a template imported from R4.2?
I figured it out. I have the ‘clear’ command in my dom0 root .bashrc because I want my terminal cleared when I switch to root. Running states fails when the command is present and works fine when it’s commented out. This should be reproducible as I’ve confirmed with a fresh, updated R4.3. (add ‘clear’ to the end of .bashrc and run a state).
It sounds lilke an upstream problem, but why does Salt care about bash? isn’t it coded in python? They’ve got to be insane, making an entire configuration stack depend on an interactive shell.
Not confirmed by me. States run just fine with clear in dom0 root’s .bashrc.
You will have to look elsewhere and (I suspect) for a series of factors.
What template are you using for default-mgmt-dvm?
Is it from 4.2 or is it a clean 4.3 template?
Post a state file that does not work for you.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.