Red Hat Bugzilla – Bug 829466
Cannot register in subscription-manager-gui using on-site Subscription Service
Last modified: 2013-01-07 22:54:12 EST
Description of problem:
When using subscription-manager-gui, you cannot register to an on-site Subscription Service. This blocks all gui testing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install a rhel 5.9 system with the above sub-man-gui
2. Fire up the gui
3. Go to System > Register
4. Select "I have access to an on-site Subscription Service..."
5. In the subscription service box, enter in your standalone candlepin
5a. I entered in "mgmt5.rhq.lab.eng.bos.redhat.com:8443/candlepin"
6. Click Next
Traceback (most recent call last):
File "/usr/share/rhsm/subscription_manager/gui/registergui.py", line 191, in on_register_button_clicked
File "/usr/share/rhsm/subscription_manager/gui/registergui.py", line 203, in register
File "/usr/share/rhsm/subscription_manager/gui/registergui.py", line 334, in _server_selected
(hostname, port, prefix) = parse_server_info(local_server)
File "/usr/share/rhsm/subscription_manager/utils.py", line 74, in parse_server_info
File "/usr/share/rhsm/subscription_manager/utils.py", line 180, in parse_url
if result.port is not None:
AttributeError: 'tuple' object has no attribute 'port'
It allows me to to to the next screen so I can enter in my username and password
This makes automation sad :(
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
UI redesign seems to have cleared up the problem.
New stuff works, tested as of: subscription-manager-gui-1.0.13-1.git.14.28f8917.el5
New positive and negative tests have been incorporated into the automation for this.
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.