Bug 2080324 - Satellite incorrectly reports email test success
Summary: Satellite incorrectly reports email test success
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Email
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact: Shweta Singh
URL:
Whiteboard:
Depends On:
Blocks: 1309740
TreeView+ depends on / blocked
 
Reported: 2022-04-29 13:11 UTC by Radovan Drazny
Modified: 2022-11-16 13:34 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-12404 0 None None None 2022-08-23 15:55:31 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:34:04 UTC

Internal Links: 2109421 2126167

Description Radovan Drazny 2022-04-29 13:11:46 UTC
Description of problem:
The default email method configured for a Satellite server is "sendmail". This relies on a sendmail binary being present on the system. For RHEL 7 this is true - the postfix package (providing /usr/sbin/sendmail binary) is installed as a part of base RHEL install.

For RHEL 8, this no longer holds true - there is no sendmail by default. We probably don't want to install postfix as a part of the Satellite install. The issue is, when email is configured for a user, and a test email is sent, Satellite reports "Email was sent successfully", which is not true. There is the following message in /var/log/messages:

  foreman[948]: sh: /usr/sbin/sendmail: No such file or directory

No email is delivered of course. 

Version-Release number of selected component (if applicable):
Sat 6.11 Snap 18 running on RHEL 8

How reproducible:
Always

Steps to Reproduce:
1. Make sure the current user has a valid email address configured (root.fqdn is enough)
2. Go to Administer -> Settings -> Email
3. Push the Test Email button. 

Actual results:
There is a notification popup saying "Email was sent successfully".
An error message appears in /var/log/messages. 
No mail is delivered.

Expected results:
An error is reported (as long as there is no sendmail binary, or no valid email delivery configuration)

Additional info:
Installing and starting the postfix daemon fixes things - the test mail is delivered, and the popup about successful send is correct.

Comment 2 Adam Ruzicka 2022-08-23 15:50:27 UTC
This should be fixed by mikel/mail-2.8.0, if it is ever released. There is 2.8.0rc1, but I don't feel comfortable shipping a release candidate version. We can either wait for a proper 2.8.0 release or backport the patch[1] ourselves and carry it in our packaging.

See issues[2] and [3] for reference.

[1] - https://github.com/mikel/mail/pull/1149
[2] - https://github.com/rails/rails/issues/35330
[3] - https://github.com/mikel/mail/issues/1321

Comment 3 Evgeni Golov 2022-08-24 09:37:59 UTC
IMHO, we can fix the root cause (sendmail not being present) via https://bugzilla.redhat.com/show_bug.cgi?id=2109421 and defer fixing mike/mail until there is a release.

Comment 4 Adam Ruzicka 2022-10-03 09:09:49 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=2109421 was moved to ON_QA, moving this one as well.

Comment 5 Shweta Singh 2022-10-03 12:03:24 UTC
Verified on Satellite 6.12 Snap 13
Moving to verified with verification steps given in https://bugzilla.redhat.com/show_bug.cgi?id=2109421#c12 as it is a clone of that BZ.

Comment 9 errata-xmlrpc 2022-11-16 13:33:46 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 (Important: Satellite 6.12 Release), 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/RHSA-2022:8506


Note You need to log in before you can comment on or make changes to this bug.