[Bug 1890612] Re: ITP: Please support loading microcode early, whilst otherwise booting without initrd

[Dimitri John Ledkov]

NEW source package
https://launchpad.net/ubuntu/focal/+queue?queue_state=0&queue_text
=microcode-initrd

** Package changed: ubuntu => microcode-initrd (Ubuntu)

** Changed in: microcode-initrd (Ubuntu)
       Status: New => Fix Released

** Also affects: microcode-initrd (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: cloud-images
       Status: New => Fix Committed

** Description changed:

+ [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.

** Summary changed:

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

-- 
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:
  New

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