subiquity

curtin mishandles removing dm-multipath partition removal

Bug #1857042 reported by Frank Heimes on 2019-12-19

This bug affects 2 people

	Status	Importance	Assigned to
Ubuntu on IBM z Systems	Fix Released	Critical	Canonical Server
curtin	Fix Released	Undecided	Ryan Harper
subiquity	Fix Released	Undecided	Unassigned

Bug Description

With a closer look at the install we discovered that curtin
was attempting to clear a partition which was still controlled
by device-mapper; this prevents writes to the underlying partition.

Curtin will need to look up a partition by it's parent device,
discover the multipath-id of the parent, construct the correct
device-mapper DM_NAME value, and examine the output from
dmsetup ls to map the DM_NAME to the device-mapper device (dm-XX).

While working on this bug, we discovered a subiquity bug,
LP: #1860444

-- Original Description --
While trying Ubuntu focal ISO image with timestamp Dec 19 that includes subiquity 19.12.2+git6.b024f284 I run into problems with curtin on the disk handling:

2019-12-19 16:17:15,732 WARNING curtin:1242 Extract storage config does not validate.
2019-12-19 16:17:15,734 ERROR block-discover:115 block probing failed restricted=True
Traceback (most recent call last):
  File "/snap/subiquity/1413/lib/python3.6/site-packages/subiquity/controllers/filesystem.py", line 112, in _probe
    await asyncio.wait_for(self._probe_once_task.task, 5.0)
  File "/snap/subiquity/1413/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/snap/subiquity/1413/lib/python3.6/site-packages/subiquity/controllers/filesystem.py", line 99, in _probe_once
    self.model.load_probe_data(storage)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/subiquity/models/filesystem.py", line 1378, in load_probe_data
    self.reset()
  File "/snap/subiquity/1413/lib/python3.6/site-packages/subiquity/models/filesystem.py", line 1202, in reset
    config = storage_config.extract_storage_config(self._probe_data)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/storage_config.py", line 1257, in extract_storage_config
    tree = get_config_tree(cfg.get('id'), final_config)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/storage_config.py", line 274, in get_config_tree
    for dep in find_item_dependencies(item, sconfig):
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/storage_config.py", line 244, in find_item_dependencies
    _validate_dep_type(item_id, dep_key, dep, config)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/storage_config.py", line 192, in _validate_dep_type
    'Invalid dep_id (%s) not in storage config' % dep_id)
ValueError: Invalid dep_id (disk-sda) not in storage config
2019-12-19 16:17:15,741 INFO subiquity.core:193 saving crash report 'block probing crashed with ValueError' to /var/crash/1576772235.740345001.disk_probe_fail.crash

I did two installations that failed this way.
I've attached two sets of logs/crash files.

See original description

Tags:

Related branches

~raharper/curtin:ubuntu/xenial-sru-20200130

Merged into curtin:ubuntu/xenial at revision 1012247082abb716a515d668a923f0a6faffb6d9

Server Team CI bot: Needs Fixing (continuous-integration) on 2020-01-30

Dan Watkins (community): Approve on 2020-01-30

Diff: 16912 lines (+12842/-697)

95 files modified

