Hide Forgot
Description of problem: When I do a dnf upgrade, and there are no packages to upgrade, it can take up to a few minutes to finish, even after saying 'nothing to do'. The messages I see are that it is creating a completion cache, and I see a lot of disk activity. It also takes this time when there are packages to upgrade, after the upgrade is complete. Version-Release number of selected component (if applicable): # rpm -q libsolv dnf hawkey libsolv-0.6.19-2.fc25.x86_64 dnf-1.1.7-2.fc25.noarch hawkey-0.6.2-4.fc24.x86_64 How reproducible: every time Steps to Reproduce: 1. Have completion cache plugin installed 2. Do a dnf upgrade 3. Actual results: Takes a few minutes even when nothing to do Expected results: If nothing to do, quits immediately Additional info: All packages with dnf in name in rpm database: dnf-1.1.7-2.fc25.noarch dnf-conf-1.1.7-2.fc25.noarch dnf-plugins-core-0.1.19-1.fc25.noarch dnf-yum-1.1.7-2.fc25.noarch python2-dnf-1.1.7-2.fc25.noarch python3-dnf-1.1.7-2.fc25.noarch python3-dnf-plugins-core-0.1.19-1.fc25.noarch python3-dnf-plugins-extras-common-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-leaves-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-local-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-repoclosure-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-repograph-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-repomanage-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-rpmconf-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-show-leaves-0.0.12-2.fc24.noarch python3-dnf-plugins-extras-versionlock-0.0.12-2.fc24.noarch python-dnf-plugins-core-0.1.19-1.fc25.noarch If run with the flag --disableplugin=\*, the behavior is as expected. As soon as it sees there is nothing to do, it immediately exits. This is the output from a run without the --disableplugin=\* set. Nothing to do. DEBUG:dnf.plugin:Completion plugin: Generating completion cache... Complete! INFO:dnf:Complete! DDEBUG:dnf:Cleaning up. Contents of /etc/dnf/dnf.conf [main] gpgcheck=1 installonly_limit=6 clean_requirements_on_remove=False #clean_requirements_on_remove=True metadata_timer_sync=0 # 12 hours metadata_expire=43200 minrate=500 timeout=120 #debuglevel=10 keepcache=1 throttle=1000k #throttle=600k #errorlevel=5
Thanks for the tip about the --disableplugin=\* flag in the user email list.
completion plugin should at least write some message that it generates the cache. otherwise it's fine.
So it's normal for dnf to generate a completion cache when there is nothing to do? And that's what is taking all the time? What is the completion cache? Is it necessary? It's not really a big deal to wait the few minutes for it to be generated, but if it's not necessary, I'll just run with the --disableplugin=\* flag, and skip it.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Might be the local plugin to create a local repo; python3-dnf-plugins-extras-local-0.0.12-2.fc24.noarch See also https://github.com/rpm-software-management/dnf-plugins-extras/blob/master/doc/local.rst How about dedicatedly disabling it? BTW: Any chance to get rid of the post-install DDEBUG messages?
@Andreas That was a possibility, and I do have the plugins-extra package installed. But I have the local plugin disabled, and there is no local repository at /var/lib/dnf/plugins (the default location in the configuration file). The configuration files are in /etc/dnf/plugins. In that configuration directory, there is a conf file called debuginfo-install.conf. It seems to be enabled by default. Perhaps that is the source of your DDEBUG messages? I haven't tried disabling it.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
PR was created: https://github.com/rpm-software-management/dnf-plugins-core/pull/190 @Andreas There is opened bug for that debug info, I will take a look at it (https://bugzilla.redhat.com/show_bug.cgi?id=1284835)
It looks like that patch was rejected.
Interestingly enough, I was just running an update with dnf in rawhide yesterday, and after it had completed cleanup, and had finished running the post scripts for the packages that required it, it took about 20 minutes before it wrapped up. I checked what was happening and it was waiting on mandb to update its database after the package updates. Does it really have to wait for that? Could that be offloaded to a cron job, or is there information that dnf passes to mandb that is only available at update time? This was a large update, ~1500 packages, as I hadn't updated for a few weeks, so that probably dragged the time out also. I'm not sure if this is related to the problem I opened the ticket for.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.