s390x squashfs image should include s390-tools

Bug #1664367 reported by Joshua Powers
This bug report is a duplicate of:  Bug #1662346: vmtest: s390x requires zipl command. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
New
Undecided
Unassigned
curtin
New
Undecided
Unassigned
livecd-rootfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

I propose that the s390x cloud-images should contain the s390-tools package by default.

In working on the s390x testing for curtin we discovered that the s390-tools package was missing as we needed to be able to run zipl. After talking to xnox and cpaelzer it was suggested that this package should be in there should you want to do anything useful with a s390x as the package contains many utilities to interact and manage a system.

Joshua Powers (powersj)
summary: - s390x images should include s390x-tools
+ s390x images should include s390-tools
description: updated
Revision history for this message
Dan Watkins (oddbloke) wrote : Re: s390x images should include s390-tools

So on investigation, we actually have the following issues:

- s390-tools is included in the qcow2 image, but is not in the manifest
- s390-tools is not included in the squashfs

I'm guessing you're hitting the latter, so I'm going to modify this to be about that.

summary: - s390x images should include s390-tools
+ s390x squashfs image should include s390-tools
Revision history for this message
Dan Watkins (oddbloke) wrote :

The specific issue here is that s390-tools is installed in live-build/ubuntu-cpc/hooks/032-disk-image.binary (which runs after the squashfs is generated). It should probably instead run in a chroot hook.

Revision history for this message
Dan Watkins (oddbloke) wrote :

xnox points out on IRC that we don't include grub et al in the squashfs for those architectures that use it, so including s390-tools might not be the right thing to do after all.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

s390-tools, and specifically zipl part of that package is a bootloader and only makes sense on images that are booted: e.g. for virtual machines and bare metal. It is kind of like e.g. grub2 in x86_64 world.

squashfs is used for containers.

on amd64, squashfs does not contain grub2, thus s390-tools should be installed just like other bootloaders are installed.

So no, s390-tools should not be installed in the squashfs, but instead installed just before zipl is called to make image/install bootable. How is grub2 installed in amd64 case in MAAS images?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.