Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When some application uses RHSM D-Bus API, then rhsm.service sends information about dbus_sender in HTTP header User-Agent in related REST API calls. This functionality is available only on RHEL9. This functionality was introduce in this PR: https://github.com/candlepin/subscription-manager/pull/2329
Intention of this card is to backport this functionality to 1.28 branch (RHEL8).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
No way to determine the client tool used for registering the system
Expected results:
Should be able to view which tooling was used for registering to Red Hat fulfilling the requirement from https://issues.redhat.com/browse/RHIN-829
Additional info:
Version of SUBMAN for final verification:
[root@kvm-02-guest15 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 4.2.15-1
subscription management rules: 5.43
subscription-manager: 1.28.37-1.el8
updating rhsm.service
[root@kvm-02-guest15 ~]# tail -2 /usr/lib/systemd/system/rhsm.service
Environment=SUBMAN_DEBUG_PRINT_REQUEST=1
Environment=SUBMAN_DEBUG_PRINT_REQUEST_HEADER=1
reloading systemd daemon:
[root@kvm-02-guest15 ~]# systemctl daemon-reload
Registering through cockpit
After registering through cockpit, the log contained:
Making insecure request: subscription.rhsm.stage.redhat.com:443 POST /subscription/consumers?owner=16767941 {'Content-type': 'application/json', 'Accept': 'application/json', 'x-subscription-manager-version': '1.28.37-1.el8', 'X-Correlation-ID': '430c431e21de43cbac648ebf4da8b3ca', 'Authorization': 'Basic enBldHJhY2VrOlBldHJhY2Vr', 'Accept-Language': 'en-us', 'User-Agent': 'RHSM/1.0 (cmd=rhsm-service) subscription-manager/1.28.37-1.el8'}
^^ Final verification PASSED
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 (subscription-manager bug fix and enhancement update), 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-2023:7092