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.
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.
Hi,
I have the same issue as JustAnotherQubesUser, but errors occur during the execution of the script
Job for qubes-qrexec-agent.service failed because a timeout was exceeded.
See "systemctl status qubes-qrexec-agent.service" and "journalctl -xeu qubes-qrexec-agent.service" for details.
warning: %posttrans(qubes-core-qrexec-vm-4.1.18-1.fc35.x86_64) scriptlet failed, exit status 1
Error in POSTTRANS scriptlet in rpm package qubes-core-qrexec-vm
Running scriptlet: qubes-core-agent-4.1.37-1.fc35.x86_64 253/253
Running scriptlet: qubes-gui-agent-4.1.26-1.fc35.x86_64 253/253
Running scriptlet: xen-runtime-4.15.3-4.fc35.x86_64 253/253
ls: cannot access '/usr/lib/xen': No such file or directory
I remember having this issue with one of my StandaloneVM a long time ago, I don’t really remember how I resolved it. In case you didn’t clone the VM beforehand, you could try to revert the root volume with qvm-volume:
Hi,
Thank you for your help.
I have cloned the VM before hte upgrade, so I still have the previous version (fedora 35).
But I’ve deleted the new one and re-clone and retry to upgrade but everytime, it fails as shown in my screenshots…
What was the whole upgrade process you did? I see you went from “35” to “36” so I assume you tried to in-place upgrade the VM. Where does that template come from (installed in 4.0 or 4.1)?
When I installed Qubes at first, it came with fedora 30.
I cloned it and upgraded it to 31, and repeated these 2 actions for 32, 33, 34 and 35 (using dnf --releasever= distro-sync --best --allowerasing).
As it failed for 36, I tried your script…
I remember getting this error with that one standalone because I manually edited the repos from 4.0 to 4.1. I used the script on at least 10 StandaloneVM without getting this again so it should work for you too.
Make sure to run the script first, let it finish completely then turn off the template. Boot it up again and then do the upgrade from 35 to 36.
Is it normal to have these errors during the script execution ?
Job for qubes-qrexec-agent.service failed because a timeout was exceeded.
See “systemctl status qubes-qrexec-agent.service” and “journalctl -xeu qubes-qrexec-agent.service” for details.
warning: %posttrans(qubes-core-qrexec-vm-4.1.18-1.fc35.x86_64) scriptlet failed, exit status 1
Error in POSTTRANS scriptlet in rpm package qubes-core-qrexec-vm
Running scriptlet: qubes-core-agent-4.1.37-1.fc35.x86_64 253/253
Running scriptlet: qubes-gui-agent-4.1.26-1.fc35.x86_64 253/253
Running scriptlet: xen-runtime-4.15.3-4.fc35.x86_64 253/253
ls: cannot access ‘/usr/lib/xen’: No such file or directory