In short: Product-SLES15-SP2-Pool is for SLES 15SP2 Product-SLES15-Pool is for SLES 15 with no SP (so you can call it SLES 15SP0 as well, as some people call it) The correct Pool must be used for your SP version. I am not aware of how the HEP ssacli works, but if the repository is realy valid for all SLE15 versions, then: 1. Create a repository with that URL 2. Create one subchannel as a child of each Product-SLES15*-Pool channel 3. Assign the repository to all those channels. Then you can work with Content Lifecycle Management normally :-) Best regards. On lunes, 12 de julio de 2021 15:56:10 (CEST) Heiner Wulfhorst wrote:
Hi List,
i need HPE ssacli on my uyuni managed Systems, so i added this Repository as a Custom Channel: https://downloads.linux.hpe.com/SDR/repo/spp-gen10/SUSE/15/x86_64/current/ As it seems to be for all SLES Service Packs i created it as a child to the parent channel "SLE-Product-SLES15-Pool for x86_64".
My managed Systems have been installed with SLES SP2, so i added them to a staged ("lifecycle management") version of Base Channel "SLE-Product-SLES15- *SP2*-Pool for x86_64".
1. Within my Lifecycle Project I can add the "foreign" Child Channel to my Systems. But how would I accomplish this if my systems would be using the latest / upstream version? 2. Is there a "better" way to add Service Pack independent Software to my systems? 3. Should i even use "Product-SLES15-*SP2*-Pool" as a base channel for my Systems, or would it be better to use the general " Product-SLES15-Pool"? 4. What is the difference between "Product-SLES15-*SP2*-Pool" and "Product-SLES15-Pool", how/when should they be used?
Hope to get a better understanding of how it is meant to be used so i can avoid possible future problems!
Thanks! Heiner
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com