Upgrade R4.1 --> R4.2, Cannot Complete Stage 1 (updating template and standalone VMs)

User Support General
1

I’m having some issues upgrading from 4.1 to 4.2. Every time I attempt to use

sudo qubes-dist-upgrade --all-pre-reboot -y

, I get some issues. Output looks like this:

---> (STAGE 1) Updating Templates VMs and StandaloneVMs...
whonix-gw-16: OK
whonix-ws-16: OK
<user-created-VM-1>: ERROR (exit code 20, details in /var/log/qubes/mgmt-<user-created-VM-1>.log
<user-created-VM-2>: ERROR (exit code 20, details in /var/log/qubes/mgmt-<user-created-VM-2>.log

This happens for multiple VMs I’ve created, and trying again sometimes gets some of them to be OK but not always. I can delete some of these and proceed while restoring backup data later, but there are a few that I really don’t want to delete. I really just want to upgrade in place.

The log messages boil down to failing to get release files for debian/whonix-based VMs (connection refused) or failed to download metadata for repo 'fedora'. Annoying stuff.

Has anyone seen this yet?

2

The issues that I’m seeing appear to be connection issues. The logs for my whonix-ws-16 VMs that are failing consistently have the following:

E: failed to fetch tor+https://deb.debian.org/debian/dists/bullseye/InRelease  Could not connect to 127.0.0.1:9050 (127.0.0.1). - connect (111: Connection refused)
E: failed to fetch https://deb.qubes-os.org/r4.1/vm/dists/bullseye/InRelease Something wicked happened resolving 'deb.qubes-os.org:https' (-4 - Non-recoverable failure in name resolution)