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.
Bug 1023320 - [RFE][RHSM-GUI] - Once registered with RHN Classic, the "Register" button of rhsm-gui should be disabled
Summary: [RFE][RHSM-GUI] - Once registered with RHN Classic, the "Register" button of ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.5
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-25 08:04 UTC by Satyabrata Maitra
Modified: 2023-09-14 01:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-25 15:21:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Satyabrata Maitra 2013-10-25 08:04:13 UTC 
Description of problem:
If the system already registered with RHN Classic, and user opening subscription-manager-gui, the "Register" button should be disabled until the system is getting uregistered from RHN Classic.

Version-Release number of selected component (if applicable):
subscription-manager-1.9.9-1.el6
subscription-manager-firstboot-1.9.9-1.el6
subscription-manager-gui-1.9.9-1.el6
subscription-manager-migration-1.9.9-1.el6
subscription-manager-migration-data-2.0.4-1.el6

How reproducible:
Always

Steps to Reproduce:
1. Register rhsm with RHN Classic as :
   In terminal(with superuser) create a file /etc/sysconfig/rhn/systemid
   Append line sudo touch /etc/sysconfig/rhn/systemid into that file. save and 
   quit.
2. Open rhsm gui either from menu or typing subscription-manager-gui in console 
   or run application dialog box.
3. Observe the rhsm-main page appearing the "Register" button enabled.

Actual results:
Although even if user click on "Register" button, it throws some message and restrict user to proceed further, still this restriction can be implemented simply disabling the "Register" button, handling the exception in easier way.

Expected results:
"Register" button should be disable once system is already registered with RHN Classic

Additional info:
Comment 2 Bryan Kearney 2013-10-25 15:21:50 UTC 
There may be valid cases for dual registration. I would prefer to document and warn then to disable.
Comment 3 Satyabrata Maitra 2013-10-28 05:03:28 UTC 
Hi Bryan

Once it is registered with RHN classic does the current system at all allows to register even with other login credential if not the same one, in rhsm gui for dual registration?

Regards
Satya
Comment 4 Red Hat Bugzilla 2023-09-14 01:52:39 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.