Ubuntu on IBM z Systems

Installation fails on s390x due to unexpected input for Archive Mirror

Bug #1944675 reported by Frank Heimes on 2021-09-23

8

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu on IBM z Systems	New	Wishlist	Canonical Foundations Team
	curtin	New	Undecided	Unassigned
	subiquity	New	Undecided	Unassigned

Bug Description

I got aware by mail that an installation on s390x fails and ended up in a crash during disk configuration. The crash files are attached, but I also asked for the entire /var/log content.

I've found in the crash file that fdasd got accidentally executed against a device-mapper device (/dev/dm-0) rather than a DASD ECKD device:

"
Running command ['fdasd', '--table', '/dev/dm-0'] with allowed return codes [0] (capture=False)

fdasd error: Unsupported disk type
Disk geometry does not match a DASD device of type 3390.
"
I found the same in the second crash file.

Not sure yet why a wrong device is used.
I think the crash files don't allow much more analysis at that time (at least not for me) and we may need to wait for the installer logs (from /var/log)...

Tags:

Revision history for this message

Frank Heimes (fheimes) wrote on 2021-09-23:

#1

crash_data.tgz Edit (160.1 KiB, application/x-tar)

tags:	added: focal
Changed in ubuntu-z-systems:
importance:	Undecided → High
assignee:	nobody → Canonical Foundations Team (canonical-foundations)

Revision history for this message

Frank Heimes (fheimes) wrote on 2021-09-23:

#2

/var/log from ext4 installation on 20.04 Edit (509.0 KiB, application/x-tar)

/var/log from ext4 installation on 20.04

Revision history for this message

Frank Heimes (fheimes) wrote on 2021-09-23 (last edit on 2021-09-23):

#3

screenshots Edit (114.9 KiB, application/zip)

Interestingly there are no DASDs attached to this DPM LPAR (as the attached screenshots show).
Wondering why fdasd is called ...
(this is more curtin related, hence adding curtin to the bug)

Revision history for this message

Frank Heimes (fheimes) wrote on 2021-09-24:

#4

output of 'probert --storage' Edit (117.5 KiB, text/plain)

output of 'probert --storage'

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2021-09-26:

#5

We try to call fdasd --table in a bunch of situations where it's not expected to work (on all architectures!), that's not what is causing the failure.

This is user error, they entered a URL to a an ISO in the mirror screen:

2021-09-23 14:51:40,822 DEBUG subiquity.client.controllers.mirror:43 MirrorController.done next_screen mirror=https://cdimage.ubuntu.com/releases/20.04/release/ubuntu-20.04.3-live-server-s390x.iso

We should think about the wording of the screen so users are less likely to do this and I've been meaning for a long time to do some checks of the value the user enters here.

Revision history for this message

Frank Heimes (fheimes) wrote on 2021-09-27 (last edit on 2021-09-27):

#6

Thx for identifying the root cause @mwhudson
(I fall for this 'speculative' execution too often, like with lsusb, too.)

+1 on adding some checks (to make this more robust against wrong entries)

Also, adjusting(correcting the bug title...

Frank Heimes (fheimes) on 2021-09-27

summary:

- Installation fails on s390x because fdasd is executed on "/dev/dm-0"
- rather than a DASD ECKD device
+ Installation fails on s390x due to unexpected input for Archive Mirror

Frank Heimes (fheimes) on 2022-09-13

Changed in ubuntu-z-systems:
importance:	High → Wishlist

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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