[Bug 2072366] [NEW] s390-tools zipl breaks when user provides target attributes

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Frank Heimes (fheimes):

This issue has already been identified and fixed in the (upstream?)
github repository:
https://github.com/ibm-s390-linux/s390-tools/commit/63ff07ba38dda99e2661a097d05266555c727a2e

The issue fixed by the revert linked above is causing Cloudware Oracular
download image builds to fail on s390x. From the image build log:

```
+ ZIPL_EXTRA_PARAMS=--ramdisk=/boot/initrd.img
+ chroot mountpoint /sbin/zipl -V --image=/boot/vmlinuz --parameters=root=LABEL=cloudimg-rootfs --target=/boot/ --targetbase=/dev/loop3 --targettype=SCSI --targetblocksize=512 --targetoffset=2048 --ramdisk=/boot/initrd.img
Error: Could not add image file '/boot/vmlinuz': Could not get disk geometry
Looking for components in '/lib/s390-tools'
Secure boot support: no
Target device information
  Device..........................: 07:03
  Device name.....................: loop3 *)
  Device driver name..............: blkext
  Type............................: disk device
  Disk layout.....................: SCSI disk layout *)
  Geometry - start................: 2048 *)
  File system block size..........: 4096
  Physical block size.............: 512 *)
  Device size in physical blocks..: 4608000
  *) Data provided by user.
Building bootmap in '/boot/'
Adding IPL section
  initial ramdisk...: /boot/initrd.img
  kernel image......: /boot/vmlinuz
zIPL environment block content:
```

The fix is in the github repo but not yet released. The LP builders for
Oracular are using version 2.33.1, which contains the bug.

** Affects: ubuntu-z-systems
     Importance: High
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: In Progress

** Affects: s390-tools (Ubuntu)
     Importance: High
         Status: In Progress


** Tags: s390x
-- 
s390-tools zipl breaks when user provides target attributes
https://bugs.launchpad.net/bugs/2072366
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.