Dom0 update error (Converting database from bdb to sqlite backend)

[load...@gmail.com]

Hi,

Few days ago I decided to delete templates which I do not use anymore (whonix-ws-14 and whonix-gw-14).
I did this like it said on this page https://www.qubes-os.org/doc/templates/

Today, when I tried to update my Dom0 I got this:

$ sudo qubes-dom0-update
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
warning: Converting database from bdb to sqlite backend
Invalid configuration value: failovermethod=priority in /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Fedora 25 - x86_64                              8.1 MB/s |  50 MB     00:06   
Fedora 25 - x86_64 - Updates                    5.7 MB/s |  24 MB     00:04   
Qubes Dom0 Repository (updates)                 2.1 MB/s | 2.0 MB     00:00   
determining the fastest mirror (14 hosts).. done.--  B/s |   0  B     --:-- ETA
Qubes Templates repository                      2.2 kB/s | 5.9 kB     00:02   
Dependencies resolved.
Nothing to do.
Complete!
No packages downloaded
Qubes OS Repository for Dom0                     22 MB/s |  26 kB     00:00


Could anyone know how to fix it?

[awokd]

load...@gmail.com:

> Configuration: OptionBinding with id "failovermethod" does not existInvalid

> configuration value: failovermethod=priority in
> /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo;

> Configuration: OptionBinding with id "failovermethod" does not existFedora

In a sys-firewall terminal session, make a backup copy of the file it's
complaining about
(/var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo), then edit it.
Remove the value it's complaining about (failovermethod=priority). Save
and try again.

If it still fails, you might want to create a fresh sys-firewall, or
change your UpdateVM to point to a different AppVM.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

[load...@gmail.com]

On Monday, May 10, 2021 at 10:06:10 PM UTC+3 awokd wrote:

load...@gmail.com:

In a sys-firewall terminal session, make a backup copy of the file it's
complaining about
(/var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo), then edit it.
Remove the value it's complaining about (failovermethod=priority). Save
and try again.

 

Unfortunately the '/var/lib/qubes/dom0-updates/' completely empty in sys-firewall.
 

If it still fails, you might want to create a fresh sys-firewall, or
change your UpdateVM to point to a different AppVM.

I tried with sys-net and also I tried with new netvm, but still have this error.
 

[awokd]

load...@gmail.com:

> On Monday, May 10, 2021 at 10:06:10 PM UTC+3 awokd wrote:

> Unfortunately the '*/var/lib/qubes/dom0-updates/*' completely empty in

> sys-firewall.
>
>
> If it still fails, you might want to create a fresh sys-firewall, or
>> change your UpdateVM to point to a different AppVM.
>>
>
> I tried with sys-net and also I tried with new netvm, but still have this
> error.

In dom0, check the files in /etc/yum.repos.d for the problem value.
Could possibly be copying them from there.

[load...@gmail.com]

On Wednesday, May 12, 2021 at 10:00:16 PM UTC+3 awokd wrote:

load...@gmail.com:
> On Monday, May 10, 2021 at 10:06:10 PM UTC+3 awokd wrote:


In dom0, check the files in /etc/yum.repos.d for the problem value.
Could possibly be copying them from there.

I removed the value it's complaining about (failovermethod=priority). And nothing changed, the same error. Everytime when I save and try update again I see this 'failovermethod=priority' in the file 'yum.repos.d'.

So I tried the fresh sys-firewall and tried to change UpdateVM on sys-net and nothing changed :(

[unman]

Then you simply have not deleted the entry from every file in dom0.

In any case it's a warning and harmless. Also a fix is in the pipeline.
It's always good practive to check that your problem isnt already covered
- it **has** been covered here the Forum, and also at github in the
issue tracker - #6581, and comes up with a trivial search.

[load...@gmail.com]

Thank you for your help. I deleted the entry from every file in /var/lib/qubes/dom0-updates/etc/yum.repos.d/ (not only from fedora-updates.repo) and it helps.

[Ulrich Windl]

After reading this, I tried to find the issue, starting at the Qubes OS
main page. Unfortunately you'll have to follow several links starting
from the "Team" link until you get there.

I wonder:
* Is it possible to add some more direct links for "Search known issues"?
* Maybe also add shortcuts for "Issues recently reported", "Issues
recently fixed", and maybe "'popular' issues" (like those being opened
many times; unsure if that's possible)

>

[unman]

On Wed, May 26, 2021 at 04:11:44PM +0200, Ulrich Windl wrote:
> On 5/14/21 3:22 PM, unman wrote:
> > On Fri, May 14, 2021 at 05:30:30AM -0700, load...@gmail.com wrote:
> > > On Wednesday, May 12, 2021 at 10:00:16 PM UTC+3 awokd wrote:
> > >
> > > > load...@gmail.com:
> > > > > On Monday, May 10, 2021 at 10:06:10 PM UTC+3 awokd wrote:
> > > >
> > > >
> > > > In dom0, check the files in /etc/yum.repos.d for the problem value.
> > > > Could possibly be copying them from there.
> > > >
> > >
> > > I removed the value it's complaining about (failovermethod=priority). And
> > > nothing changed, the same error. Everytime when I save and try update again
> > > I see this 'failovermethod=priority' in the file 'yum.repos.d'.
> > >
> > > So I tried the fresh sys-firewall and tried to change UpdateVM on sys-net
> > > and nothing changed :(
> > >
> >
> > Then you simply have not deleted the entry from every file in dom0.
> >
> > In any case it's a warning and harmless. Also a fix is in the pipeline.
> > It's always good practive to check that your problem isnt already covered
> > - it **has** been covered here the Forum, and also at github in the
> > issue tracker - #6581, and comes up with a trivial search.
>
> After reading this, I tried to find the issue, starting at the Qubes OS main
> page. Unfortunately you'll have to follow several links starting from the
> "Team" link until you get there.

I wouldn't start from there.

ddg "qubes issues failovermethod" takes me straight to it, as does
"failovermethod=priority error".

"failovermethod=priority" takes you directly to the Red Hat bugzilla
where the issue is discussed and resolved.

>
> I wonder:
> * Is it possible to add some more direct links for "Search known issues"?
> * Maybe also add shortcuts for "Issues recently reported", "Issues recently
> fixed", and maybe "'popular' issues" (like those being opened many times;
> unsure if that's possible)
>

Where do you think these links would be helpful?

[Ulrich Windl]

Close to the home page; maybe in the top navigation bar under "Support"
(does not exist yet, but could target at
https://www.qubes-os.org/support/), even though people might be afraid
of the traffic it may create ;-)

>