Bug 1328974

Summary:	Self-registering Sat 6 fails: Unable to find available subscriptions for all your installed products.
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Thom Carlin <tcarlin>
Component:	Installation - Satellite	Assignee:	John Matthews <jmatthew>
Status:	CLOSED NOTABUG	QA Contact:	Thom Carlin <tcarlin>
Severity:	high	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	unspecified
Version:	1.0	CC:	bthurber, jesusr
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1329404 (view as bug list)		Environment:
Last Closed:	2016-06-03 18:33:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1329404

Description Thom Carlin 2016-04-20 19:08:48 UTC

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:

Comment 1 Jesus M. Rodriguez 2016-04-21 20:16:50 UTC

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.

Comment 2 Thom Carlin 2016-06-03 18:33:04 UTC

After internal discussions, I was using a SKU with incorrect properties (which customers shouldn't encounter).  Closing.