Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2213899

Summary: [RFE] Set custom User Agent for Pulpcore
Product: Red Hat Satellite Reporter: Sam Lindberg <slindber>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.13.1CC: dalley, dsinglet, rlavi
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-31 13:28:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sam Lindberg 2023-06-09 19:39:25 UTC
Description of problem:
Connections from Pulpcore have a user agent header in their requests created from the Pulp version, the Python version, and aiohttp version. Certain network components have the ability to restrict requests by user agent fields. This request is to allow a user to set a custom user agent header value for Pulpcore to use.

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

python39-pulpcore-3.21.6-1.el8pc.noarch

satellite-6.13.1-1.el8sat.noarch

How reproducible:
N/A

Steps to Reproduce:
N/A

Actual results:
User agent field is defined in this file 
/usr/lib/python3.6/site-packages/pulpcore/download/factory.py, By the following function:

def user_agent():
        """
        Produce a User-Agent string to identify Pulp and relevant system info.
        """
        pulp_version = get_distribution("pulpcore").version
        python = "{} {}.{}.{}-{}{}".format(sys.implementation.name, *sys.version_info)
        uname = platform.uname()
        system = f"{uname.system} {uname.machine}"
        return f"pulpcore/{pulp_version} ({python}, {system}) (aiohttp {aiohttp_version})"

Expected results:
A settings value on Satellite to allow user to input a custom user agent string.

Additional info:
As a workaround to allow this to work replace the following line:
        return f"pulpcore/{pulp_version} ({python}, {system}) (aiohttp {aiohttp_version})"
with:
        return f"curl/7.61.1"

Comment 1 Daniel Alley 2023-07-17 16:59:28 UTC
What about disabling the UserAgent entirely, rather than using a false one?  Do those "network components" permit requests which lack UserAgent?

Comment 3 Daniel Alley 2023-08-28 02:37:53 UTC
Ultimately this is a failure of the firewall - it may be challenging to configure, but I feel like having the software lie about the UserAgent is not the appropriate solution here.

Barring any further information about this issue re: my previous queries, I'm going to mark this "Closed - insufficent data" in a week or two. Please let me know if there's some context that makes this genuinely the best solution in some cases.  And if so, whether my previous suggestion would work.

Comment 4 Red Hat Bugzilla 2023-12-30 04:25:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days