Upgrading from SLES15 SP7 to SLES 16.0 failed!

Hi Ahmad,

here is the result of my last try :

htt ps:// drive. proton. me/ urls/ 8ZC77BN8FC#Dc4W9y7xusyw

Pls have look on it …

TIA!

Now we are not getting anymore that encoding issue. But seems this is very similar to: https://support.scc.suse.com/s/kb/SLES-15-SP7-to-SLES-16-Migration-fails-due-to-not-registered-modules?language=en_US , I would advice to check it and if you can remove PackageHub

Let me know the result. Maybe I will need a new supportconfig.

Kindly keep the PackageHub. I was able to reproduce issue similar to yours.

Problem: 1: nothing provides ‘graphviz = 12.2.1’ needed by the to be installed graphviz-gnome-12.2.1-160000.1.1.x86_64

Remove: graphviz and graphviz-gnome

give it a try and let me know the result.

It seems now much better now:

  • after uninstalling graphviz and graphviz-gnome it did finally function(!) , BUT:

uname -a
Linux aipsp6 6.4.0-150700.53.34-default #1 SMP PREEMPT_DYNAMIC Sat Mar 14 01:18:44 UTC 2026 (62c8bca) x86_64 x86_64 x86_64 GNU/Linux

dir /boot/

-rw-r–r-- 1 root root 270613 16. Mär 17:44 config-6.4.0-150700.53.34-default
drwxr-xr-x 3 root root 16384 1. Jan 1970 efi
drwxr-xr-x 7 root root 115 14. Apr 13:20 grub2
lrwxrwxrwx 1 root root 33 27. Mär 14:18 initrd → initrd-6.4.0-150700.53.34-default
-rw------- 1 root root 21549747 27. Mär 14:20 initrd-6.4.0-150700.53.34-default
-rw-r–r-- 1 root root 1554478 16. Mär 17:57 symtypes-6.4.0-150700.53.34-default.gz
-rw-r–r-- 1 root root 360818 16. Mär 17:57 symvers-6.4.0-150700.53.34-default.gz
-rw-r–r-- 1 root root 484 16. Mär 17:57 sysctl.conf-6.4.0-150700.53.34-default
-rw-r–r-- 1 root root 7749547 16. Mär 17:55 System.map-6.4.0-150700.53.34-default
-rw-r–r-- 1 root root 16202418 16. Mär 18:00 vmlinux-6.4.0-150700.53.34-default.gz
lrwxrwxrwx 1 root root 34 27. Mär 14:18 vmlinuz → vmlinuz-6.4.0-150700.53.34-default
-rw-r–r-- 1 root root 14412288 16. Mär 18:30 vmlinuz-6.4.0-150700.53.34-default
-rw-r–r-- 1 root root 65 16. Mär 18:30 .vmlinuz-6.4.0-150700.53.34-default.hmac
lrwxrwxrwx 1 root root 40 27. Mär 14:18 .vmlinuz.hmac → .vmlinuz-6.4.0-150700.53.34-default.hmac

  • very strange: I’d expect kernel version of 6.12.0-160000.27, or sth. like that !?

cat /etc/os-release

The NAME and PRETTY_NAME fields have been chosen to state compatibility between our products.

The use of “SLES” and “SUSE Linux Enterprise” rather than a more generic name is due to backward compatibility with existing OS detection code in applications of third party vendors.

NAME=“SLES”
PRETTY_NAME=“SUSE Linux Enterprise Server 16.0”
VARIANT=“Enterprise Server”
VARIANT_ID=“server”
VERSION=“16.0”
VERSION_ID=“16.0”
ANSI_COLOR=“0;32”
ID=“sles”
ID_LIKE=“suse opensuse”
CPE_NAME=“cpe:/o:suse:sles:16:16.0”
SUSE_SUPPORT_PRODUCT=“SUSE Linux Enterprise Server”
SUSE_SUPPORT_PRODUCT_VERSION=“16.0”
HOME_URL=“https://www.suse.com/products/server/”
DOCUMENTATION_URL=“https://documentation.suse.com/sles/16.0/”
LOGO=“distributor-logo”

→ as it should be …

Thank you!

That’s good to read :wink:

Regarding the kernel, something went wrong because it should boot from new kernel. Take a look at the /var/log/dis* file and check if anything went wrong. You can share it and I will check.

It is not possible to work with the system now - even “vi” don’t work anymore :confused: :

vi /var/log/distro_migration.log
vi: error while loading shared libraries: libperl.so: cannot open shared object file: No such
file or directory

But I managed to copy the migration file anyway - here it is:

htt ps:// drive. proton. me/ urls/ X5BVR5F45R#Mbt1PUuZgkAV

