[Bug 1977896] Re: log flood when installing acpid and acpi-support inside a 22.04 container

[Simon Déziel]

** Bug watch added: Debian Bug tracker #1009301
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009301

** Also affects: acpid (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009301
   Importance: Unknown
       Status: Unknown

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

Title:
  log flood when installing acpid and acpi-support inside a 22.04
  container

Status in acpid package in Ubuntu:
  New
Status in acpid package in Debian:
  Unknown

Bug description:
  # Steps to reproduce

  1) Create a Jammy container
  lxc launch ubuntu:22.04 jammy-ctn
  2) Install acpid and acpi-support in the container
  lxc exec jammy-ctn -- apt-get update
  lxc exec jammy-ctn -- apt-get install -Vy acpid acpi-support
  3) Check the logs while apt is stalled at "Setting up acpi-support"
  lxc exec jammy-ctn -- journalctl -fu acpid.service

  3) will show a huge flood of:

  Jun 07 23:42:50 jammy-ctn systemd[1]: Condition check resulted in ACPI
  event daemon being skipped.

  A workaround is to empty /etc/acpi/events with:

  lxc exec jammy-ctn -- sh -c 'mv /etc/acpi/events/* /tmp/'

  # Initial analysis

  The acpid.service unit contains `ConditionVirtualization=!container`
  but something keeps asking systemd to start the acpid service which is
  not possible due to the unmet condition (!container).

  The acpid.path unit contains `DirectoryNotEmpty=/etc/acpi/events/`
  meaning that it uses inotify to trigger the acpid.service which is
  probably what's causing the endless loop.

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