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 1865943 - dynflow-sidekiq results in messages logs getting filled up more frequently
Summary: dynflow-sidekiq results in messages logs getting filled up more frequently
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dynflow
Version: 6.8.0
Hardware: All
OS: All
medium
medium
Target Milestone: 6.8.0
Assignee: Adam Ruzicka
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-04 15:12 UTC by anerurka
Modified: 2020-10-27 13:06 UTC (History)
4 users (show)

Fixed In Version: foreman-2.1.2.1-1,foreman-2.1.2.14-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:05:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
mesage logs captured at the time of execution (10.66 KB, text/plain)
2020-08-04 15:12 UTC, anerurka 		no flags Details
var-log-messages.log (19.88 KB, text/plain)
2020-09-25 15:02 UTC, Lukáš Hellebrandt 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30667 0 Normal Closed dynflow-sidekiq results in messages logs getting filled up more frequently 2021-01-05 14:53:36 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:06:12 UTC

Description anerurka 2020-08-04 15:12:04 UTC 
Created attachment 1710348 [details]
mesage logs captured at the time of execution

Description of problem:

dynflow-sidekiq results in messages logs getting filled up more frequently 

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

Red Hat Satellite 6.8 [snap 09]
tfm-rubygem-smart_proxy_dynflow-0.2.4-5.el7sat.noarch
tfm-rubygem-smart_proxy_dynflow_core-0.2.6-1.fm2_1.el7sat.noarch
tfm-rubygem-dynflow-1.4.6-1.el7sat.noarch
foreman-dynflow-sidekiq-2.1.0-1.el7sat.noarch


Dynflow sidekiq, logs inside /var/log/messages, and it is observed that for a single rex execution, there is additional logging compared to  Red Hat Satellite v6.7

1. Assign few Ansible roles to the host
- RedHatInsights.insights-client	
- theforeman.foreman_scap_client

2. Run Ansible Roles.	

Actual Result 

- For a host registered to Sat v.6.7, "/var/log/messages" was filled up with 4KB
 
- However for Sat v.6.8 "/var/log/messages" was filled up with 12kb.  

This could impact users in a large environment where messages logs being frequently getting full.
Comment 1 Adam Ruzicka 2020-08-19 13:41:08 UTC 
Created redmine issue http://projects.theforeman.org/issues/30667 from this bug
Comment 2 Bryan Kearney 2020-08-20 12:01:15 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30667 has been resolved.
Comment 4 Lukáš Hellebrandt 2020-09-16 13:31:57 UTC 
FailedQA with Sat 6.8 snap 14.

The sidekiq logs are still present with default settings. Using reproducer from OP, I got a ~40 KB increase in /var/log/messages file size.
Comment 6 Lukáš Hellebrandt 2020-09-25 15:01:03 UTC 
FailedQA with Sat 6.8 snap 17.

While it's better than in comment 4, we still have the original size this BZ has been reported for: 12 KB. Attaching /var/log/messages.
Comment 7 Lukáš Hellebrandt 2020-09-25 15:02:28 UTC 
Created attachment 1716635 [details]
var-log-messages.log
Comment 8 Adam Ruzicka 2020-09-25 17:28:03 UTC 
You cannot really compare absolute sizes of a system-wide log file if you do different things on the system (attachment from #7 shows bunch of puppet and pulp stuff going on while attachment from #0 had none of that).

The original description said "dynflow-sidekiq results in messages logs getting filled up more frequently", which is now fixed. None of the log messages in #7 comes from dynflow-sidekiq.
Comment 9 Mike McCune 2020-09-26 15:09:35 UTC 
The only thing this BZ should be testing is the *count* of log messages from the dynflow services, not absolute file size of /var/log/messages as that is entirely dependent on the entire sum of services on the Satellite which is unpredictable.

Test the message line count from dynflow, not file size of all messages.
Comment 10 Lukáš Hellebrandt 2020-09-29 09:45:12 UTC 
After stripping the log off of pulp activity, I still see more messages both as in count and in size. They are, however, of the same type as the messages provided in original log for 6.7. Excess messages from original log for 6.8 are gone => verified with Sat 6.8 snap 17 using reproducer from OP and based on devs' comment 8 and comment 9.
Comment 13 errata-xmlrpc 2020-10-27 13:05:07 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.8 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.