Bug 733081

Summary:	RFE: More verbose cron job output
Product:	[Fedora] Fedora	Reporter:	Michael Cronenworth <mike>
Component:	spamassassin	Assignee:	Warren Togami <wtogami>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	14	CC:	kevin, redhat-bugzilla, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-16 16:36:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Cronenworth 2011-08-24 16:50:27 UTC

Description of problem: When an update mirror is down the cron job output looks like sa-update had a problem. In reality sa-update may have gone to a second mirror and successfully applied an update. I have no idea if this is the case or not based on the cron job output as it stands now.


Version-Release number of selected component (if applicable):
spamassassin-3.3.2-1.fc14.x86_64


How reproducible: Any time there is an update failure.


Steps to Reproduce:
1. Block one of the mirrors in your firewall or hosts file (point to localhost)
2. Let sa-update run an update
3. Cron output will state the mirror had a read timeout. No idea if sa-update went to a second mirror or what.
  
Actual results:
http: GET http://daryl.dostech.ca/sa-update/asf/1160585.tar.gz request failed: 500 read timeout: 500 read timeout 


Expected results:
http: GET http://daryl.dostech.ca/sa-update/asf/1160585.tar.gz request failed: 500 read timeout: 500 read timeout 
"SpamAssassin has gone to a second mirror and has succeeded"
or
don't even print the read timeout if the update was successful by using a second mirror.

Additional info:
I've discussed this with upstream at length. Feel free to read the thread.
http://mail-archives.apache.org/mod_mbox/spamassassin-users/201108.mbox/%3C4E550492.10906@cchtml.com%3E

Comment 1 Fedora End Of Life 2012-08-16 16:37:03 UTC

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping