Traceback deploying Jammy with MAAS 3.1

Doing some testing of Jammy via MAAS. I've added the 22.04 images via the Candidate stream and just attempted several deployments on multiple machines, all fail with the same traceback:

finish: cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL: removing previous storage devices
TIMED BLOCK_META: 5.411
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command block-meta
Traceback (most recent call last):
  File "/curtin/curtin/commands/main.py", line 202, in main
    ret = args.func(args)
  File "/curtin/curtin/log.py", line 97, in wrapper
    return log_time("TIMED %s: " % msg, func, *args, **kwargs)
  File "/curtin/curtin/log.py", line 79, in log_time
    return func(*args, **kwargs)
  File "/curtin/curtin/commands/block_meta.py", line 102, in block_meta
    meta_clear(devices, state.get('report_stack_prefix', ''))
  File "/curtin/curtin/commands/block_meta.py", line 1889, in meta_clear
    clear_holders.clear_holders(devices)
  File "/curtin/curtin/block/clear_holders.py", line 639, in clear_holders
    shutdown_function(dev_info['device'])
  File "/curtin/curtin/block/clear_holders.py", line 244, in wipe_superblock
    if block.is_extended_partition(blockdev):
  File "/curtin/curtin/block/__init__.py", line 1084, in is_extended_partition
    return (get_part_table_type(parent_dev) in ['dos', 'msdos'] and
  File "/curtin/curtin/block/__init__.py", line 1026, in get_part_table_type
    return ('gpt' if check_efi_signature(device) else
  File "/curtin/curtin/block/__init__.py", line 1058, in check_efi_signature
    sector_size = get_blockdev_sector_size(devname)[0]
  File "/curtin/curtin/block/__init__.py", line 785, in get_blockdev_sector_size
    logical = info[parent]['LOG-SEC']
KeyError: 'LOG-SEC'
'LOG-SEC'
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3

I've attached the logs from one of the failed deployments.

I know that there were some curtin issues earlier that affected Jammy deployments, but was told that MAAS 3.1 should have addressed these, so I don't know if this is a new issue or still the same issue.

We're using the MAAS 3.1.0 snap.

As a side note, I really, REALLY appreciate being able to simply download the tarball of deployment logs from the MAAS UI. Bravo!