fedora-26-dvm always shows updates pending, can't delete it.

[cooloutac]

Upgraded to 4.0. was able to restore all my backup vms no problems.

Only issues i had was had to keep doing qvm-appmenus-sync on vms.

Another problem was I selected whonix as updatevm during installation, which meant fedora-26 didn't update. I believe this is a known issue?

I followed suggestion here: https://groups.google.com/forum/#!searchin/qubes-users/failed$20to$20synchronize$20cache$20%7Csort:date/qubes-users/gLqORddxb-Y/VEe-SNwCBAAJ and made all qubes update proxy entries changed from sys-whonix to sys-firewall.

But does this mean dom0 is not really using tor to update? Is whonix even using tor to update after doing this? I'm confused.

Also I managed to figure out how to created a new dvm template based off a cloned os template.

And i won't go into all the bugs with the qube-manager I'm sure they are known. Like organizing by vm type is not the same as in 3.2 and its very confusing having to keep refresh it.

But its driving me nuts that the default fedora-26-dvm always shows updates pending. and I don't know how to get rid of it. I even changed its template and it still shows updates pending and it won't let me delete altogether so I can just use my custom one.

Any solution to this?

Thanks

Rich.

[cooloutac]

also forgot to mention for some reason I had two sys-whonix. there was another sys-whonix (1) and its not something I backed up. happened after a dom0 update. I think I used testing. and tor stopped working. So I deleted all the sys-whonix and used the qubes stack to reinstall them and tor is now working again. Just found it strange.

Everything seems to be working ok besides the qube-manager issues and fedora-26-dvm being undeleteable. can't figure out what is using it. or how to get rid of the updates pending.

Thanks.

[awokd]

On Thu, March 29, 2018 4:34 pm, cooloutac wrote:
> Upgraded to 4.0. was able to restore all my backup vms no problems.

> made all qubes update proxy entries changed from sys-whonix to
> sys-firewall.
>
> But does this mean dom0 is not really using tor to update?

I think dom0 only looks at the UpdateVM setting in qubes-prefs for its
update location.

> Is whonix
> even using tor to update after doing this? I'm confused.

I believe it would not.

> But its driving me nuts that the default fedora-26-dvm always shows
> updates pending. and I don't know how to get rid of it. I even changed
> its template and it still shows updates pending and it won't let me
> delete altogether so I can just use my custom one.
>
> Any solution to this?

Not sure on this one, maybe one of the salt commands is needed?

[cooloutac]

yes, actually looks like dom0's update setting is totally separate so its probably using tor. https://github.com/QubesOS/qubes-issues/issues/3527

Not sure about whonix templates itself though? I guess I have to check that proxy file again.

According to another github i can't find right now, doesn't look like fedora will be able to update over tor any time soon using whonix. But according to the github above each template can use a specific updatevm in 4.0.

Also now my custom dvm is constantly showing updates pending in qubes manager. Once i update the template used for the dvm template, it constantly shows update pending.

[cooloutac]

Realized this only happens when using testing repo. Current repos don't have the pending updates on dvms issue.

[cooloutac]

did a -v and saw that it said metadata errors.

So sudo dnf clean metadata fixed the issue.