Red Hat Bugzilla – Bug 811337
Firstboot: Already registered screen is presented after registering and clicking back
Last modified: 2013-01-10 06:00:50 EST
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):
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".
You are shown the Set Up Software Updates screen with a message of "Your system was registered for updates during installation".
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
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.
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.