Bug 1392252 - mediawriter prints many messages that it can not download releases.json
Summary: mediawriter prints many messages that it can not download releases.json
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mediawriter
Version: 24
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-06 23:21 UTC by Michael
Modified: 2016-11-07 11:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 11:16:32 UTC
Type: Bug


Attachments (Terms of Use)

Description Michael 2016-11-06 23:21:21 UTC
Description of problem:

mediawriter prints the following message dozens of times to the console:

Warning: Was not able to fetch new releases: "Error transferring https://fedoraproject.org/releases.json - server replied: Not Found" Retrying in 10 seconds. ((null):0, (null))
Warning: Error QNetworkReply::NetworkError(ContentNotFoundError) reading from QUrl("https://fedoraproject.org/releases.json") : "Error transferring https://fedoraproject.org/releases.json - server replied: Not Found" ((null):0, (null))


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

mediawriter-4.0.0-2.fc24.x86_64

How reproducible:

always

Steps to Reproduce:
1. run mediawriter from commandline
2. observe the unable to download releases.json message that it prints every few seconds
3. 

Actual results:


Expected results:

The server at fedoraproject.org is returning 404 over https, so the resource is not there. It doesn't make sense for mediawriter to keep trying to find it indefinitely, it's just pointless network traffic.

Additional info:

wget agrees that releases.json does not exist. So either this is a bug against mediawriter, or the releases.json resource should be restored at https://fedoraproject.org/releases.json

Comment 1 Martin Bříza 2016-11-07 11:16:32 UTC
Hello,
this is just a temporary issue - the file will be in place for F25 release. Until then, I apologize for the unnecessary traffic. However, it doesn't make sense to handle getting 404 because the error is going to be in place only for a few days.


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