Fedora template no longer supported 4.2.0-rc5

pjmbraet · December 3, 2023, 7:00am

After updating Qubes 4.2.0-rc4 to rc5 on Notebook NH5x_NH7xHP got this notification:

so did an in-place upgrade to Fedora 39, and get this notification:

After updating grub (sudo grub-mkconfig -o /boot/grub2/grub.cfg) and reboot:

The notification remains.
As you can see on the pictures, after updating there are two network icons. ¨cat /etc/qubes-release¨ in terminal says I am still on Qubes rc4 though i did the update normally so i should be on rc5. Also, when updating again in terminal i get this warning about datetime deprecated:
/usr/lib/python3.12/site-packages/salt/utils/jid.py:19: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
return datetime.datetime.utcnow()*
Okay, Qubes 4.2.0-rc4 worked just fine, after updating normally to 4.2.0-rc5 there are some new issues. I am not going to install a new fedora template. That would be too much work, reïnstalling all the software I use. That is why i always do an in place upgrade of the templates.

adw · December 3, 2023, 2:20pm

Appears to be this:

github.com/QubesOS/qubes-issues

Qubes Updater considers in-place upgraded qubes to be "no longer supported"

opened 09:42AM - 23 Nov 23 UTC

Minimalist73

T: bug C: manager/widget C: doc P: critical needs diagnosis C: updates affects-4.2

### Qubes OS release 4.2-rc4 ### Brief summary The new Qubes Updater …introduced [a new way](https://github.com/QubesOS/qubes-desktop-linux-manager/blob/main/qui/utils.py#L83-L95) to detect if a template or standalone qube is no longer supported. It works, but shows false positives for users who use the in-place upgrade method for their qubes. The "template-name" option in qvm-features retains its old value and Qubes Updater uses it to check if the system is EOL. ### Steps to reproduce Not really reproducible by itself, since it only happens to users who upgrade their templates/standalone qubes in-place. Can be artificially reproduced by changing the `template-name` value to an old template version: - `qvm-features fedora-38-xxx template-name fedora-35` ### Expected behavior No "no longer supported" message should appear in Qubes Updater qui if the qube runs a supported release. ### Actual behavior Say that some of my qubes are no longer supported (reported as "obsolete" in Qubes Updater itself) when they are fully upgraded to fedora-38. Running qvm-features on one of the affected template reports the following: ``` template-name fedora-35 template-epoch 0 template-version 4.0.6 template-release 202111131804 template-reponame qubes-templates-itl-testing template-buildtime 2021-11-13 19:14:50 template-installtime 2021-12-07 18:11:25 template-license GPL template-url http://www.qubes-os.org template-summary Qubes template for fedora-35 template-description Qubes template for fedora-35 ```

adw · December 3, 2023, 2:21pm

This has already been fixed in the code, but the fix will not be reflected in existing ISOs.

DVM · December 3, 2023, 2:24pm

The following command will fix your issue (in a dom0 terminal):

qvm-features fedora-39 template-name fedora-39

I had the same issue as well for multiple templates. The message will go away after you reboot or restart the widget.

pjmbraet · December 4, 2023, 4:10am

Thnx. After

The message was gone indeed, and then updated dom0 again, now i am really on Qubes release 4.2.0-rc5