PDA

View Full Version : [SUMA 3.2] Service Pack Migration with custom channels



timstein
26-Nov-2018, 13:55
Hello,

This is about SUSE Manager 3.2.12.

Currently we are testing the Service Pack Migration support with custom channels from SLES 12 SP2 to SLES 12 SP3. According to this document: https://www.suse.com/documentation/suse-best-practices/singlehtml/susemanager/susemanager.html#sec.implement (2.6.1.1 Service Pack Migration Support with Update and Exception Channels) the basic prerequisite is the creation of a full clone-tree. We did this for SLES 12 SP2 and SLES 12 SP3. However, the Service Pack Migration feature still only presents the original SUSE channels with the corresponding base products. We cannot choose our SLES 12 SP3 clone-tree.

Any hints what might be wrong?

Thanks and best regards
Tim

kwk
27-Nov-2018, 08:05
Hello,

This is about SUSE Manager 3.2.12.


Latest released version for SUSE Manager 3.2 is 3.2.3. Make sure you're on the latest update level.




However, the Service Pack Migration feature still only presents the original SUSE channels with the corresponding base products. We cannot choose our SLES 12 SP3 clone-tree.


SP migration needs to backtrack the origin for every channel to the corresponding SUSE channel in order to verify the migration path. Are all clones originating from SUSE vendor channels ?

timstein
29-Nov-2018, 08:09
Latest released version for SUSE Manager 3.2 is 3.2.3. Make sure you're on the latest update level.
You are absolutely right. SUSE Manager is on version 3.2,3. I mentioned the RPM‘s version.


SP migration needs to backtrack the origin for every channel to the corresponding SUSE channel in order to verify the migration path. Are all clones originating from SUSE vendor channels ?
Yes, I think all clones are originating from SUSE vendor channels as the following command was used:

spacecmd -- softwarechannel_clonetree -s sles12-sp3-pool-x86_64 -p "clonetree-"

The result looks as follows:

clonetree-sles12-sp3-pool-x86_64
clonetree-prod-security-asap-sles-12-sp3-updates-x86_64
clonetree-prod-sle-manager-tools-12-sp3-updates-x86_64
clonetree-prod-sle-module-containers-12-sp3-updates-x86_64
clonetree-prod-sle-module-web-scripting-12-sp3-updates-x86_64
clonetree-prod-sles12_sp3_custom_softwarepakete_x86_64
clonetree-prod-sles-12-sp3-updates-x86_64
clonetree-prod-sle-sdk-12-sp3-updates-x86_64
clonetree-sle-manager-tools12-pool-x86_64-sp3
clonetree-sle-module-containers12-pool-x86_64-sp3
clonetree-sle-module-web-scripting12-pool-x86_64-sp3
clonetree-sles12_sp3_custom_log-management_server_x86_64
clonetree-sles12_sp3_custom_monitoring_server_x86_64
clonetree-sles12_sp3_server_monitoring_software_x86_64
clonetree-sles12_sp3_thruk_monitoring_x86_64
clonetree-sle-sdk12-sp3-pool-x86_64
clonetree-test-security-asap-sles-12-sp3-updates-x86_64
clonetree-test-sle-manager-tools-12-sp3-updates-x86_64
clonetree-test-sle-module-containers-12-sp3-updates-x86_64
clonetree-test-sle-module-web-scripting-12-sp3-updates-x86_64
clonetree-test-sles12_sp3_custom_softwarepakete_x86_64
clonetree-test-sles-12-sp3-updates-x86_64
clonetree-test-sle-sdk-12-sp3-updates-x86_64

timstein
30-Nov-2018, 08:55
We opened a SR at SUSE.