Description of problem:
If you go through firstboot while already registered to RHN classic, the entire "Set Up Software Updates" module is skipped and it goes to a screen explaining 'Your system was registered for updates during installation'.

Being registered with subscription manager gives you similar registration detection (skipping the register screen), but happens much later in the process which presents several problems.


Version-Release number of selected component (if applicable):
subscription-manager-firstboot-0.96.11-1.git.7.15fc9d2.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1.  register subscription manager
2.  run firstboot
  
Actual results:
* You get to the screen asking if you'd like to set up software updates.
  - If you choose 'No, I prefer to register at a later time', you are presented with a warning saying you won't receive software updates, and that you wont be in compliance.

  - Is this screen relevant if you're already registered?

* If you choose to register, you are asked to choose a server to register to.
  - The default is still RHN classic even though you've must have chosen subscription-manager at some earlier point by the fact you've already registered to it.

  - If you end up choosing classic you do not get the "you are already registered with subscription manager, do you want to continue?" warning that you would get if you used the rhn_register gui normally.

Expected results:
You would never get to the screen where you would be asked if you want to set up software updates.  Instead you would be taken directly to the subscription-manager gui screen so you could subscribe to entitlements.

If you hit back on this screen, you would be sent to the previous firstboot module: License Information.

Additional info:
This may be an issue for the maintainers of both subscription-manager-firstboot and rhn-setup-gnome/rhn-client-tools.