curtin-dev team mailing list archive

[Ryan Harper <1895922@xxxxxxxxxxxxxxxxxx>]

I believe this is a duplicate of:  https://bugs.launchpad.net/curtin/+bug/1876258 
This has already been fixed in curtin, you can test with curtin's daily PPA, or curtin in groovy.

W.r.t uvtool;  like MAAS, uvtool should generate serial disk attributes
for all virtio disks by default.


** Changed in: curtin
       Status: New => Invalid

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

Title:
  maas could not deploy a kvm-based vm via virsh

Status in curtin:
  Invalid
Status in uvtool:
  Incomplete
Status in curtin package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New

Bug description:
  Curtin process failed during MaaS deployment. The infrastructure
  worked well until ~3 weeks ago.

  [Steps to Reproduce]
  1. Enlist and commission a KVM-based VM in MaaS 2.8.2 (8577-g.a3e674063)
  2. Deploy the VM node

  - Reproducing environment: nodes named after "scalebot-dev-controller" prefix in tremont lab maas.
  - Those vm were created (via virsh command), enlisted (via maas web UI), and commissioned (via maas web UI) manually. They are not created via MaaS pod controlling flow.

  [Expected Result]
  1. The VM is deployed

  [Actual Result]
  Curtin failed during the deployment

  Here is the error message:

          Generating grub debconf_selections for devices=['/dev/vda'] uefi=False
          finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL: installing grub to target devices
          finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL: configuring target system bootloader
          finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command curthooks
          Traceback (most recent call last):
            File "/curtin/curtin/commands/main.py", line 202, in main
              ret = args.func(args)
            File "/curtin/curtin/commands/curthooks.py", line 1770, in curthooks
              builtin_curthooks(cfg, target, state)
            File "/curtin/curtin/commands/curthooks.py", line 1736, in builtin_curthooks
              setup_grub(cfg, target, osfamily=osfamily)
            File "/curtin/curtin/commands/curthooks.py", line 689, in setup_grub
              configure_grub_debconf(instdevs, target, uefi_bootable)
            File "/curtin/curtin/commands/curthooks.py", line 509, in configure_grub_debconf
              link = block.disk_to_byid_path(dev)
            File "/curtin/curtin/block/__init__.py", line 869, in disk_to_byid_path
              mapping = get_dev_disk_byid()
            File "/curtin/curtin/block/__init__.py", line 861, in get_dev_disk_byid
              return _get_dev_disk_by_prefix('/dev/disk/by-id')
            File "/curtin/curtin/block/__init__.py", line 846, in _get_dev_disk_by_prefix
              for path in os.listdir(prefix)]
          FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-id'
          [Errno 2] No such file or directory: '/dev/disk/by-id'

  VM kernel: Linux scalebot-dev-controller5 4.15.0-117-generic
  #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64
  GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: curtin (not installed)
  ProcVersionSignature: User Name 4.15.0-117.118-generic 4.15.18
  Uname: Linux 4.15.0-117-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  Date: Thu Sep 17 04:38:32 2020
  SourcePackage: curtin
  UpgradeStatus: No upgrade log present (probably fresh install)

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