Bug 1339860 - Fedora 24 repository unable to locate cache data
Summary: Fedora 24 repository unable to locate cache data
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-repos
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-26 01:24 UTC by Ryan
Modified: 2016-06-21 09:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-21 09:05:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ryan 2016-05-26 01:24:40 UTC
Description of problem:

When running

#dnf install nano

I receive the error:

Error: Failed to synchronize cache for repo 'fedora'

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

Current

How reproducible:

Very

Steps to Reproduce:
1. run DNF makecache/install/update
2. wait for timeout
3. receive error

Actual results:

Error: Failed to synchronize cache for repo 'fedora'

Expected results:

cache to be updated successfully

Additional info:

when following the baseurl path to http://download.fedoraproject.org/pub/fedora/linux/releases/ it is noted there is an additional subfolder for every mirror (e.g. http://download.fedoraproject.org/pub/fedora/linux/releases/test/24_beta) if you uncomment and modify the baseurl it works. I am lodging this as an extension of https://ask.fedoraproject.org/en/question/88086/error-failed-to-synchronize-cache-for-repo-fedora/

Comment 1 Peter Robinson 2016-05-26 07:31:03 UTC
Try "dnf make clean; dnf update --refresh; dnf install nano"

Comment 2 Dennis Gilmore 2016-05-26 12:47:09 UTC
Also make sure that the date on your system is close to correct

Comment 3 Ryan 2016-06-21 08:09:01 UTC
issue is resolved, please close. there were some updated repos pushed with the correct path to updates.


Note You need to log in before you can comment on or make changes to this bug.