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 1429642

Summary: Remove package profile JSON from production.log
Product: Red Hat Satellite Reporter: Chris Duryee <cduryee>
Component: LoggingAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Renzo Nuccitelli <rnuccite>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.7CC: bkearney, jcallaha, lzap, rnuccite, zhunting
Target Milestone: UnspecifiedKeywords: PrioBumpField
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.0.0.115-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1429670 (view as bug list) Environment:
Last Closed: 2017-05-01 14:00:55 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: 1429670    

Description Chris Duryee 2017-03-06 18:19:58 UTC
Description of problem:

The entire package profile json is logged in production.log. This makes the log extremely painful to read. These lines can be over 110K characters long.

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


How reproducible: every time


Steps to Reproduce:
1. start a satellite and upload a package profile
2. view production.log via 'less'
3.

Actual results: extremely large log message, log takes about 5-10 seconds to page through for each package profile line


Expected results: package profile lines are not logged

Comment 2 Satellite Program 2017-03-06 19:04:15 UTC
Upstream bug assigned to jsherril

Comment 3 Satellite Program 2017-03-06 19:04:17 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15940 has been resolved.

Comment 4 Lukas Zapletal 2017-03-07 08:29:07 UTC
Just for better clarity, I am renaming to prevent confusion. We are removing one element from log that floods it. I also think this consumes a lot of memory because hash structures are large and causes lot of allocations on the Ruby VM stack.

Comment 5 Renzo Nuccitelli 2017-03-23 15:46:57 UTC
No large messages on 6.2.9. Log after uploading a package on production.log:

2017-03-23 11:42:43 40abcce7 [app] [I] Processing by Katello::Api::V2::RepositoriesController#upload_content as HTML
2017-03-23 11:42:43 40abcce7 [app] [I]   Parameters: {"content"=>[#<ActionDispatch::Http::UploadedFile:0x000000090e8f18 @tempfile=#<Tempfile:/tmp/RackMultipart20170323-17654-11tbe62>, @original_filename="PyPAM-0.5.0-12.el6.src.rpm", @content_type="application/x-rpm", @headers="Content-Disposition: form-data; name=\"content[]\"; filename=\"PyPAM-0.5.0-12.el6.src.rpm\"\r\nContent-Type: application/x-rpm\r\n">], "authenticity_token"=>"voDq5tertDzrjK8v9YoHpadOtYVH9ABp4LurGk+suLE=", "api_version"=>"v2", "id"=>"1"}
2017-03-23 11:42:48 40abcce7 [app] [I] Completed 200 OK in 5095ms (Views: 0.7ms | ActiveRecord: 63.7ms)
2017-03-23 11:42:48 40abcce7 [app] [I] Started GET "/katello/api/v2/repositories/1?organization_id=1" for 10.10.120.229 at 2017-03-23 11:42:48 -0400
2017-03-23 11:42:48 40abcce7 [app] [I] Processing by Katello::Api::V2::RepositoriesController#show as JSON
2017-03-23 11:42:48 40abcce7 [app] [I]   Parameters: {"organization_id"=>"1", "api_version"=>"v2", "id"=>"1"}
2017-03-23 11:42:49 40abcce7 [app] [I]   Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.117/app/views/katello/api/v2/repositories/show.json.rabl within katello/api/v2/layouts/resource (215.6ms)
2017-03-23 11:42:49 40abcce7 [app] [I] Completed 200 OK in 233ms (Views: 184.1ms | ActiveRecord: 39.0ms)

Comment 7 errata-xmlrpc 2017-05-01 14:00:55 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-2017:1191