openSUSE Leap 15.2 can not be migrated to openSUSE Leap 15.3 using SUSE Manager

This document (000020823) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 4.3 Server

Situation

When the service package migration of openSUSE Leap 15.2 was selected (and scheduled) to openSUSE Leap 15.3, the product was always migrated to SUSE Linux Enterprise Server 15 SP2.

Resolution

It is needed to remove all packages from affected channel and let repo-sync add the right packages back. The commands below do not delete the packages nor remove them from SUSE Manager Server. It just removes the "link" which tells SUSE Manager Server which packages belong into which channel.

spacewalk-sql --select-mode - <<< "delete from rhnchannelpackage where channel_id in (select id from rhnchannel where label = 'sle-15-sp3-updates-x86_64-opensuse-15.3');"

spacewalk-repo-sync -c sle-15-sp3-updates-x86_64-opensuse-15.3

The spacewalk-repo-sync should mostly link the packages back and it may take few minutes.

Cause

At some point sles-release package for SUSE Linux Enterprise Server 15 SP2 appeared (and then was removed) in sle-15-sp3-updates-x86_64-opensuse-15.3 repository and it was synced into the SUSE Manager Server. Having such package in mentioned channel was causing that the service pack migration offered SUSE Linux Enterprise Server 15 SP2 as target product instead of openSUSE Leap 15.3.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.