HACKING.rst (+3/-4)
Makefile (+5/-1)
curtin/__init__.py (+1/-1)
curtin/block/__init__.py (+50/-6)
curtin/block/clear_holders.py (+88/-21)
curtin/block/deps.py (+1/-1)
curtin/block/multipath.py (+74/-2)
curtin/block/schemas.py (+8/-2)
curtin/block/zfs.py (+24/-0)
curtin/commands/block_meta.py (+138/-55)
curtin/commands/curthooks.py (+229/-53)
curtin/commands/install.py (+5/-1)
curtin/deps/__init__.py (+1/-1)
curtin/distro.py (+25/-2)
curtin/net/deps.py (+3/-3)
curtin/storage_config.py (+108/-22)
curtin/udev.py (+15/-7)
curtin/util.py (+23/-8)
debian/changelog (+81/-0)
debian/control (+1/-1)
doc/topics/config.rst (+6/-1)
doc/topics/integration-testing.rst (+13/-6)
doc/topics/storage.rst (+17/-2)
examples/tests/basic-dasd.yaml (+2/-2)
examples/tests/bcache-ceph-nvme-simple.yaml (+107/-0)
examples/tests/bcache-wipe-xfs.yaml (+4/-3)
examples/tests/bridging_network_v2.yaml (+38/-0)
examples/tests/dirty_disks_config.yaml (+9/-1)
examples/tests/network_mtu_networkd.yaml (+93/-0)
examples/tests/reuse-raid-member-partition.yaml (+73/-0)
examples/tests/reuse-raid-member-wipe.yaml (+71/-0)
helpers/common (+84/-13)
tests/data/probert_storage_multipath.json (+1059/-0)
tests/data/probert_storage_raid1_partitions.json (+951/-0)
tests/data/probert_storage_zlp6.json (+6980/-0)
tests/unittests/test_block.py (+59/-0)
tests/unittests/test_block_dasd.py (+1/-1)
tests/unittests/test_block_multipath.py (+87/-6)
tests/unittests/test_block_zfs.py (+26/-0)
tests/unittests/test_clear_holders.py (+131/-11)
tests/unittests/test_commands_block_meta.py (+550/-35)
tests/unittests/test_commands_collect_logs.py (+3/-1)
tests/unittests/test_curthooks.py (+338/-31)
tests/unittests/test_distro.py (+71/-0)
tests/unittests/test_storage_config.py (+152/-10)
tests/unittests/test_udev.py (+15/-14)
tests/unittests/test_util.py (+120/-1)
tests/vmtests/__init__.py (+244/-34)
tests/vmtests/helpers.py (+11/-6)
tests/vmtests/image_sync.py (+10/-3)
tests/vmtests/releases.py (+34/-0)
tests/vmtests/test_apt_config_cmd.py (+1/-8)
tests/vmtests/test_basic.py (+69/-89)
tests/vmtests/test_basic_dasd.py (+7/-16)
tests/vmtests/test_bcache_basic.py (+4/-3)
tests/vmtests/test_bcache_bug1718699.py (+4/-3)
tests/vmtests/test_bcache_ceph.py (+30/-3)
tests/vmtests/test_bcache_partitions.py (+4/-3)
tests/vmtests/test_fs_battery.py (+4/-3)
tests/vmtests/test_iscsi.py (+5/-3)
tests/vmtests/test_journald_reporter.py (+4/-7)
tests/vmtests/test_lvm.py (+14/-21)
tests/vmtests/test_lvm_iscsi.py (+4/-3)
tests/vmtests/test_lvm_raid.py (+3/-3)
tests/vmtests/test_lvm_root.py (+16/-1)
tests/vmtests/test_mdadm_bcache.py (+86/-40)
tests/vmtests/test_mdadm_iscsi.py (+4/-3)
tests/vmtests/test_multipath.py (+5/-5)
tests/vmtests/test_network.py (+3/-3)
tests/vmtests/test_network_alias.py (+4/-3)
tests/vmtests/test_network_bonding.py (+3/-3)
tests/vmtests/test_network_bridging.py (+22/-3)
tests/vmtests/test_network_ipv6.py (+0/-4)
tests/vmtests/test_network_ipv6_static.py (+3/-3)
tests/vmtests/test_network_ipv6_vlan.py (+7/-3)
tests/vmtests/test_network_mtu.py (+41/-13)
tests/vmtests/test_network_static.py (+3/-3)
tests/vmtests/test_network_static_routes.py (+5/-5)
tests/vmtests/test_network_vlan.py (+11/-3)
tests/vmtests/test_nvme.py (+4/-7)
tests/vmtests/test_old_apt_features.py (+3/-2)
tests/vmtests/test_pollinate_useragent.py (+4/-3)
tests/vmtests/test_preserve.py (+4/-3)
tests/vmtests/test_preserve_raid.py (+4/-3)
tests/vmtests/test_raid5_bcache.py (+4/-3)
tests/vmtests/test_reuse_raid_member.py (+63/-0)
tests/vmtests/test_simple.py (+10/-10)
tests/vmtests/test_uefi_basic.py (+8/-7)
tests/vmtests/test_zfsroot.py (+20/-8)
tools/block-discover-to-config (+3/-1)
tools/jenkins-runner (+50/-0)
tools/launch (+10/-0)
tools/vmtest-filter (+12/-1)
tools/vmtest-sync-images (+15/-13)
tools/xkvm (+20/-4)

