Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1648274
Summary: | dnf fails to refresh expired metadata | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Hughes <tom> | ||||||
Component: | dnf | Assignee: | Marek Blaha <mblaha> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 29 | CC: | bitlord0xff, carl, chepioq, cvanewijk, dmach, george.seaton, gtwilliams, ilaurie, mblaha, mhatina, packaging-team-maint, petersen, pmatilai, rmy, robatino, roger.k.wells, rpm-software-management, vmukhame | ||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | dnf-4.1.0-1.fc29 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2019-02-21 02:56:52 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Tom Hughes
2018-11-09 10:05:26 UTC
*** Bug 1648142 has been marked as a duplicate of this bug. *** *** Bug 1655610 has been marked as a duplicate of this bug. *** Hi, I'm not sure if this is the same bug I think I'm experiencing, but if it is I guess you should give it a higher priority (new release/backporting fixes ...). Default `metadata_expire` is 7days, but after checking for updates dnf happily says (this is saved from one of dnf runs, I now always run it with `--refresh`): Last metadata expiration check: 16 days, 13:08:44 ago on Mon 17 Dec 2018 09:38:39 PM CET. Dependencies resolved. Nothing to do. Complete! And if you force it with `--refresh` it updates metadata and offers to update packages as well. I was experiencing this on multiple f29 systems. *** Bug 1669118 has been marked as a duplicate of this bug. *** Created attachment 1528471 [details]
First nothing to do and then Waiting for process with pid 3267 to finish.
Waiting for process means, that another process has locked cache / database. It could be for example dnf-makecache.timer, another dnf process, packagekit... Please, what version of dnf are you using ($ rpm -q dnf libdnf)? [cewijk@linux ~]$ rpm -q dnf libdnf dnf-4.0.9-2.fc29.noarch libdnf-0.22.3-1.fc29.x86_64 Created attachment 1534685 [details]
Dnf upgrade session report 4
libcomps-0.1.10-2.fc29 libdnf-0.26.0-1.fc29 dnf-plugins-core-4.0.4-1.fc29 dnf-plugins-extras-4.0.2-1.fc29 dnf-4.1.0-1.fc29 librepo-1.9.4-1.fc29 createrepo_c-0.12.1-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1fccede810 createrepo_c-0.12.1-1.fc29, dnf-4.1.0-1.fc29, dnf-plugins-core-4.0.4-1.fc29, dnf-plugins-extras-4.0.2-1.fc29, libcomps-0.1.10-2.fc29, libdnf-0.26.0-1.fc29, librepo-1.9.4-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1fccede810 createrepo_c-0.12.1-1.fc29, dnf-4.1.0-1.fc29, dnf-plugins-core-4.0.4-1.fc29, dnf-plugins-extras-4.0.2-1.fc29, libcomps-0.1.10-2.fc29, libdnf-0.26.0-1.fc29, librepo-1.9.4-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |