Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1376134 - [RFE] Pulp should log content unit downloads at a level other than DEBUG
[RFE] Pulp should log content unit downloads at a level other than DEBUG
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Pulp (Show other bugs)
6.2.0
Unspecified Unspecified
medium Severity medium (vote)
: GA
: Unused
Assigned To: satellite6-bugs
Perry Gagne
: FutureFeature, Triaged
: 1400747 (view as bug list)
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-09-14 14:54 EDT by Rich Jerrido
Modified: 2018-09-19 11:12 EDT (History)
11 users (show)

See Also:
Fixed In Version: pulp-2.13.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-21 07:35:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Pulp Redmine 2315 Normal CLOSED - CURRENTRELEASE Better logging at INFO level 2017-05-24 14:36 EDT
Red Hat Product Errata RHSA-2018:0336 normal SHIPPED_LIVE Important: Satellite 6.3 security, bug fix, and enhancement update 2018-02-21 17:43:42 EST

  None (edit)
Description Rich Jerrido 2016-09-14 14:54:43 EDT 
Description of problem:
As a user of Satellite 6, I would like to have Pulp should log content unit downloads at a level other than DEBUG. 

Unit downloads are useful information that I would like to see logged at the INFO level, as it allows me to very easily determine when I have issues with content sync (and where my content is coming from if using an alternate content source).

Enabling debug logging for pulp does in fact work, but I got a LOT of other DEBUG logging (QPID debug logging for example), which is very very verbose.
Comment 2 pulp-infra@redhat.com 2016-11-21 13:51:26 EST 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2016-11-21 13:51:29 EST 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 4 Michael Hrivnak 2016-12-12 14:39:22 EST 
*** Bug 1400747 has been marked as a duplicate of this bug. ***
Comment 5 pulp-infra@redhat.com 2016-12-19 12:31:31 EST 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 6 pulp-infra@redhat.com 2016-12-22 12:31:31 EST 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2017-01-13 09:02:01 EST 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2017-01-13 09:32:05 EST 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 9 pulp-infra@redhat.com 2017-05-17 09:35:55 EDT 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2017-05-24 14:36:06 EDT 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 15 errata-xmlrpc 2018-02-21 07:35:52 EST 
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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.