~raharper/curtin:ubuntu/bionic-sru-20200130

Merged into curtin:ubuntu/bionic at revision e95a4cfda532aa89782ef25d246cef5f023b0e08

Server Team CI bot: Needs Fixing (continuous-integration) on 2020-01-30

Dan Watkins (community): Approve on 2020-01-30

Diff: 16912 lines (+12842/-697)

95 files modified

~raharper/curtin:ubuntu/eoan-sru-20200130

Merged into curtin:ubuntu/eoan at revision 1c2b677876854b6639ae0ff8bdb6eebdf01f35e9

Server Team CI bot: Needs Fixing (continuous-integration) on 2020-01-30

Dan Watkins (community): Approve on 2020-01-30

Diff: 15603 lines (+12330/-488)

87 files modified

HACKING.rst (+3/-4)
curtin/__init__.py (+1/-1)
curtin/block/clear_holders.py (+88/-21)
curtin/block/multipath.py (+74/-2)
curtin/block/schemas.py (+7/-1)
curtin/block/zfs.py (+24/-0)
curtin/commands/block_meta.py (+99/-46)
curtin/commands/curthooks.py (+200/-53)
curtin/commands/install.py (+5/-1)
curtin/distro.py (+25/-2)
curtin/net/deps.py (+3/-3)
curtin/storage_config.py (+105/-20)
curtin/udev.py (+15/-7)
curtin/util.py (+12/-5)
debian/changelog (+63/-0)
debian/control (+1/-1)
doc/topics/config.rst (+6/-1)
doc/topics/storage.rst (+17/-2)
examples/tests/basic-dasd.yaml (+2/-2)
examples/tests/bcache-ceph-nvme-simple.yaml (+107/-0)
examples/tests/bcache-wipe-xfs.yaml (+4/-3)
examples/tests/bridging_network_v2.yaml (+38/-0)
examples/tests/dirty_disks_config.yaml (+9/-1)
examples/tests/network_mtu_networkd.yaml (+93/-0)
examples/tests/reuse-raid-member-partition.yaml (+73/-0)
examples/tests/reuse-raid-member-wipe.yaml (+71/-0)
helpers/common (+84/-13)
tests/data/probert_storage_multipath.json (+1059/-0)
tests/data/probert_storage_raid1_partitions.json (+951/-0)
tests/data/probert_storage_zlp6.json (+6980/-0)
tests/unittests/test_block.py (+26/-0)
tests/unittests/test_block_dasd.py (+1/-1)
tests/unittests/test_block_multipath.py (+87/-6)
tests/unittests/test_block_zfs.py (+26/-0)
tests/unittests/test_clear_holders.py (+131/-11)
tests/unittests/test_commands_block_meta.py (+377/-36)
tests/unittests/test_commands_collect_logs.py (+3/-1)
tests/unittests/test_curthooks.py (+311/-26)
tests/unittests/test_distro.py (+71/-0)
tests/unittests/test_storage_config.py (+114/-9)
tests/unittests/test_udev.py (+15/-14)
tests/unittests/test_util.py (+41/-1)
tests/vmtests/__init__.py (+231/-23)
tests/vmtests/helpers.py (+11/-6)
tests/vmtests/releases.py (+34/-0)
tests/vmtests/test_apt_config_cmd.py (+1/-4)
tests/vmtests/test_basic.py (+71/-81)
tests/vmtests/test_basic_dasd.py (+8/-10)
tests/vmtests/test_bcache_basic.py (+5/-0)
tests/vmtests/test_bcache_bug1718699.py (+5/-0)
tests/vmtests/test_bcache_ceph.py (+31/-0)
tests/vmtests/test_bcache_partitions.py (+5/-0)
tests/vmtests/test_fs_battery.py (+5/-0)
tests/vmtests/test_iscsi.py (+6/-0)
tests/vmtests/test_journald_reporter.py (+5/-4)
tests/vmtests/test_lvm.py (+15/-18)
tests/vmtests/test_lvm_iscsi.py (+5/-0)
tests/vmtests/test_lvm_raid.py (+4/-0)
tests/vmtests/test_lvm_root.py (+16/-1)
tests/vmtests/test_mdadm_bcache.py (+92/-12)
tests/vmtests/test_mdadm_iscsi.py (+5/-0)
tests/vmtests/test_multipath.py (+6/-0)
tests/vmtests/test_network.py (+4/-0)
tests/vmtests/test_network_alias.py (+5/-0)
tests/vmtests/test_network_bonding.py (+4/-0)
tests/vmtests/test_network_bridging.py (+23/-0)
tests/vmtests/test_network_ipv6_static.py (+4/-0)
tests/vmtests/test_network_ipv6_vlan.py (+8/-0)
tests/vmtests/test_network_mtu.py (+42/-10)
tests/vmtests/test_network_static.py (+4/-0)
tests/vmtests/test_network_static_routes.py (+5/-0)
tests/vmtests/test_network_vlan.py (+12/-0)
tests/vmtests/test_nvme.py (+5/-0)
tests/vmtests/test_old_apt_features.py (+3/-2)
tests/vmtests/test_pollinate_useragent.py (+5/-0)
tests/vmtests/test_preserve.py (+5/-0)
tests/vmtests/test_preserve_raid.py (+5/-0)
tests/vmtests/test_raid5_bcache.py (+5/-0)
tests/vmtests/test_reuse_raid_member.py (+63/-0)
tests/vmtests/test_simple.py (+16/-1)
tests/vmtests/test_uefi_basic.py (+11/-1)
tests/vmtests/test_zfsroot.py (+18/-2)
tools/block-discover-to-config (+3/-1)
tools/jenkins-runner (+50/-0)
tools/vmtest-filter (+12/-1)
tools/vmtest-sync-images (+15/-13)
tools/xkvm (+20/-4)

