Bug 1080617

Summary:	cron job `foreman-rake reports:summarize` results in "rake aborted! getaddrinfo: Name or service not known"
Product:	Red Hat Satellite	Reporter:	Jan Hutař <jhutar>
Component:	Installation	Assignee:	Dominic Cleal <dcleal>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	bbuckingham, bkearney, dcleal, greartes, tcaspy
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/5824
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-20 11:57:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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):
Satellite-6.0.3-RHEL-6-20140321.2


How reproducible:
always


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 $?
1


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


Additional info:
This was initially reported as:
  http://projects.theforeman.org/issues/4833

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

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

production:
  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 ***