[Bug 1915114] Re: Ubiquity: No vmlinuz* after install. 20.04.2

Dimitri John Ledkov 1915114 at bugs.launchpad.net
Tue Feb 9 13:59:58 UTC 2021


** Also affects: ubiquity (Ubuntu Hirsute)
   Importance: Critical
       Status: Triaged

** Also affects: oem-qemu-meta (Ubuntu Hirsute)
   Importance: High
       Status: Triaged

** Also affects: ubiquity (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: oem-qemu-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: ubiquity (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: ubiquity (Ubuntu Focal)
       Status: New => In Progress

** Changed in: ubiquity (Ubuntu Hirsute)
       Status: Triaged => Fix Committed

** Changed in: oem-qemu-meta (Ubuntu Focal)
       Status: New => Confirmed

** Changed in: oem-qemu-meta (Ubuntu Focal)
       Status: Confirmed => Triaged

** Changed in: oem-qemu-meta (Ubuntu Focal)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1915114

Title:
  Ubiquity: No vmlinuz* after install. 20.04.2

Status in oem-qemu-meta package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Fix Committed
Status in oem-qemu-meta source package in Focal:
  Triaged
Status in ubiquity source package in Focal:
  In Progress
Status in oem-qemu-meta source package in Hirsute:
  Triaged
Status in ubiquity source package in Hirsute:
  Fix Committed

Bug description:
  Ubiquity

  [Impact]

   * Certain SKUs of laptops; when networking is enabled; complete the
  installation successfully, without installing any kernel on the system
  rendering it unbootable.

  [Test Case]

   * Start install on a relevant SKU

   * Enable networking on

   * Ensure that after the installation kernel packages are installed in
  /target

   * Reboot to observe that installed

  [Where problems could occur]

   * Hopefully we will not remove kernels again.... especially the one
  we want to boot.

  [Other Info]

   * Original bug report

  I was installing ubuntu on my fresh new notebook and found that kernel
  packages wasn't installed. As workaround to run the system I had to
  chroot into /target to complete installation.

  I have one disk and it was partitioned as GPT.

  Initialy I thought  it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
  Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.

  It took me 2 days(((

  
  ===

  oem-qemu-meta

  * To ensure this doesn't happen again, we must update the test oem-
  qemu-meta package to match the behaviour of the other similar packages
  in the oem archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oem-qemu-meta/+bug/1915114/+subscriptions



More information about the foundations-bugs mailing list