[Bug 1895200] Re: [MIR] microcode-initrd

[Christian Ehrhardt ]

linux-meta-aws is already in main, I guess that is only here for tracking purposes.
Marking it "opinion" then to reflect that there is no work/change on it.

Furthermore the state for to-be-processed MIR bugs is NEW, setting it to
that and assigning myself to take a look.

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

** Changed in: linux-meta-aws (Ubuntu)
       Status: Confirmed => Opinion

** Changed in: microcode-initrd (Ubuntu)
     Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

-- 
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/1895200

Title:
  [MIR] microcode-initrd

Status in linux-meta-aws package in Ubuntu:
  Opinion
Status in microcode-initrd package in Ubuntu:
  New

Bug description:
  [Availability]

   * Groovy Universe

  [Rationale]

   * Needed to apply microcode updates, on bare-metal public-cloud
  machines, that otherwise boot without a full initrd.

  [Security]

   * This package is tiny, just a single small shell script trigger hook
  that create microcode-initrd from intel-microcode and amd-microcode
  packages.

  [Quality assurance]

   * Installing this package automatically integrates with grub2 thus
  this package needs no configuration to start using.

   * There are no debconf questions

   * Package is new, unique to Ubuntu

  [Dependencies]

   * All dependencies are in main

  [Standards compliance]

   * Complies with policy

  [Maintenance]

   * Foundations-bugs subscribed

  [Background information]

   * Currently we have a few public-clouds with bare-metal instance
  types that boot without initrd. To apply microcode updates as required
  to mitigate Spectre, Meldown, MDS attacks, a microcode-only initrd
  needs to be loaded by grub, as late-loading of microcode is not safe.
  This package was tested successfully on multiple instance types to
  ensure correct operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1895200/+subscriptions