multipath / FCP installation fails on particular LPAR

Bug #1923487 reported by Frank Heimes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
High
Michael Hudson-Doyle
curtin
Fix Released
Undecided
Unassigned
subiquity
Fix Released
Undecided
Unassigned

Bug Description

While trying to install 21.04 using subiquity in a special LPAR with zFCP disk storage using multipath it fails with the following error/crash:

 Running command ['lvcreate', 'ubuntu-vg', '--name', 'ubuntu-lv', '--zero=y', '--wipesignatures=y', '--size', '33820770304.0B'] with allowed return codes [0] (capture=False)
   Rounding up size to full physical extent 31.50 GiB
 WARNING: ext4 signature detected on /dev/ubuntu-vg/ubuntu-lv at offset 1080. Wipe it? [y/n]: [n]
   Aborted wiping of ext4.
   1 existing signature left on the device.
   Failed to wipe signatures on logical volume ubuntu-vg/ubuntu-lv.
   Aborting. Failed to wipe start of new LV.
 An error occured handling 'lvm_partition-0': ProcessExecutionError - Unexpected error while running command.

Please see the attached file with full log and crash files.

Interestingly I see this issue only on one particular LPAR, but constantly and repeatadly.
On other systems (LPARs and even zVM guests) I didn't came across this issue so far.

Related branches

Revision history for this message
Frank Heimes (fheimes) wrote :
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Wait, curtin is already passing --wipesignatures=y. What is lvcreate doing?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Ah I think maybe we need to pass --yes as well, maybe?

Revision history for this message
Frank Heimes (fheimes) wrote :

The arguments seem to be a bit confusing.
Looks like it's
-W
or --wipesignatures y|n
(so without '=' ?!)
and
--yes
on top.

Here is a discussion on hat as well: https://bugzilla.redhat.com/show_bug.cgi?id=1305894

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Ah yes that bug seems to be complaining about exactly the same confusion.

Revision history for this message
Server Team CI bot (server-team-bot) wrote :

This bug is fixed with commit 87aa64bc to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=87aa64bc

Changed in curtin:
status: New → Fix Committed
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Fix Committed
Changed in subiquity:
status: New → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
Revision history for this message
Dan Bungert (dbungert) wrote : Fixed in curtin version 21.3.

This bug is believed to be fixed in curtin in version 21.3. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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