Bugzilla – Bug 1185260
'snapper cleanup number' fails with 'Failure (error.something).'
Last modified: 2021-04-29 09:56:24 UTC
On the up-to-date (as of 2021-04-24) Leap 15.3 minimal server install VM, both 'snapper cleanup number' and 'snapper-cleanup' service fail with, not very informative, 'Failure (error.something)' for former and ------ ● snapper-cleanup.service - Daily Cleanup of Snapper Snapshots Loaded: loaded (/usr/lib/systemd/system/snapper-cleanup.service; static) Active: failed (Result: exit-code) since Sat 2021-04-24 14:49:47 CEST; 2h 57min ago TriggeredBy: ● snapper-cleanup.timer Docs: man:snapper(8) man:snapper-configs(5) Process: 23647 ExecStart=/usr/lib/snapper/systemd-helper --cleanup (code=exited, status=1/FAILURE) Main PID: 23647 (code=exited, status=1/FAILURE) Apr 24 14:49:46 leap153-se systemd[1]: Started Daily Cleanup of Snapper Snapshots. Apr 24 14:49:46 leap153-se systemd-helper[23647]: running cleanup for 'root'. Apr 24 14:49:46 leap153-se systemd-helper[23647]: running number cleanup for 'root'. Apr 24 14:49:46 leap153-se systemd-helper[23647]: Failure (error.something). Apr 24 14:49:46 leap153-se systemd-helper[23647]: number cleanup for 'root' failed. Apr 24 14:49:46 leap153-se systemd-helper[23647]: running timeline cleanup for 'root'. Apr 24 14:49:46 leap153-se systemd-helper[23647]: running empty-pre-post cleanup for 'root'. Apr 24 14:49:47 leap153-se systemd[1]: snapper-cleanup.service: Main process exited, code=exited, status=1/FAILURE Apr 24 14:49:47 leap153-se systemd[1]: snapper-cleanup.service: Failed with result 'exit-code'. ----- for latter. Since SELinux is installed and enforcing(from security:SELinux repo), I thought that was the issue, but the error is the same after setting 'enforcing=0', and, AFAICT, there are nothing related in the logs. Other then SELinux, the system is pretty much Leap as shipped, I haven't touched snapper config.
As far as I know it is up to the user to define SELinux policies. Without those many thing do not work. E.g. for me network does also not work (tested with openSUSE Leap Build 134.3). Why this also fails in permissive mode it not clear to me.
(In reply to Arvin Schnell from comment #1) > As far as I know it is up to the user to define SELinux policies. Without > those many thing do not work. E.g. for me network does also not work > (tested with openSUSE Leap Build 134.3). > > Why this also fails in permissive mode it not clear to me. security/SELinux repo ships with selinux-policy, which is, AFAIK, based on Fedora's, with some SUSE/oS tweaks/modifications, FWIW. Since I couldn't find anything related in the logs (which doesn't mean that it isn't there, just that I probably need to look harder), I'll spin up the other, pretty much identical, apart from SELinux, 15.3 VM I have, and see if snapper throws the same error there. That's something I should've done already, before opening this bug, and I apologize :)
Since I can no longer reproduce this, on either vanilla or SELinux-enabled 15.3 VM, you should close this bug. Whatever the issue was, it got cleared up after shutdown/boot cycle, it seems. Apologies for wasting your time.
Nothing more that can be done here.