[Bug 2023462] Autopkgtest regression report (systemd/249.11-0ubuntu3.10)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.10) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.4.10 (armhf)
casync/2+20201210-1build1 (ppc64el)
comitup/1.15-1 (armhf)
dbus/1.12.20-2ubuntu4.1 (armhf)
initramfs-tools/0.140ubuntu13.4 (s390x)
linux-azure-5.19/5.19.0-1027.30~22.04.2 (arm64)
linux-gcp-6.2/6.2.0-1011.11~22.04.3 (arm64)
linux-lowlatency/5.15.0-83.92 (arm64)
linux-lowlatency-hwe-5.19/5.19.0-1030.30 (arm64)
linux-nvidia-tegra/5.15.0-1016.16 (arm64)
linux-oracle-5.19/5.19.0-1027.30 (arm64)
mkosi/unknown (s390x)
munin/2.0.57-1ubuntu2 (armhf)
netplan.io/0.105-0ubuntu2~22.04.3 (arm64)
prometheus-postfix-exporter/unknown (s390x)
samba/2:4.15.13+dfsg-0ubuntu1.4 (arm64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  chromeos_pstore.service started on non chrome platform hardware.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Kernel modules that provide pstore backends are unnecessarily loaded
  by systemd-pstore.service. While this is pretty benign behavior, it
  was introduced by an earlier SRU (bug 1978079) and is not consistent
  with newer releases in which systemd-pstore.service only tries to load
  efi_pstore.

  [Test Plan]

  Check which modules systemd-pstore.service depends on:

  $ systemctl list-dependencies systemd-pstore.service
  systemd-pstore.service
  * |--.mount
  * |-modprobe at chromeos_pstore.service
  * |-modprobe at efi_pstore.service
  * |-modprobe at pstore_blk.service
  * |-modprobe at pstore_zone.service
  * |-modprobe at ramoops.service
  * `-system.slice

  On an affected machine, we see several pstore providers in addition to
  efi_pstore. On a patched system, we should only see efi_pstore.

  [Where problems could occur]

  If somehow a user was running a configuration where one of the other
  modules was needed for pstore on their system, and that module was not
  loaded when systemd-pstore.service ran, they might not get correct
  output. However, the original bug (bug 1978079) was only about
  efi_pstore, and that will still be loaded by systemd-pstore.service.
  On all releases newer than Jammy, only efi_pstore is loaded by
  systemd-pstore.service, and there have not been bug reports.

  [Original Description]

  systemd-analyze blame | grep pstore

  110ms modprobe at chromeos_pstore.service
  5ms modprobe at efi_pstore.service
  5ms modprobe at pstore_blk.service
  3ms modprobe at pstore_zone.service

  /lib/systemd/system/systemd-pstore.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023462/+subscriptions