I was googling for a MAAS deployment failure I'm seeing and this bug came up. Here's the traceback I'm seeing (full output attached):
get_blockdev_sector_size: (log=512, phys=512) Running command ['lsblk', '--noheadings', '--bytes', '--pairs', '--output=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-SIZE,SIZE,STATE,TYPE,UUID'] with allowed return codes [0] (capture=True) Checking if /dev/sdd2 is a swap device Found swap magic: b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' wiping superblock on /dev/sdd2 wiping /dev/sdd2 attempt 1/4 wiping 1M on /dev/sdd2 at offsets [0, -1048576] finish: cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL: removing previous storage devices TIMED BLOCK_META: 5.247 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 1870, in meta_clear clear_holders.clear_holders(devices) File "/curtin/curtin/block/clear_holders.py", line 633, in clear_holders shutdown_function(dev_info['device']) File "/curtin/curtin/block/clear_holders.py", line 305, in wipe_superblock _wipe_superblock(blockdev) File "/curtin/curtin/block/clear_holders.py", line 339, in _wipe_superblock exclusive=exclusive, strict=strict) File "/curtin/curtin/block/__init__.py", line 1316, in wipe_volume quick_zero(path, partitions=False, exclusive=exclusive, strict=strict) File "/curtin/curtin/block/__init__.py", line 1230, in quick_zero exclusive=exclusive, strict=strict) File "/curtin/curtin/block/__init__.py", line 1273, in zero_file_at_offsets raise ValueError(m_short.format(**msg_vals)) ValueError: /dev/sdd2 (size=524288): 1048576 bytes from 0 > size. /dev/sdd2 (size=524288): 1048576 bytes from 0 > size.
I was googling for a MAAS deployment failure I'm seeing and this bug came up. Here's the traceback I'm seeing (full output attached):
Running command ['lsblk', '--noheadings', '--bytes', '--pairs', '--output=
Checking if /dev/sdd2 is a swap device
Found swap magic: b'\x00\
wiping superblock on /dev/sdd2
wiping /dev/sdd2 attempt 1/4
wiping 1M on /dev/sdd2 at offsets [0, -1048576]
finish: cmd-install/
TIMED BLOCK_META: 5.247
finish: cmd-install/
Traceback (most recent call last):
File "/curtin/
ret = args.func(args)
File "/curtin/
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File "/curtin/
return func(*args, **kwargs)
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
raise ValueError(
ValueError: /dev/sdd2 (size=524288): 1048576 bytes from 0 > size.
/dev/sdd2 (size=524288): 1048576 bytes from 0 > size.