[4.1] Issue upgrading to fedora 36 in place

I’m having trouble upgrading a machine to fedora-36. I was able to do this yesterday on another machine, so am confused why it isn’t working today.

Both machines are running 4.1

Here is the error I am getting (the Dropbox error, you can ignore).

[user@fedora-36 ~]$ sudo dnf --releasever=36 distro-sync --best --allowerasing
1Password Stable Channel                        2.5 kB/s | 1.9 kB     00:00    
Dropbox Repository                               11 kB/s |  25 kB     00:02    
Errors during downloading metadata for repository 'Dropbox':
  - Status code: 404 for http://linux.dropbox.com/fedora/36/repodata/repomd.xml (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'Dropbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Fedora 36 - x86_64                              7.6 MB/s |  81 MB     00:10    
Fedora 36 openh264 (From Cisco) - x86_64        1.3 kB/s | 2.5 kB     00:01    
Fedora Modular 36 - x86_64                      1.1 MB/s | 2.4 MB     00:02    
Fedora 36 - x86_64 - Updates                    3.5 MB/s |  20 MB     00:05    
Fedora Modular 36 - x86_64 - Updates            543 kB/s | 2.2 MB     00:04    
Qubes OS Repository for VM (updates)            411  B/s | 169  B     00:00    
Errors during downloading metadata for repository 'qubes-vm-r4.0-current':
  - Status code: 404 for https://yum.qubes-os.org/r4.0/current/vm/fc36/repodata/repomd.xml (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'qubes-vm-r4.0-current': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Can anyone suggest anything? The error relating to 4.0 seems odd.

It seems you still use the 4.0 repo, fedora 36 is not available in it that’s why you’re not able to get any metadata.

Since you use 4.0, I suppose this VM is coming from a backup or an in place upgrade from 4.0.
You will need to run this script before doing anything to convert it to the 4.1 release. Then you should be able to upgrade it to Fedora 36 without issues.

I am running 4.1

I have no idea why there are calls to 4.0 resources.

You use 4.1 but the VMs can still be based on 4.0 repos. You get that now because Fedora 36 is not available in the 4.0 repo, Fedora 35 is.

Odd - how do I go about letting fedora know about 4.1?

You should download and run the script I provided, it will replace the repo and everything that need to be switched to 4.1.

wonderful - not sure how I missed your first mention of it.
ta

Don’t forget to reboot the VM after you are done with the script, then proceed with the upgrade.

will do - thanks.
And yes, I brought fedora (prob 34) with me when I did the upgrade as I really didn’t want to have to go and configure the template to make it the way it was before.

If you have some StandaloneVMs, you may have to upgrade them too, including Debian if you use it.