RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1577369 - DEBUG-level logging does not log request POST body
Summary: DEBUG-level logging does not log request POST body
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-11 19:49 UTC by Chris Duryee
Modified: 2021-02-08 15:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-08 15:31:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris Duryee 2018-05-11 19:49:08 UTC 
Description of problem:

It is sometimes useful to see what data sub-man is POSTing up to candlepin. However, if you enable debug-level logging in /etc/rhsm/rhsm.conf, you'll just see two lines related to the POST. For example:

2018-05-11 19:30:08,303 [DEBUG] subscription-manager:16862:MainThread @connection.py:543 - Making request: POST /subscription/consumers?owner=5894300                                                                                                                                    
2018-05-11 19:30:10,515 [INFO] subscription-manager:16862:MainThread @connection.py:586 - Response: status=200, requestUuid=d79b1f15-c84a-4d19-b58c-16b79137f268, request="POST /subscription/consumers?owner=5894300"      

It would be more useful if the request body was logged as well. This makes it easier to replicate the call when working on issues.

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


How reproducible: every time


Steps to Reproduce:
1. set the following in rhsm.conf:
[logging]
default_log_level = DEBUG
rhsm.connection = DEBUG

2. do a register
3. view rhsm.log

Actual results: you'll see the URLs called, but POSTs do not show the request body.


Expected results: the request body should be logged at debug level
Comment 3 Rehana 2021-02-08 15:31:24 UTC 
thanks for opening the bug , we have improved the debugging experience over the last couple of years . can be find here https://www.candlepinproject.org/docs/subscription-manager/debug_http_traffic.html . 

Thanks,
Rehana
Note You need to log in before you can comment on or make changes to this bug.