curtin-dev team mailing list archive

[Launchpad Bug Tracker <1885774@xxxxxxxxxxxxxxxxxx>]

[Expired for curtin because there has been no activity for 60 days.]

** Changed in: curtin
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of curtin
developers, which is subscribed to curtin.
https://bugs.launchpad.net/bugs/1885774

Title:
  Need curtin support for custom Ubuntu dd(t)gz images in MAAS

Status in curtin:
  Expired

Bug description:
  Customer requires custom Ubuntu images to be deployed in MAAS, prefers
  to provide them aas ddgz or ddtgz format.

  Since they are uploaded to MAAS as "custom", Curtin does not seem to
  understand it's deploying Ubuntu.

  If we set the boot device to be disk after the deployment failure in
  MAAS, the image boots.

  Full logs have customer information, which I can't post publicly. But
  the following is the point where the MAAS deployment fails.

         2020-06-30 18:18:30 (4.56 MB/s) - written to stdout
  [6191907410/6191907410]                0+8519680 records in
  0+8519680 records out        279172874240 bytes (279 GB, 260 GiB)
  copied, 1323.64 s, 211 MB/s        Running command ['partprobe',
  '/dev/nvme0n1'] with allowed return codes [0] (capture=False)
  Warning: Not all of the space available to /dev/nvme0n1 appears to be
  used, you can fix the GPT to use all of the space (an extra 7268777648
  blocks) or continue with the current setting?         Running command
  ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
  TIMED udevadm_settle(): 0.076        Searching for filesystem on
  ['nvme0n1'] containing one of: ['curtin', 'system-data/var/lib/snapd']
  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', '/dev/nvme0n1'] with allowed return codes
  [0] (capture=True)        Running command ['mount', '/dev/nvme0n1p2',
  '/tmp/tmpwuonqqca'] with allowed return codes [0] (capture=False)
  Running command ['umount', '/tmp/tmpwuonqqca'] with allowed return
  codes [0] (capture=False)        Running command ['mount',
  '/dev/nvme0n1p1', '/tmp/tmpwuonqqca'] with allowed return codes [0]
  (capture=False)        Running command ['umount', '/tmp/tmpwuonqqca']
  with allowed return codes [0] (capture=False)        TIMED BLOCK_META:
  1325.647        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 84, in block_meta
  return meta_simple(args)          File
  "/curtin/curtin/commands/block_meta.py", line 1886, in meta_simple
  rootdev = write_image_to_disk(dd_images[0], devname)          File
  "/curtin/curtin/commands/block_meta.py", line 127, in
  write_image_to_disk            return block.get_root_device([devname],
  paths=paths)          File "/curtin/curtin/block/__init__.py", line
  587, in get_root_device            (dev, paths))        ValueError:
  Did not find any filesystem on ['nvme0n1'] that contained one of
  ['curtin', 'system-data/var/lib/snapd']        Did not find any
  filesystem on ['nvme0n1'] that contained one of ['curtin', 'system-
  data/var/lib/snapd']

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1885774/+subscriptions