Hide Forgot
Description of problem: Try to register via GUI:system->register,the system->register button is still enabled after register Version-Release number of selected component (if applicable): python-rhsm-1.17.9-1.el7.x86_64 python-rhsm-certificates-1.17.9-1.el7.x86_64 subscription-manager-1.17.15-1.el7.x86_64 subscription-manager-gui-1.17.15-1.el7.x86_64 subscription-manager-initial-setup-addon-1.17.15-1.el7.x86_64 How reproducible: always Steps to Reproduce: 1.Install RHEL-7.3-20161005.0 2.Launch subscription-manager-gui,click system->register button,input valid url address in the blank(subscription.rhsm.stage.redhat.com:443/subscription),then click Next 3.Input account and password (new_test:redhat),then click Register button and Attach subscription 4.After register successfully,go back GUI to check system->register button,is still enabled 5.close the GUI window and launch subscription-manager-gui again.The system->register button become disabled. Actual results: The Register button is still enabled after register Expected results: The Register button should be disabled after register Additional info:
Created attachment 1208292 [details] The screenshot of the Register button after register
Created attachment 1208293 [details] The rhsm.log
verify this issue when the RHEL7.4 composes start rolling out
Verifying version: [root@dhcp-128-6 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.9.51.21-1 subscription management rules: 5.15.1 subscription-manager: 1.19.4-1.el7 python-rhsm: 1.19.2-1.el7 Verification: 1.Install build RHEL-7.4-20170330.1,and open Subscription Manager GUI. 2.Register the system by clicking system->register button,then input valid account and password to register 3.After register successfully,go back GUI to check system->register button the system-> register button become disabled. 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://access.redhat.com/errata/RHBA-2017:2083