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:
During firstboot, if the user registers the system and continues to click the back button, eventually the "Your system was registered for updates during installation" screen will be presented. When next is clicked, the user skips the subscription-manager screens and is taken to the "Create User" screens.

The user can not re-register the system.


Version-Release number of selected component (if applicable):


How reproducible:
Always.

Steps to Reproduce:
1. launch firstboot.
2. On Set up software Updates, click YES, then Forward
3. Select "I'd like to receive updates from RHN..." - then forward.
4. Progress through the registration screens until the system is successfully registered, and you are at the "Create User" screen.
5. Click the back button a few times and you will be shown the "Your system was registered for updates during installation".
  
Actual results:
You are shown the Set Up Software Updates screen with a message of "Your system was registered for updates during installation".

Expected results:
You are shown the set Up Software Updates screen allowing you to choose a server.

This is caused by the rhsm_login screen lazily unregistering you when you try to register again. I've fixed this by simply unregistering any time you return to this screen (after first using it to register).

Fixed in master 4c5cc0858e
and RHEL6.3 b82599710610b9

should be in subscription-manager-0.99.13-1

subscription-manager-firstboot-1.0.0-1.git.11.f42a186.el6.x86_64

This seems to work now in the above version ^^

I've tested this by going through firstboot all the way to the last module/screen and then clicking back to the welcome screen and then going back through again.  It did not say I was already registered at any point.

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.

http://rhn.redhat.com/errata/RHBA-2012-0804.html