After bootstrapping this client (Salt-SSH), the following is the list of repositories
# | Alias | Name | Enabled | GPG Check | Refresh
--+------------------------------------------------------------+--------------------------------------------+---------+-----------+--------
1 | SMT-http_smt:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | No | ---- | ----
2 | SMT-http_smt:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | No | ---- | ----
3 | SMT-http_smt:SLES12-SP2-LTSS-Updates | SLES12-SP2-LTSS-Updates | No | ---- | ----
4 | SMT-http_smt:SLES12-SP2-Pool | SLES12-SP2-Pool | No | ---- | ----
5 | SMT-http_smt:SLES12-SP2-Updates | SLES12-SP2-Updates | No | ---- | ----
6 | susemanager:sle-manager-tools12-pool-x86_64-sp2 | SLE-Manager-Tools12-Pool for x86_64 SP2 | Yes | ( p) Yes | Yes
7 | susemanager:sle-manager-tools12-updates-x86_64-sp2 | SLE-Manager-Tools12-Updates for x86_64 SP2 | Yes | ( p) Yes | Yes
8 | susemanager:sles12-sp2-pool-x86_64 | SLES12-SP2-Pool for x86_64 | Yes | ( p) Yes | Yes
9 | susemanager:sles12-sp2-updates-x86_64 | SLES12-SP2-Updates for x86_64 | Yes | ( p) Yes | Yes
Note that “Web and Scripting Module” is not present, even though it is correctly synced within Suma:
Mandatory Channels
SLE-Module-Web-Scripting12-Pool for x86_64 synced
sle-module-web-scripting12-pool-x86_64-sp2
SLE-Module-Web-Scripting12-Updates for x86_64 synced
sle-module-web-scripting12-updates-x86_64-sp2
How is the detection of existing and enabled modules taking place during bootstrap? What do we need to do to make sure the client is onboarded 1:1?
We do not want to worrying about missing products/modules after bootstrapping the client in Suma.
Here are the release packages:
# rpm -qa | grep -i release | sort
lsb-release-2.0-28.1.noarch
release-notes-sles-12.2.20200504-5.34.2.noarch
sle-manager-tools-release-12-10.3.1.x86_64
sle-manager-tools-release-POOL-12-1.20.x86_64
sle-module-web-scripting-release-12-10.3.1.x86_64
sle-module-web-scripting-release-POOL-12-1.119.x86_64
sle-sdk-release-12.2-1.124.x86_64
sle-sdk-release-POOL-12.2-1.124.x86_64
sles-ltss-release-12.2-8.4.1.x86_64
sles-ltss-release-POOL-12.2-8.4.1.x86_64
sles-release-12.2-1.539.x86_64
sles-release-DVD-12.2-1.539.x86_64
SUSEConnect shows the product as being activated and it’s listed in /etc/products.d/ too:
total 36
drwxr-xr-x 2 root root 4096 Feb 1 18:04 ./
drwxr-xr-x 130 root root 12288 Jan 29 19:01 ../
-rw-r--r-- 1 root root 2650 Apr 10 2018 SLES-LTSS.prod
-rw-r--r-- 1 root root 2917 Oct 25 2016 SLES.prod
lrwxrwxrwx 1 root root 9 Oct 13 2017 baseproduct -> SLES.prod
-rw-r--r-- 1 root root 1553 Mar 23 2018 sle-manager-tools.prod
-rw-r--r-- 1 root root 2254 Nov 23 2017 sle-module-web-scripting.prod
-rw-r--r-- 1 root root 2369 Oct 7 2016 sle-sdk.prod
Note that in this particular case it didn’t detect LTS either.
(Suma 4.1.4)