"Unexpected error while running command." when deploying jammy images with MAAS

Bug #1952226 reported by Diego Mascialino
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I am testing the deploy of 22.04 images using MAAS.

Curtin failed during the my first deploy.
Please find attached curtin-logs.tar

Let me know how can I help to debug it.

Related branches

Revision history for this message
Diego Mascialino (dmascialino) wrote :
Revision history for this message
Sean Feole (sfeole) wrote :
Download full text (14.5 KiB)

I have also just experienced this failure today while refreshing maas-images to include the latest uploaded jammy release.

See attached curtin.txt for full log

finish: cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL: removing previous storage devices
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
  File "/curtin/curtin/block/clear_holders.py", line 639, in clear_holders
  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'
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: start: cmd-install/stage-partitioning/builtin/cmd-block-meta: curtin command block-meta
        get_path_to_storage_volume for volume nvme0n1({'grub_device': True, 'id': 'nvme0n1', 'model': 'INTEL SSDPE2KX010T8', 'name': 'nvme0n1', 'ptable': 'gpt', 'serial': 'PHLJ0023005Y1P0FGN', 'type': 'disk', 'wipe': 'superblock'})
        Processing serial PHLJ0023005Y1P0FGN via udev to PHLJ0023005Y1P0FGN
        lookup_disks found: ['nvme-INTEL_SSDPE2KX010T8_PHLJ0023005Y1P0FGN', 'nvme-INTEL_SSDPE2KX010T8_PHLJ0023005Y1P0FGN-part1', 'nvme-INTEL_SSDPE2KX010T8_PHLJ0023005Y1P0FGN-part2']
        Running command ['udevadm', 'info', '--query=property', '--export', '/dev/nvme0n1'] with allowed return codes [0] (capture=True)
        /dev/nvme0n1 is multipath device? False
        Running command ['multipath', '-c', '/dev/nvme0n1'] with allowed return codes [0] (capture=True)
        /dev/nvme0n1 is multipath device member? False
        block.lookup_disk() returning path /dev/nvme0n1
        Running command ['partprobe', '/dev/nvme0n1'] with allowed return codes [0, 1] (capture=False)
        Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
        TIMED udevadm_settle(): 0.092
        devsync happy - path /dev/nvme0n1 now exists

Changed in curtin:
status: New → Confirmed
Revision history for this message
Dan Bungert (dbungert) wrote :
Changed in curtin:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers