Hey Sam,
As I mentioned in comment #4, this occurred due to the fact a newer
kernel (4.15~94.95), was installed as a result from the dist upgrade. It
would appear that you have enabled -proposed in /etc/apt/sources.list,
which is the reason why in your logs. the 4.15.0-94.95 kernel is trying
to install.
zipl.conf updated the configs to boot from the newly installed kernel.
As a result the linux-fips kernel takes a back seat and is moved up in
the boot order from kernel #0 -> kernel #1
DEBUG - Processing triggers for ureadahead (0.100.0-21) ...
DEBUG - Processing triggers for ureadahead (0.100.0-21) ...
DEBUG - Processing triggers for linux-image-4.15.0-94-generic
(4.15.0-94.95) ...
DEBUG - Processing triggers for linux-image-4.15.0-94-generic
(4.15.0-94.95) ...
DEBUG - /etc/kernel/postinst.d/initramfs-tools:
DEBUG - /etc/kernel/postinst.d/initramfs-tools:
DEBUG - update-initramfs: Generating
/boot/initrd.img-4.15.0-94-generic
DEBUG - update-initramfs: Generating
/boot/initrd.img-4.15.0-94-generic
DEBUG - Using config file '/etc/zipl.conf'
DEBUG - Using config file '/etc/zipl.conf'
DEBUG - Building bootmap in '/boot'
DEBUG - Building bootmap in '/boot'
DEBUG - Adding IPL section 'ubuntu' (default)
DEBUG - Adding IPL section 'ubuntu' (default)
DEBUG - Preparing boot device: vda (0000).
DEBUG - Preparing boot device: vda (0000).
DEBUG - Done.
DEBUG - Done.
DEBUG - /etc/kernel/postinst.d/zz-zipl:
DEBUG - /etc/kernel/postinst.d/zz-zipl:
DEBUG - Using config file '/etc/zipl.conf'
DEBUG - Using config file '/etc/zipl.conf'
DEBUG - Building bootmap in '/boot'
DEBUG - Building bootmap in '/boot'
DEBUG - Adding IPL section 'ubuntu' (default)
DEBUG - Adding IPL section 'ubuntu' (default)
DEBUG - Preparing boot device: vda (0000).
DEBUG - Preparing boot device: vda (0000).
DEBUG - Done.
DEBUG - Done.
DEBUG - Leave Shell::ssh
This is not a bug and working as expected, moving testing of thie kernel to
ckct.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845632
Title:
After dist-upgrade, s390x running X-fips/B-fips kernel will boot into
generic kernel
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Bug description:
Issue found on s390x KVM
Steps:
1. Deploy a s390x KVM with Xenial
2. Enable -proposed
3. Enable FIPS ppa
4. Install the FIPS kernel with linux-fips meta package
5. reboot
6. dist-upgrade
7. reboot
The system will boot into the correct fips kernel on step 5, but it
will boot into the generic kernel in proposed on step 7.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
