[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-06-29 04:33 EDT--- IBM bugzilla status->closed, Fix Released for all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-06-14 09:51 EDT--- (In reply to comment #58) > @Niklas, would you please give it another try? I can confirm the installkernel script now works as expected on current Ubuntu 20.4 with Proposed enabled. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-05-17 10:50 EDT--- I just did an "apt update && apt upgrade" on a KVM guest with Ubuntu 20.04 that I had previously used installkernel on with an early version of your updated script: Setting up linux-image-5.4.0-73-generic (5.4.0-73.82) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.12.0-rc8-07595-g446009324fa8 I: /boot/initrd.img.old is now a symlink to initrd.img-5.12.0-rc8-07595-g446009324fa8 I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-73-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-73-generic Setting up alsa-utils (1.2.2-1ubuntu2.1) ... alsa-restore.service is a disabled or a static unit not running, not starting it. alsa-state.service is a disabled or a static unit not running, not starting it. Setting up procps (2:3.3.16-1ubuntu2.1) ... Setting up bind9-dnsutils (1:9.16.1-0ubuntu2.8) ... Setting up cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.04.2) ... Setting up linux-modules-extra-5.4.0-73-generic (5.4.0-73.82) ... Setting up linux-image-generic (5.4.0.73.76) ... Setting up linux-generic (5.4.0.73.76) ... Setting up python3-distupgrade (1:20.04.32) ... Setting up ubuntu-release-upgrader-core (1:20.04.32) ... Setting up python3-update-manager (1:20.04.10.7) ... Setting up update-manager-core (1:20.04.10.7) ... Setting up update-notifier-common (3.192.30.7) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for rsyslog (8.2001.0-1ubuntu1.1) ... Processing triggers for systemd (245.4-4ubuntu3.6) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.12.0-rc8-07595-g446009324fa8 <--- this is the currently running kernel installed with installkernel Not invoking zipl: initrd doesn't exist yet Processing triggers for linux-image-5.4.0-73-generic (5.4.0-73.82) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic Not invoking zipl: initrd doesn't exist yet /etc/kernel/postinst.d/zz-zipl: Not invoking zipl: initrd doesn't exist yet <--- but above it said it generated ?it!? So usually I would expect that upgrading the kernel after having used installkernel will afterwards use the new distro kernel. Am I correct in that assumption? It might also be that this system is somehow in a weird state but would like confirmation either way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-29 10:52 EDT--- (In reply to comment #41) > Hm, I think I know what went wrong. In my local tree the new script is > executable but that seems to get lost when going via debdiff. Right now it > likely will start to work doing a "chmod a+x > /etc/kernel/postinst.d/xx-update-initrd-links". Great find! After doing the chmod a+x and redoing installkernel the symlink is correct. --- Comment From niklas.schne...@ibm.com 2021-04-29 10:53 EDT--- Oh and I see the following output: Testing softlinks in /boot/... /boot/initrd.img invalid target (initrd.img-5.4.0-73-generic) Softlink: /boot/initrd.img -> initrd.img-5.12.0-07607-g8029c2a40054 /boot/initrd.img.old invalid target (initrd.img-5.4.0-72-generic) Softlink: /boot/initrd.img.old -> initrd.img-5.12.0-07607-g8029c2a40054.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-29 04:39 EDT--- Redid the test on a freshly installed Focal + Proposed + "apt update && apt upgrade". Still the same behavior: root@t46lp77:~/testkernel# installkernel 5.12.0-07607-g8029c2a40054 bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 update-initramfs: Generating /boot/initrd.img-5.12.0-07607-g8029c2a40054 Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: sdn. Done. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 run-parts: executing /etc/kernel/postinst.d/update-notifier 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: sdn. Done. root@t46lp77:~/testkernel# ls -l /boot total 103288 -rw-r--r-- 1 root root 4475592 Apr 29 08:35 System.map-5.12.0-07607-g8029c2a40054 -rw--- 1 root root 3099673 Apr 12 15:12 System.map-5.4.0-72-generic -rw--- 1 root root 3100152 Apr 14 16:35 System.map-5.4.0-73-generic -rw--- 1 root root45056 Apr 29 08:36 bootmap -rw-r--r-- 1 root root90468 Apr 12 15:12 config-5.4.0-72-generic -rw-r--r-- 1 root root90468 Apr 14 16:35 config-5.4.0-73-generic lrwxrwxrwx 1 root root 27 Apr 29 08:19 initrd.img -> initrd.img-5.4.0-73-generic -rw-r--r-- 1 root root 20355770 Apr 29 08:36 initrd.img-5.12.0-07607-g8029c2a40054 -rw-r--r-- 1 root root 24195082 Apr 29 08:19 initrd.img-5.4.0-72-generic -rw-r--r-- 1 root root 24199441 Apr 29 08:19 initrd.img-5.4.0-73-generic lrwxrwxrwx 1 root root 27 Apr 28 15:27 initrd.img.old -> initrd.img-5.4.0-72-generic lrwxrwxrwx 1 root root 34 Apr 29 08:35 vmlinuz -> vmlinuz-5.12.0-07607-g8029c2a40054 -rw-r--r-- 1 root root 9744384 Apr 29 08:35 vmlinuz-5.12.0-07607-g8029c2a40054 -rw--- 1 root root 8172088 Apr 12 16:56 vmlinuz-5.4.0-72-generic -rw--- 1 root root 8172088 Apr 14 16:37 vmlinuz-5.4.0-73-generic lrwxrwxrwx 1 root root 24 Apr 29 08:19 vmlinuz.old -> vmlinuz-5.4.0-73-generic The vmlinuz link is updated correctly but the initrd.img links (initrd.img and initrd.img.old) are not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-28 06:44 EDT--- (In reply to comment #36) > The second attempt seems to have been made without undoing the files and > links created by the old setup. The cases to handle with that mix get rather > hard to handle. So if possible I would rather ask for to check whether the > updated script works in a clean environment forward before marking this as > failed. I'll redo the test with a prestine (despite update to Focal Proposed) system, it should be noted though that at least the initrd.img symlink at the second attempt was created by the normal kernel update. What other links/files should I look into? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-27 09:16 EDT--- I just tested the installkernel script on Ubuntu 20.04 + Focal Proposed with linux-base 4.5ubuntu3.2. I performed the following testing on a s390x z15 LPAR: # 5.12.0-07600-g75079231a966.tar is a tar of the modules compiled on another system % ls 5.12.0-07600-g75079231a966.tar System.map bzImage % tar -xavf 5.12.0-07600-g75079231a966.tar -C /usr/ % installkernel 5.12.0-07600-g75079231a966 bzImage System.map /boot After that with the previous linux-base version I see the following: % ls -la /boot total 68556 drwxr-xr-x 2 root root 4096 Apr 27 12:56 . drwxr-xr-x 20 root root 4096 Apr 27 08:33 .. -rw-r--r-- 1 root root 4475596 Apr 27 12:56 System.map-5.12.0-07600-g75079231a966 -rw--- 1 root root 3099673 Apr 12 15:12 System.map-5.4.0-72-generic -rw--- 1 root root45056 Apr 27 12:56 bootmap -rw-r--r-- 1 root root90468 Apr 12 15:12 config-5.4.0-72-generic lrwxrwxrwx 1 root root 27 Apr 27 08:34 initrd.img -> initrd.img-5.4.0-72-generic -rw-r--r-- 1 root root 20356043 Apr 27 12:56 initrd.img-5.12.0-07600-g75079231a966 -rw-r--r-- 1 root root 24196892 Apr 27 12:46 initrd.img-5.4.0-72-generic lrwxrwxrwx 1 root root 27 Apr 27 08:34 initrd.img.old -> initrd.img-5.4.0-72-generic lrwxrwxrwx 1 root root 34 Apr 27 12:56 vmlinuz -> vmlinuz-5.12.0-07600-g75079231a966 -rw-r--r-- 1 root root 9744384 Apr 27 12:56 vmlinuz-5.12.0-07600-g75079231a966 -rw--- 1 root root 8172088 Apr 12 16:56 vmlinuz-5.4.0-72-generic lrwxrwxrwx 1 root root 24 Apr 27 08:34 vmlinuz.old -> vmlinuz-5.4.0-72-generic Note the wrong initrd.img symlink still pointing at initrd.img-5.4.0-72-generic After the upate and performing the same steps again I get: % ls -la /boot total 117188 drwxr-xr-x 2 root root 4096 Apr 27 13:13 . drwxr-xr-x 20 root root 4096 Apr 27 08:33 .. -rw-r--r-- 1 root root 4475596 Apr 27 13:13 System.map-5.12.0-07600-g75079231a966 -rw-r--r-- 1 root root 4475596 Apr 27 12:56 System.map-5.12.0-07600-g75079231a966.old -rw--- 1 root root 3099673 Apr 12 15:12 System.map-5.4.0-72-generic -rw--- 1 root root 3100152 Apr 14 16:35 System.map-5.4.0-73-generic -rw--- 1 root root45056 Apr 27 13:13 bootmap -rw-r--r-- 1 root root90468 Apr 12 15:12 config-5.4.0-72-generic -rw-r--r-- 1 root root90468 Apr 14 16:35 config-5.4.0-73-generic lrwxrwxrwx 1 root root 27 Apr 27 13:03 initrd.img -> initrd.img-5.4.0-73-generic -rw-r--r-- 1 root root 20355627 Apr 27 13:13 initrd.img-5.12.0-07600-g75079231a966 -rw-r--r-- 1 root root 24196892 Apr 27 12:46 initrd.img-5.4.0-72-generic -rw-r--r-- 1 root root 24204650 Apr 27 13:04 initrd.img-5.4.0-73-generic lrwxrwxrwx 1 root root 37 Apr 27 13:03 initrd.img.old -> initrd.img-5.12.0-07600-g75079231a966 lrwxrwxrwx 1 root root 34 Apr 27 13:13 vmlinuz -> vmlinuz-5.12.0-07600-g75079231a966 -rw-r--r-- 1 root root 9744384 Apr 27 13:13 vmlinuz-5.12.0-07600-g75079231a966 -rw-r--r-- 1 root root 9744384 Apr 27 12:56 vmlinuz-5.12.0-07600-g75079231a966.old -rw--- 1 root root 8172088 Apr 12 16:56 vmlinuz-5.4.0-72-generic -rw--- 1 root root 8172088 Apr 14 16:37 vmlinuz-5.4.0-73-generic lrwxrwxrwx 1 root root 24 Apr 27 13:03 vmlinuz.old -> vmlinuz-5.4.0-73-generic So this does NOT seem to be fixed. Do note that during the dpkg based kernel install the symlink is updated correctly as can be seen by the symlink after installing Proposed updates now pointing to initrd.img-5.4.0-73-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-12-07 05:17 EDT--- (In reply to comment #23) > Could someone try to put the attached script into /etc/kernel/postinst.d and > let me know whether that make installkernel work? Thanks. I can confirm this works with installkernel and the previously described workflow on Ubuntu 20.04.1! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-07-20 12:57 EDT--- (In reply to comment #19) > On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote: > > > > (In reply to comment #17) > > > Eoan and later d-i, new installer, curtin do not install > > > /etc/kernel-img.conf. > > > Upgraded systems keep having it (ie. installed with bionic or xenial, and > > > upgraded). > > > > > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ > > > sudo > > > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make > > > install? > > > > > > Cause the expectation is that `/etc/kernel-img.conf` should not be there, > > > yet everything should still work correctly. > > > > > > I think somewhere something is reading "link_in_boot=yes" and was not > > > updated with the new implicit default to always assume that on recent > > > ubuntu. > > > > For me the installkernel script (including in the current case "sudo > > make install" from a mainline Linux tree) doesn't update the > > /boot/initrd.img symlink. > > > > Interestingly a package upgrade for linux-generic does overwrite this > > symlink. > > .deb package uses very different maintainer scripts / codepath, and is > not the same operation as "sudo make install". > > I personally always build my kernels as debs, and install debs, rather > than doing "sudo make install". But I am a distribution developer, and > I care for .debs to work right. Kernel developers, I guess, are > inverse, and care for "upstream" $ sudo make install to work. > > > > > Not with the /etc/kernel-img.conf[0] and not without it either. > > As before the /boot/vmlinuz link is always updated. > > > > That is slightly concerning, as to how $ sudo make install, ever > worked before. Or what has changed since. > > Normally, $ sudo make install, should lookup if /sbin/installkernel is > available, and call that to "do what it has to do, on a given > distribution", and that script is shipped by the debianutils package > which is required and must be installed always. And it hasn't been > touched in ages. > > I wonder which arguments are passed to /sbin/installkernel by $ sudo > make install. And whether the 4th argument is passed, and if it is > empty, /, or /boot. It should be either empty, or /boot. > > -- > Regards, > > Dimitri. So when I built on a beefy development server I usually copy a tar of the modules + bzImage + System.map and e.g.: # sudo tar -xavf 5.8.0-rc6-06703-g93c67d794cfc.tar -C /usr/ # sudo installkernel 5.8.0-rc6-06703-g93c67d794cfc bzImage System.map /boot that works well on RHEL, Fedora, SUSE and I'm pretty sure it worked on Ubuntu only a week prior to me opening this Bugzilla. I also looked in the history and didn't find anything so yeah I'm pretty confused how that used to work on Ubuntu but I've even bisected like that (on Ubuntu) so have used that approach dozens of times. Of course for us working with multiple distros there's a lot of value in this working the same on all of them and I think that's the main point of the installkernel script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1877088] Comment bridged from LTC Bugzilla
On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote: > > --- Comment From niklas.schne...@ibm.com 2020-06-26 09:45 EDT--- > (In reply to comment #17) > > Eoan and later d-i, new installer, curtin do not install > > /etc/kernel-img.conf. > > Upgraded systems keep having it (ie. installed with bionic or xenial, and > > upgraded). > > > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ sudo > > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make > > install? > > > > Cause the expectation is that `/etc/kernel-img.conf` should not be there, > > yet everything should still work correctly. > > > > I think somewhere something is reading "link_in_boot=yes" and was not > > updated with the new implicit default to always assume that on recent > > ubuntu. > > For me the installkernel script (including in the current case "sudo > make install" from a mainline Linux tree) doesn't update the > /boot/initrd.img symlink. > > Interestingly a package upgrade for linux-generic does overwrite this > symlink. .deb package uses very different maintainer scripts / codepath, and is not the same operation as "sudo make install". I personally always build my kernels as debs, and install debs, rather than doing "sudo make install". But I am a distribution developer, and I care for .debs to work right. Kernel developers, I guess, are inverse, and care for "upstream" $ sudo make install to work. > > Not with the /etc/kernel-img.conf[0] and not without it either. > As before the /boot/vmlinuz link is always updated. > That is slightly concerning, as to how $ sudo make install, ever worked before. Or what has changed since. Normally, $ sudo make install, should lookup if /sbin/installkernel is available, and call that to "do what it has to do, on a given distribution", and that script is shipped by the debianutils package which is required and must be installed always. And it hasn't been touched in ages. I wonder which arguments are passed to /sbin/installkernel by $ sudo make install. And whether the 4th argument is passed, and if it is empty, /, or /boot. It should be either empty, or /boot. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-06-26 09:45 EDT--- (In reply to comment #17) > Eoan and later d-i, new installer, curtin do not install > /etc/kernel-img.conf. > Upgraded systems keep having it (ie. installed with bionic or xenial, and > upgraded). > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ sudo > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make > install? > > Cause the expectation is that `/etc/kernel-img.conf` should not be there, > yet everything should still work correctly. > > I think somewhere something is reading "link_in_boot=yes" and was not > updated with the new implicit default to always assume that on recent ubuntu. For me the installkernel script (including in the current case "sudo make install" from a mainline Linux tree) doesn't update the /boot/initrd.img symlink. Interestingly a package upgrade for linux-generic does overwrite this symlink. Not with the /etc/kernel-img.conf[0] and not without it either. As before the /boot/vmlinuz link is always updated. [0] # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = yes do_initrd = yes link_in_boot = yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-06-02 10:15 EDT--- "make install" also triggers initramfs creation as does manual invocation of the installkernel script. In fact both even trigger boot loader update/install. This is the output: $ sudo make install sh -x ./arch/s390/boot/install.sh 5.4.27 arch/s390/boot/bzImage \ System.map "/boot" + [ -x /root/bin/installkernel ] + [ -x /sbin/installkernel ] + exec /sbin/installkernel 5.4.27 arch/s390/boot/bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.27 /boot/vmlinuz-5.4.27 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.27 /boot/vmlinuz-5.4.27 update-initramfs: Generating /boot/initrd.img-5.4.27 Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper /boot Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dm-0. Done. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 5.4.27 /boot/vmlinuz-5.4.27 run-parts: executing /etc/kernel/postinst.d/update-notifier 5.4.27 /boot/vmlinuz-5.4.27 run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.4.27 /boot/vmlinuz-5.4.27 Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper /boot Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dm-0. Done. I did already have /etc/kernel-img.conf with the following content: # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = yes do_initrd = yes link_in_boot = yes Could this depend on the legacy installer? Our automatically installed systems are currently all installed with it and I also used that for this test LPAR (that has PCI Physical Functions) since the legacy installer allowed a much nicer manual network configuration using the HMC console. Sadly that's also why I can't currently test on another fresh install as our automatic installation system is currently being changed to support the new installer and I couldn't get the previous workaround to work today. I'm not knowledgeable enough to give a good opinion on initrd less boot but I would suspect that the deployments at our customers are much more varied than the average cloud so I would be hesitant about defaulting to it. Also in my experience s390 boot times are already quite good. Afaik with our defconfig a lot of us developers regularly boot without initrd or even any modules, so supporting it shouldn't be a problem. As the defconfig doesn't include the drivers for PCI devices into the Kernel I usually use both modules and an initrd, which might be why I stumbled over this first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-06-02 07:57 EDT--- I usually compile on a development machine and then scp a tar archive of the modules and the vmlinuz e.g. to a z/VM guest with less memory and CPU. Previously this worked the same across all distros which makes this very practical for us. That said, I've now tried with a locally build Kernel (from the focal Kernel repository master branch) with the following sequence: (As build dependencies I installed build-essential, bison, flex, and libssl-dev) $ make defconfig (defconfig is what we usually use internally but I don't think this changes anything) $ make -j $(nproc) $ sudo make modules_install $ sudo make install With this I also see the same issue /boot/vmlinuz is freshly symlinked but /boot/initrd.img keeps pointing to the previous kernel installed as a deb. E.g. below that was the PPA Kernel from the other issue: $ ls -l /boot/initrd.img lrwxrwxrwx 1 root root 37 Jun 2 04:37 /boot/initrd.img -> initrd.img-5.4.0-31.35ubuntu2-generic $ ls -l /boot/vmlinuz lrwxrwxrwx 1 root root 14 Jun 2 05:57 /boot/vmlinuz -> vmlinuz-5.4.27 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-26 04:21 EDT--- I've only seen this happen with manually using the installkernel script with the commands included in my first comment. I will have to try if it also occurs with "make install" in a kernel tree. I currently have a small vacation, just keeping the critical bugs progressing, but will try once I'm working again. As for different setups, I've seen this on two separate installations one on LPAR and one in z/VM, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-13 09:53 EDT--- I'm now getting the same behavior on a fresh Ubuntu 18.04 (including apt update && apt upgrade). This really makes testing kernels very frustrating especially with the Ubuntu config that unlike defconfig doesn't have the dasd and qeth drivers compiled in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-06 08:06 EDT--- To add, I'm pretty sure this broke in a very recent change as we were using the installkernel script extensively just last week. Also I believe there is something in the usual kernel upgrade process that hides this issue as kernel upgrades via apt seem to work fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
