| 2022-06-01 22:46:40 |
Etienne URBAH |
description |
On some systems snapd relies on apparmor.service systemd unit to load apparmor profiles on boot. As we found in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1803476 the service may be disabled for arbitrary reason, leading to hard-to-diagnose issues. The interface manager's ensure method might ask systemd about the state of apparmor.service and if such unit exists but is disabled, issue a warning about it to the user. |
On some systems, snapd relies on apparmor.service and snapd.apparmor.service systemd units to load apparmor profiles on boot.
As we found in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1803476 apparmor.service may be disabled for arbitrary reason, leading to hard-to-diagnose issues.
Also snapd.apparmor.service may be disabled for arbitrary reason, leading to hard-to-diagnose issues.
The interface manager's ensure method might ask systemd about the state of apparmor.service and snapd.apparmor.service.
If any such unit exists but is disabled or exited with failure, issue a warning about it to the user. |
|
