Bug 1692423

Summary: 100% CPU usage regression
Product: [Fedora] Fedora Reporter: Vitaly <vitaly>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: alalexey, dmach, ego.cordatus, elxreno, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, taocrismon, vmukhame, zawertun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-28 11:39:54 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:

Description Vitaly 2019-03-25 15:19:45 UTC 
Description of problem:
100% CPU usage during downloading packages, updates or repo metadata.

Version-Release number of selected component (if applicable):
dnf-4.2.1-1.fc29.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Run dnf update --refresh.
2. Check CPU usage using top/htop.
3.

Actual results:
100% CPU usage.

Expected results:
Normal CPU usage.

Additional info:
Version dnf-4.1.0-1.fc29 works fine.
Comment 1 Michael 2019-03-25 18:33:18 UTC 
Confirm. Same problem on Fedora 29 (dnf-4.2.1-1.fc29.noarch).
Comment 2 Artem 2019-03-25 18:36:28 UTC 
Same here. 100% load one CPU core.

OS:
  Fedora 30.

Version-Release number of selected component (if applicable):
  dnf-4.2.1-1.fc30
Comment 3 Yaroslav Sidlovsky 2019-03-25 18:44:10 UTC 
I can reproduce this bug with 100% probability after running `dnf clean all`.

Fedora 29 x86_64, dnf-4.2.1-1.fc29.
Comment 4 Aleksei Aleshin 2019-03-26 08:25:37 UTC 
I have the same issue. dnf-4.2.1-1.fc29
Comment 5 Artem 2019-03-28 10:22:09 UTC 
This update fixes this issue for me https://bodhi.fedoraproject.org/updates/FEDORA-2019-b504d6ad8f
Comment 6 Vitaly 2019-03-28 11:39:54 UTC 

*** This bug has been marked as a duplicate of bug 1691856 ***