[Bug 1840670] Re: amd64-microcode better initramfs hook

[Robie Basak]

> It is hard to generate initrd, with all microcodes included because
the initramfs hook ignores preset defaults.

How does this impact users: why might a user want to generate such an
initrd and what breaks by not being able to do it?

If another SRU team member already understands then that's fine, but I
don't think that I can accept an SRU unless I can understand why we're
doing it.

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

Title:
  amd64-microcode better initramfs hook

Status in amd64-microcode package in Ubuntu:
  Fix Released
Status in amd64-microcode source package in Xenial:
  In Progress
Status in amd64-microcode source package in Bionic:
  In Progress
Status in amd64-microcode source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * It is hard to generate initrd, with all microcodes included because the initramfs hook ignores
     preset defaults. Adjust hook to take preset defaults into account.

  [Test Case]

   * Install new package, and check that initrd with default settings (i.e. modules=most) has amd64
     microcode included. And that with modules=dep|list it only does so, if one is on AMD cpu.

   * Install initramfs-tools-ubuntu-core from snap image PPA, the resulting initrd should contian
     both amd64 and intel microcode, despite using modules=list, due to the conf.d default settings
     it overrides.

  [Regression Potential]

   * The hook default behaviour is not changed, only integration with
  custom conf.d's is improved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1840670/+subscriptions