Project

General

Profile

Defect #123

Handle DNS errors and other network failures

Added by Deoren Moor over 3 years ago. Updated about 3 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
RHEL - All
Target version:
Start date:
01/31/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
Resolution:

Description

Output sent to me via cron email:

/etc/cron.daily/email_updates:

https://cdn.redhat.com/content/dist/rhel/server/5/5Server/x86_64/cf-tools/1/os/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Trying other mirror.
https://cdn.redhat.com/content/dist/rhel/server/5/5Server/x86_64/rhev-agent/3/os/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Trying other mirror.
https://cdn.redhat.com/content/dist/rhel/server/5/5Server/x86_64/os/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Trying other mirror.
SQL error: near "Temporary": syntax error

The email notification contained a body that looked like this:

-3,-'Temporary

Hostname: X.X.X

IP Address(es):
----------------------------------
X.X.X.X

My first thought is that this situation should be treated the same as if there were no updates at all and not reported. Or at the very least let cron catch the errors and skip sending an email notification. That way whatever ticketing system that catches the emails won't create invalid tickets.

History

#1 Updated by Deoren Moor about 3 years ago

  • Target version changed from 0.2 to 0.4

Also available in: Atom PDF