Thank you for pointing this out. the one liner solution in
https://github.com/QubesOS/qubes-issues/issues/6188#issuecomment-726373728
(as applied to the default management template) fixed things for me.
On Friday, November 13, 2020 at 9:10:54 PM UTC+1 Ludovic Bellier wrote:
>
> Le 13/11/2020 à
Le 13/11/2020 à 19:33, balin a écrit :
Ok. More detail:
When calling (as root and in dom0):
qubesctl --target=fedora-32 state.highstate,
I get
fedora-32: ERROR (exit code 20, details in
/var/log/qubes/mgmt-fedora-32.log)
The relevant part in the referenced log reads:
...
balin schrieb am Freitag, 13. November 2020 um 19:33:36 UTC+1:
> Ok. More detail:
>
> When calling (as root and in dom0):
> qubesctl --target=fedora-32 state.highstate,
> I get
> fedora-32: ERROR (exit code 20, details in
> /var/log/qubes/mgmt-fedora-32.log)
>
> The relevant part in the
Ok. More detail:
When calling (as root and in dom0):
qubesctl --target=fedora-32 state.highstate,
I get
fedora-32: ERROR (exit code 20, details in
/var/log/qubes/mgmt-fedora-32.log)
The relevant part in the referenced log reads:
2020-11-13 19:27:51,237 calling 'state.highstate'...
