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.
Latest released version for SUSE Manager 3.2 is 3.2.3. Make sure you’re on the latest update level.
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 ?