Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 1RHEL 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.
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?
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 ***