QubesOS
Qubes OS Global Config section for setting exceptions for template update proxies includes an app qube in the template list
Qubes OS release
4.2
Brief summary
Qubes OS Global Config allows to set exceptions for update proxys of templates. For whatever reason one of my AppVMs can be chosen in the template-exception list is well (is not standalone, does not provide Network, no service enable in qube settings)
Steps to reproduce
Don't know. need help to find out
Expected behavior
Templates have a default update proxy and an other update proxy can be defined by exceptions (and in fact Standalone VMs should be as well #8851), but not AppVMs and NetVMs
Actual behavior
One (and only one) non-standlone, not providing Network, no service enable in qube settings qube can be selected for whatever reason. It is not lexicographically the first (but the second)
Are you sure it's an AppVM? The current logic for "needs UpdateProxy" is:
- AdminVM and AppVM: always False
- has a template: always False
- networked: always False
- the rest: True
Could you check the qvm-prefs for this VM? I'm interested in whether it has template and what class it has.
Also this might be accidentally fixed by https://github.com/QubesOS/qubes-desktop-linux-manager/pull/182 together with #8851
qubes-manager.noarch 4.2.8-1.fc37 still has this. I verified again that the settings page of the mentioned qubes says "Type: AppVM"