[SRU] Log flood when installing acpid and acpi-support inside a 22.04 container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acpid (Debian) |
Fix Released
|
Unknown
|
|||
acpid (Ubuntu) |
Fix Released
|
Undecided
|
Luís Infante da Câmara |
Bug Description
[Impact]
The acpid.service unit contains `ConditionVirtu
The acpid.path unit contains `DirectoryNotEm
This SRU fixes this by adding `ConditionVirtu
[Test Plan]
1) Create Jammy and Focal containers
lxc launch ubuntu:22.04 jammy-ctn
lxc launch ubuntu:20.04 focal-ctn
2) Install acpid and acpi-support in the Jammy 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
4) Stop the Jammy container
lxc stop jammy-ctn
5) Install acpid and acpi-support in the Focal container
lxc exec focal-ctn -- apt-get update
lxc exec focal-ctn -- apt-get install -Vy acpid acpi-support
6) Check the logs while apt is stalled at "Setting up acpi-support", if it gets stalled, or after the installation otherwise
lxc exec focal-ctn -- journalctl -fu acpid.service
3) will show a huge flood of, and 6) will show several 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 $CONTAINER -- sh -c 'mv /etc/acpi/events/* /tmp/'
[Where problems could occur]
This could affect non-container environments, such as native Ubuntu machines and Ubuntu VMs.
Changed in acpid (Debian): | |
status: | Unknown → New |
Changed in acpid (Debian): | |
status: | New → Fix Released |
summary: |
- log flood when installing acpid and acpi-support inside a 22.04 + [SRU] Log flood when installing acpid and acpi-support inside a 22.04 container |
description: | updated |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.