~raharper/curtin:fix/mpath-partition-wiping

Merged into curtin:master

Dan Watkins (community): Approve on 2020-01-24

Server Team CI bot: Approve (continuous-integration) on 2020-01-24

Revision history for this message

Frank Heimes (fheimes) wrote on 2019-12-19:

logs_crash.tar.gz Edit (3.5 MiB, application/x-tar)

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

Frank Heimes (fheimes) on 2019-12-19

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

Revision history for this message

Dan Watkins (oddbloke) wrote on 2020-01-07:

I think the underlying issue here is that curtin failed during block-meta due to /dev/sda1 being busy:

finish: cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL: removing previous storage devices
TIMED BLOCK_META: 10.963
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command block-meta
Traceback (most recent call last):
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/commands/main.py", line 202, in main
    ret = args.func(args)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/log.py", line 97, in wrapper
    return log_time("TIMED %s: " % msg, func, *args, **kwargs)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/log.py", line 79, in log_time
    return func(*args, **kwargs)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/commands/block_meta.py", line 79, in block_meta
    meta_clear(devices, state.get('report_stack_prefix', ''))
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/commands/block_meta.py", line 1662, in meta_clear
    clear_holders.clear_holders(devices)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/clear_holders.py", line 624, in clear_holders
    shutdown_function(dev_info['device'])
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/clear_holders.py", line 288, in wipe_superblock
    _wipe_superblock(blockdev)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/clear_holders.py", line 333, in _wipe_superblock
    exclusive=exclusive, strict=strict)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/__init__.py", line 1127, in wipe_volume
    quick_zero(path, partitions=False, exclusive=exclusive, strict=strict)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/__init__.py", line 1041, in quick_zero
    exclusive=exclusive, strict=strict)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/__init__.py", line 1061, in zero_file_at_offsets
    with exclusive_open(path, exclusive=exclusive) as fp:
  File "/snap/subiquity/1413/usr/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/snap/subiquity/1413/lib/python3.6/site-packages/curtin/block/__init__.py", line 954, in exclusive_open
    fd = os.open(path, flags)
