[Bug 1949412] Re: Upgrade fwupd for Atomic Docking Support

[Yuan-Chen Cheng]

test on jammy, install fwupd/libjcat1 from focal proposed channel.
secure boot on

1. upgrade install nvme fw from snap-store: passed
2. upgrade os bios cab from the command line: passed
3. upgrade os bios from gnome-software: passed
4. AI: upgrade WD19SC FW.
5. AI: upgrade Atomic docking fw.

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

Title:
  Upgrade fwupd for Atomic Docking Support

Status in OEM Priority Project:
  In Progress
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-efi package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Committed
Status in fwupd-efi source package in Focal:
  Fix Committed
Status in fwupd-signed source package in Focal:
  Fix Committed
Status in fwupd source package in Hirsute:
  Won't Fix
Status in fwupd-efi source package in Hirsute:
  Won't Fix
Status in fwupd-signed source package in Hirsute:
  Won't Fix
Status in fwupd source package in Impish:
  Fix Committed
Status in fwupd-efi source package in Impish:
  Fix Committed
Status in fwupd-signed source package in Impish:
  Fix Committed
Status in fwupd source package in Jammy:
  Fix Released
Status in fwupd-efi source package in Jammy:
  Fix Released
Status in fwupd-signed source package in Jammy:
  Fix Released

Bug description:
  This is to support Dell's new Atomic Docking and WD22TB4 in focal.

  As fwupd 1.7.x efi split is done, let use 1.7.5 for this.

  In this SRU, it include source package: fwupd-efi, fwupd, fwupd-signed and
  libjcat (LP: #1961864)

  [Impact]

   * Several components that are used in OEM projects need
     to use the fwupd to support firmware update.

   * This will follow the SRU exception in
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * follow the steps in the SRU exception page.
     Need to make sure it still works well even if secure
     boot is on.

   * Given fwupd 1.7.4 is so new, I think we should extended
     the date in proposed channel like 14 days.

   * Plan to loop existing OEM project and also request for
     more regression tests.

  [Where problems could occur]

   * BIOS upgrade failed and brick the machine:
     We test the fwupd in PPA and this does not happen. Given past
     experience, this only happens as we use unstable/not-tested
     bios from vendors.

   * component fw upgrade and the component no longer working:
     Per OEM team experience, this only happens as we use
     unstable/not-tested fw from vendors, or there are special
     steps and we didn't follow up carefully enough.

   * component fw upgraded and kernel driver/firmware in the ubuntu
     the archive does not support it:
     This is possible but has rarely happened before. And this is so
     hard to know in advance if IHV didn't do their job well.
     This only happened in case that the failed fw is not supported
     in the previous fwupd, but it supported in the new fwupd, and
     the new fw happened not been supported by existing
     kernel driver/linux-firmware deb.
     We will notify OEM projects to be aware of it, so it won't
     break things.

   * Other possible failures: those are well-covered in the SRU
     exception test plan.
     - fwupd does not work as Secure boot is on.
     - dbus interface in-compatibility.

  [Other Info]

   * Two bugs will also be fixed with this SRU: lp:1954965, lp:1953573.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1949412/+subscriptions