Created attachment 1479817 [details] production logs Description of problem: We are observing extra logging in the production logs which is crowding the production logs even when no debug logging is enabled Version-Release number of selected component (if applicable): 6.4 HTB How reproducible: Always. Steps to Reproduce: 1. Sync a Repo on the satellite and wait until it completes. 2. Simultaneously check the production logs and you will see something as below: ---snip ----- 2018-08-30T09:13:30 [I|kat|] GET: https://satellite.example.com/pulp/api/v2/repositories/5fad9c2f-2e8b-48d1-981a-ddc6ff8e649a/?details=true: {"content_type"=>"application/json", "accept"=>"application/json"} ---snip ------ Actual results: Extra logging is observed Expected results: Logging should be minimal if logging level is info Additional info: Attaching relevant part of the production logs on the bz
I was able to reproduce the log on a 6.4 install when syncing a repo that needed to download more packages. If the sync resulted in no packages, the additional log was not there. I also confirmed that I did not see the same on a 6.2 instance. In the scenario where it was observed, the log was generated 4 times syncing a RHEL 7Server repo that needed to pull down 204 new packages. (Note: there is likely no correlation between the packages and logs.)
*** Bug 1626540 has been marked as a duplicate of this bug. ***
Created redmine issue https://projects.theforeman.org/issues/26018 from this bug
This bug was cloned and is still going to be included in the 6.4.3 release. It no longer has the sat-6.4.z+ flag and 6.4.3 Target Milestone Set which are now on the 6.4.z cloned bug. Please see the Clones field to track the progress of this bug in the 6.4.3 release.
The upstream issue is still in a NEW state with no fix attached.
Eric, I closed the issue and associated the Runcible PR. Should be good to go
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26018 has been resolved.
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/RHSA-2019:1222