Bug 1218353

Summary: [metadata] Failed to synchronize cache for repo
Product: [Fedora] Fedora Reporter: diegofernandez
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jsilhan, mjuszkie, mluscon, neatuovi, packaging-team-maint, pnemade, rholy, tim.lauridsen, vmukhame
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-28 14:35:18 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
/var/cache/dnf archive none

Description diegofernandez 2015-05-04 16:54:38 UTC 
Created attachment 1021810 [details]
/var/cache/dnf archive

Description of problem: I'm trying to use DNF, but any command I try result in the following error:
"Failed to synchronize cache for repo 'Dropbox' from 'http://linux.dropbox.com/fedora/22/': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried, disabling.
Error: Failed to synchronize cache for repo 'fedora' from 'https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64': Yum repo downloading error: Downloading error(s): repodata/025694bc7164bebf478246c5e2c80f9c3ea6891b12eafdb3864efe507cf3d600-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/6f30747a59d05cd7b75f31e0e3fc2a88f16a2fdd8fe84e09106edb9da0ed7b59-primary.xml.gz - Cannot download, all mirrors were already tried without success"


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


How reproducible: Any command as: dnf update, dnf install, dnf upgrade.

Additional info: When I installed Fedora 22 it was working fine. After reboot it gives me that error.
Comment 1 Marcin Juszkiewicz 2015-05-28 14:35:18 UTC 

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