Bug 1648142

Summary: dnf does not see packages to update (unless clean all first)
Product: [Fedora] Fedora Reporter: George <ggr.seaton>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: chepioq, dmach, mblaha, mhatina, packaging-team-maint, rpm-software-management, vmukhame
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: 2018-11-23 01:12:58 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 Flags
example dnf update no packages none

Description George 2018-11-08 22:15:11 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. dnf update (no packages to update)
2. dnf clean all
3. dnf update  (packages now available to update)

Actual results:no packages to update


Expected results: packages to update (without using clean all first)


Additional info:
Comment 1 George 2018-11-08 22:18:27 UTC 
Created attachment 1503512 [details]
example dnf update no packages
Comment 2 Marek Blaha 2018-11-09 10:40:39 UTC 
Hi, are you able to reproduce it? I suspect this bug is related to (or may be is a duplicate of) https://bugzilla.redhat.com/show_bug.cgi?id=1648274
If that is the case, "dnf clean all" doesn't matter and running "dnf update" twice should be enough to reproduce the error.
Comment 3 George 2018-11-23 01:11:17 UTC 
Hi,
Yes it is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1648274
I hadn't tried running it twice.
Comment 4 George 2018-11-23 01:12:58 UTC 

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