Description of problem: Migration from RHN_classic to RHSM completes the auto-subscribing process and then asks you to choose a service-level Version-Release number of selected component (if applicable): RPM used: [root@dhcp201-196 ~]# rpm -qa | grep subscription-manager subscription-manager-gui-1.0.4-1.git.1.b28337e.el5 subscription-manager-migration-data-1.11.1.1-1.git.2.c7fbafe.el5 subscription-manager-migration-1.0.4-1.git.1.b28337e.el5 subscription-manager-1.0.4-1.git.1.b28337e.el5 subscription-manager-firstboot-1.0.4-1.git.1.b28337e.el5 How reproducible: Steps to Reproduce: [root@dhcp201-196 ~]# rhn-migrate-classic-to-rhsm RHN Username: qa Password: Retrieving existing RHN Classic subscription information ... +----------------------------------+ System is currently subscribed to: +----------------------------------+ rhel-x86_64-server-5 List of channels for which certs are being copied rhel-x86_64-server-5 Product certificates copied successfully to /etc/pki/product Preparing to unregister system from RHN classic ... System successfully unregistered from RHN Classic. Attempting to register system to Certificate-based RHN ... The system has been registered with id: 0208590b-59f3-4715-8644-fbafc9d3b81a System 'dhcp201-196.englab.pnq.redhat.com' successfully registered to Certificate-based RHN. Attempting to auto-subscribe to appropriate subscriptions ... Installed Product Current Status: Product Name: Awesome OS for S390 Bits Status: Not Subscribed Product Name: Stackable with Awesome OS for x86_64 Bits Status: Not Subscribed Please visit https://access.redhat.com/management/consumers/0208590b-59f3-4715-8644-fbafc9d3b81a to view the details, and to make changes if necessary. Please select a service level agreement for this system. 1. SELF-SUPPORT 2. Standard 3. STANDARD 4. None 5. Premium 6. NONE 7. No service level preference ? 2 Subscribing to service level Standard Actual results: completes the auto-subscribing process and then asks you to choose a service-level Expected results: Service-level should be chosen before auto-subscribe process is complete Additional info:
*** This bug has been marked as a duplicate of bug 840169 ***