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

Bug #1952226 reported by Diego Mascialino
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Fix Committed
Undecided
Unassigned

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
TIMED BLOCK_META: 1.260
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
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
Revision history for this message
Patricia Domingues (patriciasd) wrote :

I was checking this on a 2.9.2 MAAS and I can reproduce this issue on a ppc64le (POWER9) server trying to install 22.04. Attaching the curtin log

Revision history for this message
Patricia Domingues (patriciasd) wrote :

I can now install and boot 22.04 on the same Power9 server - installing curtin 21.3 from ppa:curtin-dev/daily:

`2021-12-14T15:58:23+00:00 tiselius cloud-init[3091]: curtin: Installation started. (21.3-972-g9ea6be15-0ubuntu1+307~trunk~ubuntu20.04.1)`

```
ii curtin-common 21.3-972-g9ea6be15-0ubuntu1+307~trunk~ubuntu20.04.1 all Library and tools for curtin installer
ii python3-curtin 21.3-972-g9ea6be15-0ubuntu1+307~trunk~ubuntu20.04.1 all Library and tools for curtin installer
```

`Welcome to Ubuntu Jammy Jellyfish (development branch) (GNU/Linux 5.13.0-19-generic ppc64le)`

let me know if I can provide any other test/info

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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