s390-tools zipl breaks when user provides target attributes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Skipper Bug Screeners | ||
s390-tools (Ubuntu) |
Fix Released
|
High
|
Frank Heimes | ||
s390-tools-signed (Ubuntu) |
Fix Released
|
High
|
Frank Heimes |
Bug Description
This issue has already been identified and fixed in the (upstream?) github repository: https:/
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_
+ chroot mountpoint /sbin/zipl -V --image=
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.
Device name...
Device driver name..............: blkext
Type.
Disk layout.
Geometry - start..
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.
description: | updated |
tags: | added: s390x |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
importance: | Undecided → High |
Changed in s390-tools (Ubuntu): | |
importance: | Undecided → High |
Changed in ubuntu-z-systems: | |
status: | New → In Progress |
Changed in s390-tools (Ubuntu): | |
status: | New → In Progress |
tags: | added: pe-sponsoring-request |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Released |
Thx Cody for this report and you investigation upstream.
An update package, with the above fix included, is currently building in the following PPA: net/~fheimes/ +archive/ ubuntu/ lp2072366
launchpad.
(But btw. why have you attached your Intel ProcCpuinfoMini mal.txt here?)