Red Hat Bugzilla – Bug 642660
Firstboot - inconsistent state when going "back" after registering
Last modified: 2014-11-09 17:51:03 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start firstboot
2. Register with candlepin
3. Now click Back
You're back on the registration form even though you are already registered. The user can enter a new user/pw here and try to register again, which appears to succeed but is actually in a failed state.
We may want to consider unregistering the user when he clicks "Back" (perhaps with a "Are you sure you want to unregister?"). Because it's possible to register with candlepin, and use the back button to select RHN, and then proceed with RHN, and be registered with both RHN *and* Candlepin.
Alternatively, we could have Back still show the register panel, but if you change user/pw it registers with --force (with a prompt, of course - should never use --force by default). But then we'd need some way of preventing double registration with candlepin/RHN.
My personal preference is option #1 above - make it impossible to register with both rhn and candlepin.
This was not fixed exactly as mentioned above. After some discussion, the decision was made to bypass the registration screen if the system was already registered, and to disable the back button once the user reaches the subscription manager screen.
Fixed in branches:
RHEL6.2 - 75a65f92580e74f26488d1bba5580550679f719a
master - e57d43303f5ca506c7b5df69a95ca471beb6fdde
This fix does not apply to RHEL5 since there did not seem to be a way to access the back button in order to disable with the older version of firstboot.
739551 was created to keep track of this issue with 5.8.
Created attachment 524924 [details]
no back button
VERIFIED against the above version.
Screen shot shows that the back button is disabled once registered. It also will skip the registration screen entirely if you are already registered when starting firstboot.
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.