Hello together, openQA can not release openSUSE Tumbleweed at the moment, because the system is hanging after the package installation and the restart with following message: Use the ^ and v keys to select which entry is highlighted. Press ', ' enter to boot the selected OS, `e\' to edit the commands before ', ' booting or `c\' for a command-line. ', ' *(1) openSUSE Tumbleweed ', ' (2) Advanced options for openSUSE Tumbleweed ', ' (s) Start bootloader from a read-only snapshot ', 'Welcome to GRUB! ', ' GNU GRUB version 2.06 ', ' Use the ^ and v keys to select which entry is highlighted. Press ', ' enter to boot the selected OS, `e\' to edit the commands before ', ' booting or `c\' for a command-line. ', ' *(1) openSUSE Tumbleweed ', ' (2) Advanced options for openSUSE Tumbleweed ', ' (s) Start bootloader from a read-only snapshot ', ' Loading Linux 5.15.8-1-default ... ', ' Loading initial ramdisk ... ', ' Performing \'kexec -la /boot/image-5.15.8-1-default ', ' --initrd=/boot/initrd-5.15.8-1-default ', ' --command-line=root=UUID=543317df-6bd2-437a-aa2c-65af592d4efb ', ' hvc_iucv=8 TERM=dumb crashkernel=195M mitigations=auto\' ', ' Performing \'systemctl kexec\' (just-in-case) Running in chroot, ignoring command', ' \'kexec\' ', 'Performing \'kexec -e -x\'01: HCPGSP2629I The virtual machine is placed in CP mode', ' due to a SIGP stop from ', ' CPU 00. CP commands are based on s390-tools. If I am looking for the last kexec output, that can be a part for a successful boot process or a "CP IPL" command is required for the integration of z/FCP disks. But we are using DASD disks in this test. I need the more experienced zLinux Users on this mailing list now. We had an update of s390-tools last month. Is that a misconfiguration and we have to add new additional steps for these test cases? Or is that a bug? It seems that GRU>B can be started. The kernel can also be found. Is that a bug in s390-tools then? Thank you for your feedback! Best regards, Sarah