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 1676891 - RFE to allow for better stats gathering
Summary: RFE to allow for better stats gathering
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Michal Domonkos
QA Contact: Luca Berton
Katerina Nemcova
Depends On: 1647454 1681084
Blocks: 1755139
TreeView+ depends on / blocked
Reported: 2019-02-13 14:13 UTC by Daniel Mach
Modified: 2024-03-25 15:13 UTC (History)
16 users (show)

Fixed In Version: libdnf-0.38.1-1.el8
Doc Type: Enhancement
Doc Text:
.`User-Agent` header string now includes information read from the `/etc/os-release` file With this enhancement, the `User-Agent` header string, which is normally included with the HTTP requests made by DNF, has been extended with information read from the `/etc/os-release` file. To obtain more information, see `user_agent` in the `dnf.conf(5)` man page.
Clone Of: 1647454
Last Closed: 2020-04-28 16:47:38 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1823 0 None None None 2020-04-28 16:48:01 UTC

Description Daniel Mach 2019-02-13 14:13:47 UTC
This requirement comes from Fedora to enable better stats gathering on metalink servers and mirrors.

Fedora Change: https://fedoraproject.org/wiki/Changes/DNF_Better_Counting

The change consists of 2 parts:
- User-Agent change
- countme feature


libdnf/$libdnf_version ($NAME $VERSION_ID; Linux.$basearch)
libdnf/$libdnf_version ($NAME $VERSION_ID; $VARIANT_ID; Linux.$basearch)

libdnf/0.26.0 (Fedora 29; Linux.x86_64)
libdnf/0.26.0 (Fedora 29; server; Linux.x86_64)
libdnf/0.26.0 (Red Hat Enterprise Linux 7.6; workstation; Linux.x86_64)

Add a new 'countme' option to repo configs, for example:
countme = 1

Create a new dnf sub-command to trigger the countme feature:
$ dnf countme
Iterate through all repos:
if countme == 1:
   where $url is first available from [metalink, mirrorlist, baseurl]
   # consider using HEAD instead of GET

Create a systemd timer triggering the `dnf countme` command periodically

Comment 23 Terry Bowling 2019-12-06 13:36:10 UTC
After further discussion, it was decided that this should be included in the release notes to ensure full disclosure and trust from users. It should be noted that great care was taken to ensure that this is not user identifiable information and is less detailed than common Web Browser user agent reporting, as well as less detail than other popular linux distributions collect from update repositories.

Additionally documentation should included instructions on how this can be disabled in the yum configuration.

Comment 33 errata-xmlrpc 2020-04-28 16:47:38 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.


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