Bug 1599102
| Summary: | DNF, at certain times, takes a couple minutes to start up | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Scott Cohen <yetoohappy> | ||||||||
| Component: | dnf | Assignee: | Marek Blaha <mblaha> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 28 | CC: | dmach, mblaha, mhatina, packaging-team-maint, rpm-software-management, vmukhame | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-07-16 11:17:01 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: |
|
||||||||||
Created attachment 1457325 [details]
My /etc/dnf/dnf.conf
Please, can you provide us with /var/log/dnf.librepo.log? Created attachment 1457561 [details] The dnf.librepo.log from July 8th. (In reply to Marek Blaha from comment #2) > Please, can you provide us with /var/log/dnf.librepo.log? This is the the librepo log from July 8th. *** This bug has been marked as a duplicate of bug 1598554 *** |
Created attachment 1457324 [details] This is the output of dnf doing an update with the -yv switches and timed. Description of problem: Either right after Fedora boots (not verified for shutdown but is for reboot)) or after a long period of inactive use of the DNF command, the command takes a couple minutes to start and then go onto its routines. The part where DNF takes the longest is after it outputs the plugins it loaded. The following is a snippet from the output which exemplifies this erroneous behavior (I forgot if the text: cachedir: /var/cache/dnf showed up during the following snippet or after): Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync, system-upgrade DNF version: 2.7.5 Version-Release number of selected component (if applicable): dnf-2.7.5-12.fc28 How reproducible: Almost after every boot and/or inactive use of the command. Steps to Reproduce: 1. Reboot machine or don't use the dnf command for several hours (in my experience 10 is a magic number) 2. Execute the dnf command once either of the conditions in 1 have been met. Actual results: It takes several minutes to start up dnf after execution of command. Expected results: Only a couple of seconds or less is to be experienced before the cache is read. Additional info: This occurs no matter what command is ran with dnf once the conditions, explained above, are met.