lxd-agent-loader might fail on selinux enabled VMs
Bug #2058303 reported by
Simon Déziel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lxd-agent-loader (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
This was originally reported at https:/
On Red Hat based VMs using SELinux, we seem to be occasionally hitting lxd-agent startup issues due to systemd not being able to execute the agent binary.
This is because of SELinux labeling issues and typically only kicks-in after a full re-label.
The particular issue with the agent can be fixed by setting the appropriate label on the agent binary as part of its creation.
Related branches
~sdeziel/ubuntu/+source/lxd-agent-loader:noble-bug-fixes
- Lucas Kanashiro (community): Approve
- Thomas Parrott (community): Approve
-
Diff: 75 lines (+45/-1)3 files modifieddebian/changelog (+8/-0)
debian/lxd-agent-loader.postinst (+33/-0)
lxd-agent-setup (+4/-1)
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in lxd-agent-loader (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package lxd-agent-loader - 0.7
---------------
lxd-agent-loader (0.7) noble; urgency=medium
* d/lxd-agent-
* lxd-agent-setup: Bump /run/lxd_agent size to 50M (LP: #2058302)
* lxd-agent-setup: Attempt to restore SELinux labels (LP: #2058303)
-- Simon Deziel <email address hidden> Tue, 13 Feb 2024 16:48:15 -0500