Can you pls check it ?

TIA!

Hi,

looking into this file I see migration failed. That’s why system booted into SP7 Kernel.

2494 packages to upgrade, 107 to downgrade, 1033 new, 190 to remove, 390  to change vendor, 13 to change arch.
...
...
Retrieving: libOpenIPMIui1-2.0.36.56+git.0a3a991-160000.2.2.x86_64 (SLE-Product-SLES-16.0) (1436/3634),  81.4 KiB
Retrieving: libOpenIPMIui1-2.0.36.56+git.0a3a991-160000.2.2.x86_64.rpm [.done]
(1454/3706) Installing: libOpenIPMIui1-2.0.36.56+git.0a3a991-160000.2.2.x86_64 [..
/sbin/ldconfig: /lib64/libldap_r-2.4.so.2 is not a symbolic link
/sbin/ldconfig: /lib64/liblber-2.4.so.2 is not a symbolic link
done]
Retrieving: OpenIPMI-2.0.36.56+git.0a3a991-160000.2.2.x86_64 (SLE-Product-SLES-16.0) (1437/3634), 374.5 KiB
Retrieving: OpenIPMI-2.0.36.56+git.0a3a991-160000.2.2.x86_64.rpm [..done (16.0 KiB/s)]
(1455/3706) Installing: OpenIPMI-2.0.36.56+git.0a3a991-160000.2.2.x86_64 [...
Updating /etc/sysconfig/ipmi ...
Running in chroot, ignoring command 'daemon-reload'
Running in chroot, ignoring command 'try-restart'
done]
Retrieving: postfix-3.10.2-160000.2.2.x86_64 (SLE-Product-SLES-16.0) (1438/3634),   1.4 MiB
Retrieving: postfix-3.10.2-160000.2.2.x86_64.rpm [..done (112.8 KiB/s)]
(1456/3706) Installing: postfix-3.10.2-160000.2.2.x86_64 [..
/usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/postfix-user.conf -
.
warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew
warning: /etc/postfix/master.cf created as /etc/postfix/master.cf.rpmnew
error: unpacking of archive failed on file /var/mail;69de2a2a: cpio: File from package already exists as a directory in system
error: postfix-3.10.2-160000.2.2.x86_64: install failed
error: postfix-3.8.4-150600.3.3.1.x86_64: erase skipped
error]
Installation of postfix-3.10.2-160000.2.2.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): a
Warning: %posttrans and %transfiletrigger scripts are not executed when aborting!

Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
command '/usr/bin/zypper --root /system-root --non-interactive --verbose --releasever 16.0 --no-refresh dist-upgrade --auto-agree-with-licenses --auto-agree-with-licenses --replacefiles --allow-vendor-change' failed
Error: zypper returned 8 with 'Installation of postfix-3.10.2-160000.2.2.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.' (exit status 8)

Migration failed.

The migration to the new service pack has failed. The system is most
likely in an inconsistent state.

We strongly recommend to rollback to a snapshot created before the
migration was started (via selecting the snapshot in the boot menu
if you use snapper) or restore the system from a backup.
'/usr/lib/zypper/commands/zypper-migration' exited with status 2
EXEC: Failed with stderr: (no output on stderr), stdout: (no output on stdout)
migrate service failed with zypper failed with: bash: stderr: (no output on stderr), stdout: (no output on stdout)

Q: is this a test system or production?

The system contains a lot of packages and during migration, a lot of packages changed vendor. E.g.,

	The following 390 packages are going to change vendor:
alee-fonts
  13-1.21 -> 13.3-bp160.1.10
  SUSE LLC <https://www.suse.com/> -> openSUSE


  The following 14 patterns are going to change vendor:
32bit
  20200124-150700.36.1 -> 20241218-bp160.2.2
  SUSE LLC <https://www.suse.com/> -> openSUSE
apparmor

So, you need now to restore the system from valid backup before triggering the migration. Clean up the /etc/hosts and the extra two packages coming from SLE HA , and double check which packages are needed and what packages not needed and can be removed.

My system e.g., has 795 packages, to reproduce your setup, I had to install 2245 extra packages. I would start removing all packages changing vendor to openSUSE, grep for openSUSE in distro_migration.log and remove the packages.

Let me know the result.

Regards,

Ahmad

Hi, this is a test (sample/template/role model) system - I will try it next …

Thank you very much for your help!

error: unpacking of archive failed on file /var/mail;69de2a2a: cpio: File from package already exists as a directory in system

The last migration failed because of above error. Restore from valid backup and remove /var/mail

Aaah, OK - very good idea! Thanks!