Description of problem:
In firstboot go to Set Up Software Updates. Register to RHN or RHN Satellite and when you hit screen "Review Subscription". Click on "Back" and then "Forward". Your machine is registered two times (and consume two entitlements). IMO on the screen "Review Subscription" you should either disable "back" button. Or provide some warning when user decide to go back and register again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. got through firstboot till "Review Subscription"
2. hit Back
3. hit Forward
and repeat steps 2 and 3 as many times you want
machine is registred multiple time, which user probably do not expect
button back is disable on screen "Review Subscription" or
when user hit this button on this screen some warning pop up
This does not happen if using plain rhn_register. Buttons Back and Forward are managed by firstboot.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
The firstboot (RHN register part thereof) in RHEL 5 has the same problem. Therefore, this is not a regression against RHEL 5 and I propose moving it to RHEL 6.1.
The fix for the bug has two parts:
1. From 'Review Subscription' page, 'Back' button will skip to the 'Set
Up Software Updates' page
2. 'Set Up Software Updates' page will render correctly depending on
whether or not is the system registered.
spacewalk.git master: 9d68037cb12da93a660265e26b4d213d9e307ea2
satellite.git CLIENT-RHEL-6: 53c3cac22acddfb0f33fc505db5884b2e5273808
Verified in rhn-client-tools-1.0.0-48.el6.noarch - works as described in comment 7.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.