Bugzilla – Bug 1220708
Warning: The unit file, source configuration file or drop-ins of apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Last modified: 2024-03-04 02:10:13 UTC
Running "zypper dup" on Tumbleweed yesterday, I got the following confusing warnings at the end of the process, both related to AppArmor: %posttrans(apparmor-abstractions-3.1.7-3.1.noarch) script output: Warning: The unit file, source configuration file or drop-ins of apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units. %posttrans(apparmor-profiles-3.1.7-3.1.noarch) script output: Warning: The unit file, source configuration file or drop-ins of apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units. Running post-transaction scripts It's not clear what, or whether there is anything, actually to do for me as operator here. Intuitively, should such a restart happen automatically? Or am I really expected to copy&paste&run those two commands?
This looks similar to https://bugzilla.suse.com/show_bug.cgi?id=729348 which was about nscd (and reported fixed there).
This looks like a combination of an old workaround for bnc#853019 (yes, from bnc times) aka boo#853019 in combination with (probably) a change in what the %service_del_postun_without_restart macro does. It seems to do nothing nowadays, while in the past it at least did the systemctl daemon-reload IIRC. Fortunately there's a better workaround in apparmor.service nowadays which means I could drop the systemctl workaround and switch over to the %service_del_postun macro. Note: the fix was in %postun of apparmor-parser, which means you'll see the warnings once more on the next update (caused by the currently installed package). See SR 1154195 for the diff for this bugreport, and SR 1154197 towards Factory (which includes some more changes).
This is an autogenerated message for OBS integration: This bug (1220708) was mentioned in https://build.opensuse.org/request/show/1154197 Factory / apparmor