Please document the restriction in TP3 that the Entitlement chosen for the Subscription needs to include Smart Management. +++ This bug was initially created as a clone of Bug #1328974 +++ Description of problem: While verifying https://bugzilla.redhat.com/show_bug.cgi?id=1320287, the system was unable to find a subscription for Red Hat Satellite Version-Release number of selected component (if applicable): TP3 RC4 How reproducible: 100% Steps to Reproduce: 1. Install RHCI ISO 2. Log in to run launch-fusor-installer 3. Deploy RHEV 4. Once repositories have sync'd, follow steps in Sat 6.1 Install Guide, Procedure 5.1, steps Steps 7ff (replacing step 8 with 'subscription-manager register --org="Default_Organization" --environment="Library"' and step 10 with 'subscription-manager attach --auto') Actual results: Installed Product Current Status: Product Name: Red Hat Software Collections (for RHEL Server) Status: Subscribed Product Name: Red Hat Enterprise Linux Server Status: Subscribed Product Name: Red Hat Satellite Status: Not Subscribed Unable to find available subscriptions for all your installed products. Expected results: All products successfully subscribed Additional info: --- Additional comment from Jesus M. Rodriguez on 2016-04-21 16:16:50 EDT --- So just to reword the situation: * in the portal configure a subscription mgmt application with MCT2847. An entitlement that does NOT have Satellite * you setup fusor * you kicked off a deployment. During the deployment select the above subscription mgmt appplication * attempt to register the satellite after repos are sync'd. Because there was no satellite entitlement in the one chosen the satellite could not be registered. I believe this scenario should be documented that the user must ensure they have a Satellite entitlement in their SKU if they want to self-register the satellite. We have a backlog item to attempt to calculate the required entitlements for a deployment and self-registering the satellite. I believe that feature will ultimately take care of this situation. Again, for now, simply document it.
Verified in https://access.redhat.com/documentation/en/quickstart-cloud-installer/version-1.0/quickstart-cloud-installer-guide/ Appendix D