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.

Bug 1188346

Summary: [RFE] Add email configuration settings to katello-installer
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: InstallationAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: sthirugn <sthirugn>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: bbuckingham, bkearney, jhutar
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/5824
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 08:47:32 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:
Bug Depends On:    
Bug Blocks: 1130651, 1188301    

Description sthirugn@redhat.com 2015-02-02 16:30:50 UTC 
Description of problem:
Satellite 6.1 is introducing email notifications.  Basic email configuration settings should be configurable in the katello-installer - Ref: http://www.theforeman.org/manuals/1.7/index.html

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

How reproducible:
N/A

Steps to Reproduce:
N/A

Actual results:
N/A

Expected results:
N/A

Additional info:
Comment 2 Bryan Kearney 2015-04-17 18:13:26 UTC 
Created redmine issue http://projects.theforeman.org/issues/10179 from this bug
Comment 3 Bryan Kearney 2015-04-20 11:57:59 UTC 
*** Bug 1080617 has been marked as a duplicate of this bug. ***
Comment 4 Bryan Kearney 2015-04-20 11:58:08 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/5824 from this bug
Comment 5 Bryan Kearney 2015-08-25 18:33:16 UTC 
Upstream bug component is Installer
Comment 6 Bryan Kearney 2015-12-01 15:05:45 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/5824 has been closed
-------------
Stephen Benjamin
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?
Comment 11 sthirugn@redhat.com 2016-04-07 15:30:54 UTC 
Verified in satellite-6.2.0-6.2.beta.el7sat.noarch.  I passed in the following parameters and they are set properly in satellite.

foreman-installer --scenario katello --foreman-admin-email='***' \
 --foreman-email-delivery-method='smtp' \
 --foreman-email-smtp-address='smtp.*****' \
 --foreman-email-smtp-authentication='none' \
 --foreman-email-smtp-domain=*** \
 --foreman-email-smtp-port=25 \
Comment 13 errata-xmlrpc 2016-07-27 08:47:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500