Fedora-29 update does not work

[Claudio Chinicz]

Hi All,

I'm getting notification that I need to update Fedora-29 (Qubes 4.0.1),
I do it but it keeps asking to update.

On Qubes manager all VMs based on Fedora-29 template show they need to
restart because I've updated Fedora-29, although it keeps asking to update.

I've even updated it manaully (opened terminal and issued sudo dnf
update/upgrade) and it seems updated, but still Qubes thinks it needs to
update.

Any insights?

Thanks,

Claudio Chinicz

[Claudio Chinicz]

Hi again,

After a long time, the issue returned and for almost I see the update
icon on the upper right corner indicating I need to update Fedora 29
template.

When I try to update, I get an error saying "Failed to synchronize cache
for repo \ 'fedora-modular\'\n ..... Comment: System is already
up-to-date\n".

When I try to update using command line I get this error message:

sudo dnf update

Error: Failed to synchronize cache for repo 'fedora-modular'

Anyone else has been having this same problem? any ideas how to clear it?

Thanks in advance,

Claudio

[Jon deps]

what does dom0
$qubes-prefs say for updateVM ?


did you happen to recently change anything? I suppose you are aware
that the Qubes Manager sometimes won't get rid of the little green
arrow even though your up to date ? If your saying that you
closed your Fedora-29 template and then closed all your AppVM Qubes and
restarted them and still see the recycle green circle on them, I've
never heard of that problem before .....


have you ever done

$sudo dnf upgrade vs update

[Claudio Chinicz]

Hi,

I've just tried and it successfully updated both Debian 9 and Fedora 29
through the qubes updater.

Answering your question:

1. updatevm is through sys-firewall
2. yes, I'd tried both sudo dnf update / upgrade with on fedora and
debian command lines

Thank you,

Claudio

[FenderBender]

Newly posting on google.groups, Qubes user since 3.0.
======================================================
I have had a lot of glitches with Qubes. 4.x Fedora updates too - between that and the better array of apps, I find the Debian VM's to be more useful. Note that with debian based systems (at least up until the most recent updated iso) it is necessary to do a sudo apt-get dist-upgrade or the Qubes equivalents (on new installs). Perhaps there is an equivalent distinction in the fedora dnf system.

In sum, I have found that there is more than one way to update/upgrade the debian templates aside from the published method, and it would not be surprising if various tweaks and work arounds are needed for fedora. I will watch this thread and check my system as in the long run we need good updatable fedora templates as they are possibly more secure, and we need a fallback system should the various debian bugs create more vulnerability than we can live with.

[cchi...@gmail.com]

Hi,

I've found the issue. I have separate sys-net for cabled eth and sys-net-wifi. Today I tried to update and it failed but I happened to see that sys-net was started (I was on wifi and had turned sys-net off).

I then connected through cable and the update was successful.

Is there a way to setup that Fedora (and Debian) updates happen through a specific network, like my sys-net-wifi?

Thanks in advance

[awokd]

cchi...@gmail.com:

> I've found the issue. I have separate sys-net for cabled eth and sys-net-wifi. Today I tried to update and it failed but I happened to see that sys-net was started (I was on wifi and had turned sys-net off).
>
> I then connected through cable and the update was successful.
>
> Is there a way to setup that Fedora (and Debian) updates happen through a specific network, like my sys-net-wifi?
>
> Thanks in advance
>

Edit /etc/qubes-rpc/policy/qubes.UpdatesProxy, and update the Template
line. You'll probably also want to change where dom0 updates in
qubes-prefs updatevm.

[cchi...@gmail.com]

Hi,

Thanks a lot, I've updated /etc/qubes-rpc/policy/qubes.UpdatesProxy and will test next time an update is available.

I've issued "qubes-prefs updatevm" on dom0 terminal and the answer was "sys-firewall-wifi", which is my firewall VM and not sys-net or sys-net-firewall. Should it work over the wifi? I do not remember having updated qubes-prefs updatevm when I created sys-net-wifi/sys-firewall-wifi.

Regards

[awokd]

cchi...@gmail.com:

It should work. You can test with "sudo qubes-dom0-update". If it does,
you might want to change your templates to update from the same place by
editing that updates proxy file.