Bug 1080617 - cron job `foreman-rake reports:summarize` results in "rake aborted! getaddrinfo: Name or service not known"
Summary: cron job `foreman-rake reports:summarize` results in "rake aborted! getaddrin...
Status: CLOSED DUPLICATE of bug 1188346
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: Nightly
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Dominic Cleal
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-03-25 19:23 UTC by Jan Hutař
Modified: 2016-04-22 16:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-04-20 11:57:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5824 0 Normal Resolved Configure Rails email settings 2020-12-23 19:53:37 UTC

Description Jan Hutař 2014-03-25 19:23:12 UTC
Description of problem:
Cron job `foreman-rake reports:summarize` results in "rake aborted! getaddrinfo: Name or service not known" on default installation.

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

How reproducible:

Steps to Reproduce:
1. One of the cron jobs have:
   /usr/sbin/foreman-rake reports:summarize

Actual results:
# /usr/sbin/foreman-rake reports:summarize
rake aborted!
getaddrinfo: Name or service not known

Tasks: TOP => reports:summarize
(See full trace by running task with --trace)
# echo $?

Expected results:
On default installation, all should work - cron jobs should not produce errors periodically

Additional info:
This was initially reported as:

As per http://projects.theforeman.org/projects/foreman/wiki/Email_configuration I have configured this:

# cat /etc/foreman/email.yaml
# Outgoing email settings

  delivery_method: :sendmail

but that generates mails for root@$( hostname -d ) so they have permanent errors in my case, but I guess this can be configured somewhere as well.

Comment 1 RHEL Program Management 2014-03-25 19:44:48 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Dominic Cleal 2014-05-20 14:29:55 UTC
Created redmine issue http://projects.theforeman.org/issues/5824 from this bug

Comment 4 Tom Caspy 2015-01-11 09:57:59 UTC
this seems like it's a configuration issue - in redmine the bug reporter posted their email.yml which is the default one (which obviously won't work)

do we have a way to configure email in the installer, so a correct server will be defined?

Comment 5 Bryan Kearney 2015-04-20 11:57:59 UTC
Since this becomes an RFE for email configuration, I am keeping the RFE.. marking this as dupe.

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

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