Qubes-dom0-update strange message: Invalid configuration value: failovermethod=priority

User Support
1

Hello,

I am getting this weird message when I run the terminal command for updating dom0:

sudo qubes-dom0-update
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
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
Last metadata expiration check: 0:28:48 ago on Wed May  5 09:30:00 2021.
Dependencies resolved.
Nothing to do.
Complete!
No packages downloaded

Does anybody have an idea about what is going on here ?

Cheers

2

(made the title a bit more specific to reflect the situation. Feel free to change if you feel it could be betters summarized)

3

Update: it seems to have something to do with the latest Fedora 33 updates (Fedora 33 is my current default template).

I reinstalled this template following the procedure described here: How to Reinstall a TemplateVM | Qubes OS

Then, without updating this freshly reinstalled template, I ran sudo qubes-dom0-update again, and the error messages I described above did not appear.

Finally, I updated the reinstalled template, and ran sudo qubes-dom0-update once more, and the error messages appeared again.

4

I have the same problem today.

I don’t know if it’s related but yesterday I switched sys-firewall and sys-net to debian 10 and I had this problem this morning. So I switched back to fedora 33 but the problem remained.

So the updates of dom0 and fedora 33 are impossible…
…and this is far beyond my competence :roll_eyes:

Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
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
Warning: Enforcing GPG signature check globally as per active RPM security policy (see 'gpgcheck' in dnf.conf(5) for how to squelch this message)
Qubes Dom0 Repository (updates)                 0.0  B/s |   0  B     03:02    
Errors during downloading metadata for repository 'qubes-dom0-current':
  - Curl error (28): Timeout was reached for https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink [Failed to connect to yum.qubes-os.org port 443: Connection timed out]
Error: Failed to download metadata for repo 'qubes-dom0-current': Cannot prepare internal mirrorlist: Curl error (28): Timeout was reached for https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink [Failed to connect to yum.qubes-os.org port 443: Connection timed out]```
5

Known bug. Harmless. Fix on the way:

6

Tip: In the future, try searching the issue tracker (both open and closed issues) for a key word from your error message (in this case, e.g., “failovermethod”), and you will be able to easily find these issues:

https://github.com/QubesOS/qubes-issues/issues?q=failovermethod

1 Like
7

The “failovermethod” message does not interfere with updates at all. It is just a harmless warning message that does not actually do anything.

Rather, your inability to update is a completely separate thing, likely due to the current outage: Yum.qubes-os.org outage (updates not working)

8

Thanks, I thought it was, but I preferred asking just to be sure…

9

Thanks for that as well; I will remember it in useful times :wink:

10

just got the latest qubes update, sadly this is still broken, fwiw , the multi line failover method stuff

       >  $ sudo qubes-dom0-update --clean

    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
    Warning: Enforcing GPG signature check globally as per active RPM security policy (see 'gpgcheck' in dnf.conf(5) for how to squelch this message)
    0 files removed
    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
    Warning: Enforcing GPG signature check globally as per active RPM security policy (see 'gpgcheck' in dnf.conf(5) for how to squelch this message)
    Fedora 25 - x86_64                              2.3 MB/s |  50 MB     00:22    
    Fedora 25 - x86_64 - Updates                    2.1 MB/s |  24 MB     00:11    
    Qubes Dom0 Repository (updates)                 262 kB/s | 1.3 MB     00:05    
    determining the fastest mirror (14 hosts).. done.--  B/s |   0  B     --:-- ETA
    Qubes Templates repository                      1.2 kB/s | 5.9 kB     00:05    
    Last metadata expiration check: 0:00:01 ag
    Dependencies resolved.
    Nothing to do.
    Complete!
    No packages downloaded
    No updates available

rpm.x86_64 4.14.2.1-5.fc25 @qubes-dom0-cached
rpm-build-libs.x86_64 4.14.2.1-5.fc25 @qubes-dom0-cached
rpm-libs.x86_64 4.14.2.1-5.fc25 @qubes-dom0-cached
rpm-plugin-selinux.x86_64 4.14.2.1-5.fc25 @qubes-dom0-cached
rpm-plugin-systemd-inhibit.x86_64 4.14.2.1-5.fc25 @qubes-dom0-cached
rpm-sign-libs.x86_64 4.14.2.1-5.fc25 @qubes-dom0-cached

…so just be patient keep waiting ?

11

The message tells you what to do.
If you follow the instructions in that message you will see how to
squelch the failover message, which is a warning not an error.
Run man dnf.conf in whatever qube you are using as the dom0 update
qube. (If you don’t know you can check with qubes-prefs updatevm)`

12

^

13

hmm, the warnings I thought were 2 separate issues.
As they appeared 1st with just gpgcheck with the RPM patching that had to be done.
Then later the failovermethod, which swore I read was going to be fixed with the next “dom0” update.

yeah my updatevm is sys-firewall, based on a Fedora-33 template, so I guess I try to fix something in the template or in the app-based vm or both ?

14

The message tells you what to do
see 'gppcheck' in dnf.conf(5) for how to squelch this message.)

These have already been explained in the Forum, but to check for
yourself:
You need to run man dnf.conf in sys-firewall, read the instructions
under the gpgcheck heading, and carry them out.