missing migration product

SUSE Product Topics SLES Install-Boot
1

Hi,

here is a SLES11SP3 (x86_64) host. Alle Patches are installed. (zypper lp
shows nothing to install) The host is registered to an SLES11-SMT. On the
SMT-Server the migraton pack "SUSE_SLES_SP4-migration-11.3-1.4.x86-64.rpm
" is visible in the repos directory.

But a zypper pd on the host did not shown this migration product. (As add-on
there is a OES2015 installed. The migraton product for the add-on is
visible.)

Where should I start search?

TiA

Bernd

2

Hi Bernd,

[QUOTE=Bernd;33651]Hi,

here is a SLES11SP3 (x86_64) host. Alle Patches are installed. (zypper lp
shows nothing to install) The host is registered to an SLES11-SMT. On the
SMT-Server the migraton pack "SUSE_SLES_SP4-migration-11.3-1.4.x86-64.rpm
" is visible in the repos directory.

But a zypper pd on the host did not shown this migration product. (As add-on
there is a OES2015 installed. The migraton product for the add-on is
visible.)

Where should I start search?[/QUOTE]

since OES imposes certain dependencies regarding updates of the base OS: In the OES-L forums, i.e. https://forums.novell.com/forumdisplay.php/431-OES-L-Install :wink:

Regards,
J

PS: IIRC (I’m no OES guy) OES has it’s own way of upgrading the base OS and blocks the SLES migration package(s)

3

jmozdzen wrote on Dienstag, 26. Juli 2016 15:04 in
suse.support.server.install-boot :

(…)[color=blue]

PS: IIRC (I’m no OES guy) OES has it’s own way of upgrading the base OS
and blocks the SLES migration package(s)[/color]

The way to upgrade is very similar. But OES blocks the package ‘SLES-
migration-product’ until the related OES-Upgrade ist tested and available.
Then an OES-Patch remove the SLES-migration blocker and the upgrade is
possible.

In my case the problem was the SLES11-SP3 repo at the SMT-Server. Someone
has removed the files from the directory =8-O. Only the repodata was
allocatable in the DB, I clean up this repo and now the SLES11 migration
product is visible on the host.

Bernd

4

Hi Bernd,

thanks for reporting back. Having someone remove the actual files from the SMT repos is a very *** reason, indeed :wink:

Regards,
Jens