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

[Minimalist73]

Qubes OS release

4.2-rc4

Brief summary

The new Qubes Updater introduced a new way 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

[ben-grande]

Note that these features are set on package installation, not when modifying the qube from inside.

If this is a bug, it is in the documentation, maybe it should tell you to update the template-name, template-summary and template-description feature? I don't know if the other features should be changed.

But then it would also need to recommend you to set a new feature template-original-name or something like it, so you can know from which version you started doing in-place upgrades. This way the Updater could work with in-place upgrades.

[andrewdavidwong]

Another report on the forum: https://forum.qubes-os.org/t/fedora-template-no-longer-supported-4-2-0-rc5/22506

[kennethrrosen]

Note that these features are set on package installation, not when modifying the qube from inside.

If this is a bug, it is in the documentation, maybe it should tell you to update the template-name, template-summary and template-description feature? I don't know if the other features should be changed.

But then it would also need to recommend you to set a new feature template-original-name or something like it, so you can know from which version you started doing in-place upgrades. This way the Updater could work with in-place upgrades.

Confirming: Running qvm-features fedora-39 template-name fedora-39 or the like resolves the issues.

[avaaum]

does not work for me. the issue still persists.

[runephilosof-abtion]

does not work for me. the issue still persists.

I had to reboot after changing the template names to have the updater notice it.

[runephilosof-abtion]

According to https://forum.qubes-os.org/t/fedora-template-no-longer-supported-4-2-0-rc5/22506/4, it should be enough to restart the widget. But I don't know how to do that.

[andrewdavidwong]

Another user report: https://groups.google.com/d/msgid/qubes-users/ca442c50-7b31-4ea2-b27a-739fc31c7e65%40gmail.com

[sjvudp]

As I'm affected, too, I can tell:
qvm-features fedora-38 reports (among many other lines):

template-name                               fedora-36
template-epoch                              0
template-version                            4.0.6
template-release                            202205270243
template-reponame                           @commandline
template-buildtime                          2022-05-27 03:11:26
template-installtime                        2022-09-02 22:50:42
template-license                            GPL
template-url                                http://www.qubes-os.org
template-summary                            Qubes template for fedora-36
template-description                        Qubes template for fedora-36
updates-available                           
last-updates-check                          2024-01-19 22:21:28

So my guess is that one step in the template upgrade guide is missing ;-)

[qubesos-bot]

Automated announcement from builder-github

The package core-agent-linux has been pushed to the r4.3 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing trixie-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.3 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.3-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package core-agent-linux has been pushed to the r4.2 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing trixie-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package core-agent-linux has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package core-agent-linux has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component core-agent-linux (including package core-agent-linux) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update