Project

General

Profile

Feature #5824

Configure Rails email settings

Added by Dominic Cleal about 8 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1080617
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:
  1. /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)
  1. 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:

  1. cat /etc/foreman/email.yaml
  2. 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.


Related issues

Related to Foreman - Tracker #7585: Mail notifications trackerNew

Has duplicate Installer - Feature #10179: Add email configuration settings to installerDuplicate2015-04-17

History

#1 Updated by Dominic Cleal about 8 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from cron job `foreman-rake reports:summarize` results in "rake aborted! getaddrinfo: Name or service not known" to Configure Rails email settings
  • Category set to Foreman modules

This perhaps should include updating the default email.yml file distributed in core, please evaluate as a whole.

#2 Updated by Stephen Benjamin almost 8 years ago

#3 Updated by Stephen Benjamin almost 8 years ago

User contributed some documentation related to email.yml which is really useful:
https://github.com/theforeman/theforeman.org/pull/280/files

Is documentation sufficient for this issue or do we want to add some options to the installer to configure email.yml?

#4 Updated by Dominic Cleal almost 8 years ago

I'd like the installer to support it too, but the docs are very helpful indeed.

#5 Updated by Dominic Cleal over 7 years ago

  • Has duplicate Feature #10179: Add email configuration settings to installer added

#6 Updated by Bryan Kearney over 7 years ago

  • Bugzilla link changed from 1080617 to 1188346

#7 Updated by Dominic Cleal over 6 years ago

  • Status changed from New to Resolved

In puppet-foreman 4.0.0.

Also available in: Atom PDF