Bug 1398681

Summary:	restorecon: Warning no default label for /var/spool/cron/root
Product:	[Fedora] Fedora	Reporter:	David Highley <david.m.highley>
Component:	selinux-policy-targeted	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED EOL	QA Contact:	Ben Levenson <benl>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	25	CC:	dwalsh
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:18:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Highley 2016-11-25 14:48:08 UTC

Description of problem:
Cron task were failing to run

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit crond.service has finished shutting down.
Nov 25 06:13:56 redwood systemd[1]: Started Command Scheduler.
-- Subject: Unit crond.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit crond.service has finished starting up.
--
-- The start-up result is done.
Nov 25 06:13:56 redwood audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=crond comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'
Nov 25 06:13:56 redwood crond[2234]: (CRON) INFO (RANDOM_DELAY will be
scaled with factor 16% if used.)
Nov 25 06:13:56 redwood crond[2234]: (root) Unauthorized SELinux
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
file_context=unconfined_u:object_r:rsync_data_t:s0
(/var/spool/cron/root)
Nov 25 06:13:56 redwood crond[2234]: (root) SELinux in permissive mode,
continuing (/var/spool/cron/root)
Nov 25 06:13:56 redwood crond[2234]: (CRON) INFO (running with inotify
support)
Nov 25 06:13:56 redwood crond[2234]: (CRON) INFO (@reboot jobs will be
run at computer's startup.)
Nov 25 06:14:06 redwood NetworkManager[1169]: <info>  [1480083246.6163]
device (wlp3s0): supplicant interface state: inactive -> scanning


Expected results:


Additional info:
Had an administrator event and needed to do some recovery of a system. After recovering to include a dnf reinstall of all packages and an selinux relabel of the entire system. I see that there is no default context for /var/spool/cron/root. To fix this issue I had to look at another system to get the correct context labels. Then I did the following:

chcon -v -t user_cron_spool_t /var/spool/cron/root

If you do this afterward you, it does nothing:
restorecon -v /var/spool/cron/root
restorecon:  Warning no default label for /var/spool/cron/root

Then I did the following:
systemctl restart crond

Then I did:
systemctl status crond

Comment 1 David Highley 2016-11-25 17:35:25 UTC

Forgot the version numbers:
selinux-policy-3.13.1-224.fc25.noarch
selinux-policy-targeted-3.13.1-224.fc25.noarch

Another fix might have been to remove the file and recreate it with crontab but still seems to be an issue if the context label is not fixed by restorcon or a system wide relabel.

Comment 2 Daniel Walsh 2016-11-28 17:47:01 UTC

The problem is there is no default label for files in /var/spool/cron/root, You could setup the root process to run as different labels, which is why restorecon does not change it.

Comment 3 Fedora End Of Life 2017-11-16 19:18:02 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:18:26 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.