OSError: [Errno 16] Device or resource busy: '/dev/sda1'
[Errno 16] Device or resource busy: '/dev/sda1'

And I think that curtin thinks that /dev/sda1 shouldn't be busy because fuser returns non-zero and so doesn't report any users:

wiping /dev/sda1 attempt 4/4
wiping 1M on /dev/sda1 at offsets [0, -1048576]
Failed to exclusively open path: /dev/sda1
devname '/dev/sda1' had holders: []
Device holders with exclusive access: []
Device mounts: []
Running command ['fuser', '--verbose', '--mount', '/dev/sda1'] with allowed return codes [0] (capture=True)
fuser returned non-zero: ''
Possible users of /dev/sda1:
None

Playing around locally, fuser emits its error messages on stderr, so perhaps we're not capturing stderr here to get the full error message? I'm unsure.

I think the underlying issue here is that curtin failed during block-meta due to /dev/sda1 being busy:

And I think that curtin thinks that /dev/sda1 shouldn't be busy because fuser returns non-zero and so doesn't report any users:

Playing around locally, fuser emits its error messages on stderr, so perhaps we're not capturing stderr here to get the full error message?  I'm unsure.

Revision history for this message

Ryan Harper (raharper) wrote on 2020-01-09:

@Frank

Can you provide any more details about the storage setup at the start and what steps you were taking in subiquity? At some point /dev/sda becomes unaccesible and then things fall apart so it would be good to understand what's happening on the system before the failure.

Changed in curtin:
status:	New → Incomplete

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-01-09:

Download full text (3.2 KiB)

@ Ryan, sure.
So the disk setup that I use is actually the simplest that's possible (as of today).
It's 'normal' multipath (two HBAs) zFCP/SCSI setup with a 64GB LUN that results in a mpatha at the end.

root@ubuntu-server:/# dmsetup ls --tree -o nodevice
mpatha-part1
mpatha
root@ubuntu-server:/#

Device Start End Sectors Size Type
/dev/mapper/mpatha-part1 2048 134215679 134213632 64G Linux filesystem
root@ubuntu-server:/#

I wondering about the gpt disk label type, since on a alternate 18.04.3 LPAR installation it's dos:
$ sudo fdisk -l /dev/mapper/mpatha
Disk /dev/mapper/mpatha: 64 GiB, 68719476736 bytes, 134217728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x097ab3e7

Device Boot Start End Sectors Size Id Type
/dev/mapper/mpatha-part1 2048 134217727 134215680 64G 83 Linux

Well, the above output might be a bit outdated (and is maybe from an older version), I'll today redo an installation based o...

root@ubuntu-server:/# multipath -l                                              
mpatha (36005076306ffd6b60000000000002602) dm-0 IBM,2107900                     
size=64G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw                 
`-+- policy='service-time 0' prio=0 status=active                               
  |- 0:0:0:1073889318 sda 8:0  active undef running                             
  |- 0:0:1:1073889318 sdb 8:16 active undef running                             
  |- 1:0:0:1073889318 sdc 8:32 active undef running                             
  `- 1:0:1:1073889318 sdd 8:48 active undef running                             
root@ubuntu-server:/#

root@ubuntu-server:/# multipath -ll                                             
mpatha (36005076306ffd6b60000000000002602) dm-0 IBM,2107900                     
size=64G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw                 
`-+- policy='service-time 0' prio=50 status=active                              
  |- 0:0:0:1073889318 sda 8:0  active ready running                             
  |- 0:0:1:1073889318 sdb 8:16 active ready running                             
  |- 1:0:0:1073889318 sdc 8:32 active ready running                             
  `- 1:0:1:1073889318 sdd 8:48 active ready running                             
