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:
Version-Release number of selected component (if applicable):
[root@localhost ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.3.17-1
subscription management rules: 5.35
subscription-manager: 1.24.4-1.el7
Steps to Reproduce:
1. run subscription-manager-gui
2. open 'System' -> 'Configure Proxy' dialog
3. set a form to use no auth proxy
4. register the system
5. take a look at /etc/rhsm/rhsm.conf
Actual results:
a variable 'proxy_scheme' is empty in a file /etc/rhsm/rhsm.conf
Expected results:
It should be set to 'http' or 'https'.
Additional info:
It is not a big problem from subscription-manager perspective.
But if I run:
[root@localhost ~]# yum install subscription-manager-cockpit --enablerepo='*optional*'
I see a pile of errors due to this empty variable:
Repository 'rhel-7-server-beta-debug-rpms': Error parsing config: Error parsing "proxy = '://auto-services.usersys.redhat.com:3129'": URL must be http, ftp, https, socks4, socks4a, socks5 or socks5h not ""
Repository 'rhel-7-server-openstack-7.0-tools-source-rpms': Error parsing config: Error parsing "proxy = '://auto-services.usersys.redhat.com:3129'": URL must be http, ftp, https, socks4, socks4a, socks5 or socks5h not ""
Repository 'rhel-7-server-optional-beta-rpms': Error parsing config: Error parsing "proxy = '://auto-services.usersys.redhat.com:3129'": URL must be http, ftp, https, socks4, socks4a, socks5 or socks5h not ""
There are no enabled repos.
For all customers using a proxy with the subscription-manager GUI, this will cause their systems to not be able to access content for which they are properly entitled.
As such I believe this should be considered a blocker.
Verification:
I dont observe proxy scheme getting removed from rhsm.conf file after registering system (via GUI) through non-auth proxy, hence marking the bug as verified
[root@kvm-01-guest09 ~]# subscription-manager identity
system identity: 8d18c49f-171b-4fc1-8b29-5362a71e8fe7
name: kvm-01-guest09.lab.eng.brq.redhat.com
org name: Admin Owner
org ID: admin
[root@kvm-01-guest09 ~]# cat /etc/rhsm/rhsm.conf | grep proxy
# an http proxy server to use
proxy_hostname =auto-services.usersys.redhat.com
# The scheme to use for the proxy when updating repo definitions, if needed
proxy_scheme = http
# port for http proxy server
proxy_port =3129
Created attachment 1575225[details]
proxy scheme before registering
[root@kvm-01-guest09 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.7.0-1
subscription management rules: 5.37
subscription-manager: 1.24.8-1.el7
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.
https://access.redhat.com/errata/RHBA-2019:2008