On lunes, 19 de abril de 2021 15:23:50 (CEST) Heiner Wulfhorst wrote:
We are using SLES Clients and in the past they were connected to our RMT /
Reposerver using SUSEConnect command.
Now that i have bootstrapped some SLES Clients to use my Uyuni Server with
salt, "SUSEConnect -l" says:
"To list extensions, you must first register the base product, using:
SUSEConnect -r <registration code>"
Is this the normal/wanted behavior as repos are pushed actively from Server
to Client, or what should i do to make them know they belong to my uyuni
It's the normal behaviour. If you bootstrap (and therefore register) the SLE
client at Uyuni, the repositories will be always managed by Uyuni. No need to
use SUSEConnect anymore.
If we are talking about SLE15 and you need to add more modules to that client,
just sync them via the Setup Wizard and (when synced) add them to the client via
WebUI, spacecmd, API...
If you need to do that for a lot of clients, you can use (for example) the
System Set Manager:
Of course this way you can have as many SLE systems as you want, but remember
you to be in compliance with your license. The subscription-matcher feature can
help you with that:
Julio González Gil
Release Engineer, SUSE Manager and Uyuni