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:
Hosts in IPv6-only networks cannot subscribe to RHSM using an IPv6 proxy address. The dual-stack proxy is necessary as RHSM currently still don't support IPv6.
Version-Release number of selected component (if applicable):
subscription-manager 1.29.33.1-1.el9_2
How reproducible:
100%
Steps to Reproduce:
1. Provision host with IPv6 connectivity
2. Run `subscription-manager version --proxy="http://[<IPv6-of-your-proxy>]:3128
Actual results:
The following blocks show you some examples of the the commands I tried. IP addresses were replaced with RFC 3849 prefix.
~~~
# subscription-manager version --proxy="http://[2001:DB8::DEAD:BEEF:2]:3128"
Traceback (most recent call last):
File "/usr/sbin/subscription-manager", line 33, in <module>
sys.exit(load_entry_point('subscription-manager==1.29.33.1', 'console_scripts', 'subscription-manager')())
File "/usr/lib64/python3.9/site-packages/subscription_manager/scripts/subscription_manager.py", line 73, in main
return managercli.ManagerCLI().main()
File "/usr/lib64/python3.9/site-packages/subscription_manager/managercli.py", line 87, in main
ret = CLI.main(self)
File "/usr/lib64/python3.9/site-packages/subscription_manager/cli.py", line 190, in main
return cmd.main()
File "/usr/lib64/python3.9/site-packages/subscription_manager/cli_command/cli.py", line 331, in main
self.proxy_port = int(parts[1])
ValueError: invalid literal for int() with base 10: 'DB8'
~~~
The same 'ValueError' occurs when specifying the IPv6 address without the brackets '[]'. Using proxy FQDN leads to the same exception followed by another one:
~~~
# subscription-manager version --proxy="http://proxy.example.com"
Traceback (most recent call last):
File "/usr/lib64/python3.9/site-packages/rhsm/utils.py", line 207, in parse_url
int(port)
ValueError: invalid literal for int() with base 10: 'DB8'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/sbin/subscription-manager", line 33, in <module>
sys.exit(load_entry_point('subscription-manager==1.29.33.1', 'console_scripts', 'subscription-manager')())
File "/usr/lib64/python3.9/site-packages/subscription_manager/scripts/subscription_manager.py", line 73, in main
return managercli.ManagerCLI().main()
File "/usr/lib64/python3.9/site-packages/subscription_manager/managercli.py", line 87, in main
ret = CLI.main(self)
File "/usr/lib64/python3.9/site-packages/subscription_manager/cli.py", line 190, in main
return cmd.main()
File "/usr/lib64/python3.9/site-packages/subscription_manager/cli_command/cli.py", line 376, in main
self.cp = self.cp_provider.get_consumer_auth_cp()
File "/usr/lib64/python3.9/site-packages/subscription_manager/cp_provider.py", line 184, in get_consumer_auth_cp
self.consumer_auth_cp = connection.UEPConnection(
File "/usr/lib64/python3.9/site-packages/rhsm/connection.py", line 1367, in __init__
super(UEPConnection, self).__init__(user_agent=user_agent, **kwargs)
File "/usr/lib64/python3.9/site-packages/rhsm/connection.py", line 248, in __init__
info = utils.get_env_proxy_info()
File "/usr/lib64/python3.9/site-packages/rhsm/utils.py", line 237, in get_env_proxy_info
info = parse_url(proxy_info, default_port=DEFAULT_PROXY_PORT)
File "/usr/lib64/python3.9/site-packages/rhsm/utils.py", line 211, in parse_url
raise ServerUrlParseErrorPort(local_server_entry)
rhsm.utils.ServerUrlParseErrorPort: http://[2001:DB8::DEAD:BEEF:2]:3128/
~~~
Expected results:
Command should succeed.
This is the RHEL 9 version of bug 1878182; known issue, unfortunately.
OTOH, subscription-manager does actually support IPv6: at least TTBOMK, the problem is only in the parsing of URL strings.
Comment 2RHEL Program Management
2023-09-22 14:18:58 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3RHEL Program Management
2023-09-22 14:19:43 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.