root@ubuntu-server:/#

root@ubuntu-server:/# dmsetup ls --tree -o nodevice
mpatha-part1
       mpatha
root@ubuntu-server:/#

root@ubuntu-server:/# fdisk -l /dev/mapper/mpatha                               
Disk /dev/mapper/mpatha: 64 GiB, 68719476736 bytes, 134217728 sectors           
Units: sectors of 1 * 512 = 512 bytes                                           
Sector size (logical/physical): 512 bytes / 512 bytes                           
I/O size (minimum/optimal): 512 bytes / 512 bytes                               
Disklabel type: gpt                                                             
Disk identifier: 3334481D-1BA4-4C8E-B7DD-4B4A1652DF73                           
                                                                                
Device                   Start       End   Sectors Size Type                    
/dev/mapper/mpatha-part1  2048 134215679 134213632  64G Linux filesystem        
root@ubuntu-server:/#

Device                   Boot Start       End   Sectors Size Id Type
/dev/mapper/mpatha-part1       2048 134217727 134215680  64G 83 Linux

Well, the above output might be a bit outdated (and is maybe from an older version), I'll today redo an installation based on the very latest image and will capture the subiquity UI config screens as well as more details from the installer shell...

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-01-09:

subiquity test - focal live 09012020.txt Edit (206.5 KiB, text/plain)

Retried again with latest image (from today, time stamp Jan 8th) and have now more (current) details.
Please see attached (txt) for the steps in the installer, as well as the error log and curtin config snippets, and the entire /var/log in in the tgz.
Looks like the partition is gone ?! at some point in time ...

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-01-09:

09012020.tgz Edit (1.6 MiB, application/x-tar)

Chad Smith (chad.smith) on 2020-01-10

Changed in curtin:
status:	Incomplete → New

Frank Heimes (fheimes) on 2020-01-15

Changed in ubuntu-z-systems:
assignee:	nobody → Canonical Server Team (canonical-server)

Frank Heimes (fheimes) on 2020-01-22

Changed in ubuntu-z-systems:
status:	New → In Progress
Changed in curtin:
status:	New → In Progress

Ryan Harper (raharper) on 2020-01-22

summary:	- subiquity on s390x fails with curtin: block-discover probing + curtin mishandles removing dm-multipath partition removal
description:	updated

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-01-23:

23012020.tgz Edit (2.3 MiB, application/x-tar)

So after trying with "subiquity-channel=latest/edge/case" and refreshing,
I guess we hand at a slightly different step (but nearby).
/var/log and /var/crash is attached

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-01-24:

The last comment (#7) shows that the issue discussed here in this particular bug is fixed, using latest/edge/case.
For a new issue (failing to clean disk / timeout) I think it's best that I open a separate ticket,
it's now in LP 1860778.

Dan Watkins (oddbloke) on 2020-01-27

Changed in curtin:
assignee:	nobody → Ryan Harper (raharper)

Revision history for this message

Server Team CI bot (server-team-bot) wrote on 2020-01-27:

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

Changed in curtin:
status:	In Progress → Fix Committed

Frank Heimes (fheimes) on 2020-01-27

Changed in ubuntu-z-systems:
status:	In Progress → Fix Committed

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-01-30:

#10

That seems to be fine now with 19.12.2+git47.e510f574 from latest/edge/case.

Revision history for this message

Frank Heimes (fheimes) wrote on 2020-03-26:

#11

I can confirm that it is fixed with subiquity 20.03.
I installed focal on an zfcp multipath system where before a LUKS installation was running.
While selecting 'whole disk' the installer was able to wipe out the old scheme and replaced it by an all-in-on part setup.

Changed in ubuntu-z-systems:
status:	Fix Committed → Fix Released

Revision history for this message

Joshua Powers (powersj) wrote on 2020-04-01:

#12

Marking other tasks fix released so this doesn't show up in the report.

Changed in subiquity:
status:	New → Fix Released
Changed in curtin:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1855127

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.