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:
1) Running smart-proxy-openscap-send generates below logs:
~~~
Your Gemfile lists the gem rsec (< 1) more than once.
You should probably keep only one of them.
Remove any duplicate entries and specify the gem only once.
While it's not a problem now, it could cause errors if you change the version of one of them later.
~~~
and when configured email notifications, same are flooded with email every 30 minutes.
2) Cronjob trigerring this :
# cat /etc/cron.d/tfm-rubygem-smart_proxy_openscap
*/30 * * * * foreman-proxy smart-proxy-openscap-send >> /var/log/foreman-proxy/cron.log
3) The logfile /var/log/foreman-proxy/cron.log is empty
This doesn't seems to be error but causing unnecessary email notifications every 30 minutes.
Version-Release number of selected component (if applicable):
- tfm-rubygem-smart_proxy_openscap-0.9.1-1.el7sat.noarch
How reproducible:
- Easily
Steps to Reproduce:
1. Execute smart-proxy-openscap-send on Satellite 6.10
2. Or configure mail notifications for openscap and check the emails.
Actual results:
~~~
Your Gemfile lists the gem rsec (< 1) more than once.
You should probably keep only one of them.
Remove any duplicate entries and specify the gem only once.
While it's not a problem now, it could cause errors if you change the version of one of them later.
~~~
Expected results:
- Should not show logs while executing this command which will stop it getting on email notifications.
- Logs should get captured in /var/log/foreman-proxy/cron.log file.
Verified:
Verified with:
- Satellite 6.11.1 snap 2
Test steps:
- Run smart-proxy-openscap-send on Satellite 6.11.1 snap 2
Observations:
- No logs were shown while executing smart-proxy-openscap-send
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 (Satellite 6.11.1 Async Bug Fix Update), 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-2022:5742