Packer QEMU Ubuntu 20.04 UEFI kernel install failed

Bug #2018621 reported by Christopher Morales
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Using the following autoinstall configuration fails when trying to install the kernel and configuring the system. The partitions are getting created and grub is getting configured properly. I looked at the subiquity-server-debug logs and the error is

`subiquity/Install/Install/curtin_install/cmd-install/cmd-install/stage-curthoks/builtin/cmd-curthooks/installing-kernel: FAIL: installing kernel`

user-data:

#cloud-config
autoinstall:
  version: 1
  locale: en_US
  keyboard:
    layout: us
  timezone: UTC
  user-data:
    disable_root: false
  users:
    - name: ec2-user
      homedir: /home/ec2-user
      shell: /bin/bash
      sudo: ALL=(ALL) NOPASSWD:ALL
      lock-passwd: false
      password: <password>
      groups: users, admin
  identity:
    hostname: ubuntu
    username: ec2-user
    password: <password>
  ssh:
    install-server: yes
    allow-pw: yes
  early-commands:
    - sudo systemctl stop ssh
    - sed -ie 's/eject -p/#eject -p/' /sbin/casper-stop
    - touch /run/casper-no-prompt
  packages:
    - qemu-guest-agent
  storage:
    grub:
      reorder_uefi: false
    config:
    - {ptable: gpt, grub_device: true, id: disk-sda, path: /dev/sda, type: disk, wipe: superblock-recursive, match: { "size": "largest" }}
    - {device: disk-sda, id: partition-1, number: 1, flag: bios_grub, size: 1MB, type: partition}
    - {device: disk-sda, id: partition-2, number: 2, wipe: superblock, flag: boot, preserve: false, grub_device: false, type: partition, size: 1000MB}
    - {fstype: vfat, volume: partition-2, preserve: false, type: format, id: format-11}
    # /boot/efi
    - {device: disk-sda, id: partition-3, number: 3, flag: bios_grub, preserve: false, grub_device: true, type: partition, size: 512MB}
    - {fstype: vfat, volume: partition-3, preserve: false, type: format, id: format-12}
    # Main Disk
    - {device: disk-sda, id: partition-4, number: 4, wipe: superblock, size: -1, flag: '', preserve: false, grub_device: false, type: partition}
    # LVM Group
    - {name: ubuntu-vg, devices: [partition-4], preserve: false, type: lvm_volgroup, id: lvm_volgroup-3}
    - {name: root, volgroup: lvm_volgroup-3, size: 35%, preserve: false, type: lvm_partition, id: lvm_partition-9}
    - {name: swap, volgroup: lvm_volgroup-3, size: 5%, preserve: false, type: lvm_partition, id: lvm_partition-10}
    # /
    - {fstype: xfs, volume: lvm_partition-9, preserve: false, type: format, id: format-10}
    # swap
    - {fstype: swap, volume: lvm_partition-10, preserve: false, type: format, id: format-13}
    - {device: format-13, path: '', type: mount, id: mount-13}
    # /tmp
    - {name: tmp, volgroup: lvm_volgroup-3, size: 10%, preserve: false, type: lvm_partition, id: lvm_partition-11}
    - {fstype: xfs, volume: lvm_partition-11, preserve: false, type: format, id: format-14}
    # /var
    - {name: var, volgroup: lvm_volgroup-3, size: 10%, preserve: false, type: lvm_partition, id: lvm_partition-12}
    - {fstype: xfs, volume: lvm_partition-12, preserve: false, type: format, id: format-15}
    # /var/tmp
    - {name: var_tmp, volgroup: lvm_volgroup-3, size: 5%, preserve: false, type: lvm_partition, id: lvm_partition-13}
    - {fstype: xfs, volume: lvm_partition-13, preserve: false, type: format, id: format-16}
    # /var/log
    - {name: log, volgroup: lvm_volgroup-3, size: 10%, preserve: false, type: lvm_partition, id: lvm_partition-14}
    - {fstype: xfs, volume: lvm_partition-14, preserve: false, type: format, id: format-17}
    # /var/log/audit
    - {name: audit, volgroup: lvm_volgroup-3, size: 10%, preserve: false, type: lvm_partition, id: lvm_partition-15}
    - {fstype: xfs, volume: lvm_partition-15, preserve: false, type: format, id: format-18}
    # /home
    - {name: home, volgroup: lvm_volgroup-3, size: 10%, preserve: false, type: lvm_partition, id: lvm_partition-16}
    - {fstype: xfs, volume: lvm_partition-16, preserve: false, type: format, id: format-19}

    - {device: format-10, path: /, type: mount, id: mount-21}
    - {device: format-11, path: /boot, type: mount, id: mount-11}
    - {device: format-12, path: /boot/efi, type: mount, id: mount-12}
    - {device: format-19, path: /home, type: mount, id: mount-19, options: 'nodev'}
    - {device: format-14, path: /tmp, type: mount, id: mount-14, options: 'nodev,nosuid,noexec'}
    - {device: format-15, path: /var, type: mount, id: mount-15}
    - {device: format-16, path: /var/tmp, type: mount, id: mount-16, options: 'nodev,nosuid,noexec'}
    - {device: format-17, path: /var/log, type: mount, id: mount-17}
    - {device: format-18, path: /var/log/audit, type: mount, id: mount-18}

description: updated
description: updated
summary: - Packer QEMU Ubuntu 20.04 kernel install failed
+ Packer QEMU Ubuntu 20.04 UEFI kernel install failed
Revision history for this message
Dan Bungert (dbungert) wrote :

Hi Christopher, thanks for the report.

    - {fstype: vfat, volume: partition-2, preserve: false, type: format, id: format-11}
    - {device: format-11, path: /boot, type: mount, id: mount-11}
I ran some tests on this autoinstall and believe this is the problem. Make /boot a different fstype, ext4 perhaps.

    - {device: disk-sda, id: partition-3, number: 3, flag: bios_grub, preserve: false, grub_device: true, type: partition, size: 512MB}
    - {fstype: vfat, volume: partition-3, preserve: false, type: format, id: format-12}
    - {device: format-12, path: /boot/efi, type: mount, id: mount-12}
I'm not sure what the bios_grub flag does on the ESP - it's needed for the BIOS compat partition and not needed on a ESP. Seems harmless in testing but at best it does nothing.

Revision history for this message
Dan Bungert (dbungert) wrote :

Marking 'invalid' as I believe there is no bug here.

Changed in subiquity (Ubuntu):
status: New → Invalid
Revision history for this message
Dan Bungert (dbungert) wrote :

Christopher, feel free to update the bug if you retry with /boot as ext4 and find it's still not working. Thanks.

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.