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.
Descriptionsthirugn@redhat.com
2015-04-27 20:23:35 UTC
Created attachment 1019429[details]
foreman debug
Description of problem:
Email notifications failed
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150424.0
How reproducible:
Always
Steps to Reproduce:
1. Trigger an email by some means. I did the following:
- Enable email notifications is My Account
- Create a product and a repo
- Sync the repo
Actual results:
Email is not sent. I noticed the following error.
/var/log/foreman/production.log
2015-04-27 16:18:03 [I]
Sent mail to *****@******.com (799ms)
2015-04-27 16:18:03 [W] Failed to send email notification satellite_sync_errata: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
Expected results:
Email sent successfully
Additional info:
Thanks for the info -
You need to trust the internal Red Hat CA on the server:
> [root@cloud-qe-17 ~]# cp newca.crt /etc/pki/ca-trust/source/anchors/
> [root@cloud-qe-17 ~]# update-ca-trust enable
> [root@cloud-qe-17 ~]# update-ca-trust
and then mail works.
Alternatively, you need to enable this setting in email.yaml:
> :enable_starttls_auto: :false
I added this info to BZ1188320.
Comment 5sthirugn@redhat.com
2015-05-13 20:00:12 UTC
Created attachment 1019429 [details] foreman debug Description of problem: Email notifications failed Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150424.0 How reproducible: Always Steps to Reproduce: 1. Trigger an email by some means. I did the following: - Enable email notifications is My Account - Create a product and a repo - Sync the repo Actual results: Email is not sent. I noticed the following error. /var/log/foreman/production.log 2015-04-27 16:18:03 [I] Sent mail to *****@******.com (799ms) 2015-04-27 16:18:03 [W] Failed to send email notification satellite_sync_errata: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed Expected results: Email sent successfully Additional info: