[Bug 1890612] Update Released

Ɓukasz Zemczak 1890612 at bugs.launchpad.net
Thu Nov 19 10:06:06 UTC 2020


The verification of the Stable Release Update for microcode-initrd has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [Source NEW SRU FOCAL] ITP: Please support loading microcode early,
  whilst otherwise booting without initrd

Status in cloud-images:
  Fix Committed
Status in microcode-initrd package in Ubuntu:
  Fix Released
Status in microcode-initrd source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * New package to provide micorocode-only initrd for application of
  microcode on boot, when otherwise no initrd is in use.

  [Test Case]

   * install microcode-initrd in AWS cloud x86 metal instance
   * reboot, observe that microcode has been applied, and yet the boot was without initrd (observe journalctl -b -k to see that initrd was not used for boot)

  [Regression Potential]

   * This is a brand new package, that will be used by AWS images.
  Otherwise this package will not be automatically installed anywhere.
  Re spinning & promoting AWS images are tested and gated by the CPC
  team.

  [Other Info]
   
   * Original bug report for groovy:

  Normally Ubuntu boots using initrd that has three archives: early
  amd64 microcode, early intel microcode, and compressed main initrd.

  When booting without initrd, simply kernel is loaded without any
  initrd and thus without microcode.

  However, grub supports booting with multiple initrds and one can
  specify a standalone early initrd which contains microcode only, and
  separate main initrd.

  As an added bonus one can also specify just eary microcode initrd
  without a main one, to allow kernel to load microcode early, but
  otherwise boot without an initrd.

  To achieve that I need to introduce a microcode-initrd package will
  will only provide early initrd which only has microcode.

  The intention is to seed microcode-initrd to targets that boot on
  baremental without initrd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1890612/+subscriptions



More information about the foundations-bugs mailing list