Hide Forgot
Created attachment 1231985 [details] the rhsm.log Description of problem: Failed to launch subscription-manager gui when configure invalid proxy in proxy url,and was reminded "Proxy connection failed,please check your settings." Version-Release number of selected component (if applicable): RHEL-6.9-20161201.0: subscription-manager-firstboot-1.18.5-1.el6.x86_64 subscription-manager-1.18.5-1.el6.x86_64 python-rhsm-certificates-1.18.5-1.el6.x86_64 subscription-manager-gui-1.18.5-1.el6.x86_64 python-rhsm-1.18.5-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1.Install build RHEL-6.9-20161201.0 2.Open subscription-manager gui and configure the proxy with invalid one (error.test.com:123),then lick the "save" button 3.click X button to close subscription-manager gui and try to reopen again #subscription-manager-gui Actual results: subscription-manager gui not open and a reminder "Proxy connection failed,please check your settings" display on console Expected results: subscription-manager gui should open and no error should display on console. Additional info:
This behavior was first introduced in bug 1327179. The attached PR modifies that behavior to support a GUI-only flow (including a way to edit the network settings).
Verifying version: [root@dhcp-128-193 ~]# subscription-manager version subscription management server: 0.9.51.20-1 subscription management rules: 5.15.1 subscription-manager: 1.18.7-1.el6 python-rhsm: 1.18.6-1.el6 Verification: 1.Install build RHEL-6.9-20170111.0 2.Open subscription-manager gui and configure the proxy with invalid one (error.test.com:123),then lick the "save" button 3.click X button to close subscription-manager gui 4.try to reopen again #subscription-manager-gui then a warning dialog pops up to remind proxy connection failed 5.then click ok to check seetings So this issue is verified and move the status to "verified".
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://rhn.redhat.com/errata/RHSA-2017-0698.html