Description of problem: "In the following section of the SAM usage guide: 2.2. Basic Installation and Setup for Subscription Asset Manager https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1/html/Using_Subscription_Asset_Manager/sam-installing-packages.html there are three sections: 2.2.1. Installing Using yum 2.2.2. Installing Through an ISO 2.2.3. Installing Packages for Enhanced Reporting The first two sections include the steps for installing the basic (non-splice-related) packages and running the configuration script. There's no advanced warning about the differences involved in the third section, so that if the customer first runs the steps in one of the first two sections, he/she won't be able to configure a working reporting server. The third section goes on to reference a later section: 8.7. Using Subscription Asset Manager to Generate Satellite Usage Reports https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1/html/Using_Subscription_Asset_Manager/sam-splice.html which repeats the installation steps, and goes on to include additional steps that are required to connect the SAM server to the Satellite server. It would probably make more sense to include the link to section 8.7 at the very beginning of section 2.2, with language clearly stating that the steps that follow in sections 2.2.1 and 2.2.2 are only for non-reporting SAM server configuration." Version-Release number of selected component (if applicable): SAM 1.3 How reproducible: always Steps to Reproduce: 1. see above 2. 3. Actual results: Expected results: better clarify/highlight install steps for enhanced reporting vs non-enhanced reporting SAM installs otherwise customers have to re-install Additional info:
The release of Satellite 5.8 we are deprecating the support of Subscription Asset Manager. The release notes for 5.8 can be found at https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/pdf/release_notes/Red_Hat_Satellite-5.8-Release_Notes-en-US.pdf. I am therefore closing out this bug as WONTFIX. If you believe this to be an error, please feel free tor each out to either Rich Jerrido or Bryan Kearney. Thank you!