Red Hat Bugzilla – Bug 1285473
metadata_timer_sync=0 does not stop metadata sync
Last modified: 2017-04-19 16:08:47 EDT
Description of problem:
I would like to prevent fedora from going on the network
without an explicit request, for various reasons
including security and cost.
dnf.conf states this for metadata_timer_sync:
Use 0 to completely disable automatic metadata synchronizing.
this is exactly what I have in dnf.conf, but
once in a while I still get notified about
package updates being available, I conclude
that dnf goes on the network to fetch the updates.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install fedora (tested kde spin)
2. set metadata_timer_sync=0
3. run dnf update to update everything
4. wait several days to new updated to land in fedora
prompt notifying user of new updates is displayed
no prompt until dnf sync is executed manually
Seems to be a regression in F23.
We cannot reproduce this behavior. We think that it runs on F23 correctly. When metadata_timer_sync=0 in /ets/dnf/dnf.conf , systemD runs dnf-makecache.service periodically, but it doesn't synchronize metadata. Even from dnf.log it is possible to see, that it is disabled (but it is necessary to read carefully - INFO Metadata timer caching disabled).
Anyway thanks for reporting.
Except it's still a problem in F25.
It appears to be caused by some "update applet" which disregards the setting and just calls "dnf check-update" (as in: not dnf-makecache.timer) every boot, even if I'm on mobile connection, paying for every megabyte. Awesome. NOT.