Bug 1949315 - SELinux is preventing systemd-timesyn from watch access on the directory /.
Summary: SELinux is preventing systemd-timesyn from watch access on the directory /.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 34
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1970865
TreeView+ depends on / blocked
 
Reported: 2021-04-14 00:50 UTC by Lyosha Alexeev
Modified: 2021-06-11 10:24 UTC (History)
10 users (show)

Fixed In Version: selinux-policy-34.4-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1970865 (view as bug list)
Environment:
Last Closed: 2021-05-04 01:00:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lyosha Alexeev 2021-04-14 00:50:18 UTC
Description of problem:

systemd-timesyncd fails to start on boot after upgrade to Fedora 34.

Apr 14 02:32:08 polaris systemd[1]: Starting systemd-timesyncd.service...
Apr 14 02:32:08 polaris systemd-timesyncd[1138]: Failed to connect to bus: Permission denied
Apr 14 02:32:08 polaris systemd-timesyncd[1138]: Could not connect to bus: Permission denied
Apr 14 02:32:08 polaris systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 02:32:08 polaris systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 14 02:32:08 polaris systemd[1]: Failed to start systemd-timesyncd.service.
Apr 14 02:32:08 polaris audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 14 02:32:08 polaris systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Apr 14 02:32:08 polaris systemd[1]: Stopped systemd-timesyncd.service.
Apr 14 02:32:08 polaris audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 14 02:32:08 polaris audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 14 02:32:08 polaris systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Apr 14 02:32:08 polaris systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 14 02:32:08 polaris systemd[1]: Failed to start systemd-timesyncd.service.


SELinux is preventing systemd-timesyn from watch access on the directory /.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that systemd-timesyn should be allowed watch access on the  directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-timesyn' --raw | audit2allow -M my-systemdtimesyn
# semodule -X 300 -i my-systemdtimesyn.pp

Additional Information:
Source Context                system_u:system_r:systemd_timedated_t:s0
Target Context                system_u:object_r:root_t:s0
Target Objects                / [ dir ]
Source                        systemd-timesyn
Source Path                   systemd-timesyn
Port                          <Unknown>
Host                          polaris
Source RPM Packages           
Target RPM Packages           filesystem-3.14-5.fc34.x86_64
SELinux Policy RPM            selinux-policy-targeted-34.3-1.fc34.noarch
Local Policy RPM              selinux-policy-targeted-34.3-1.fc34.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     polaris
Platform                      Linux polaris 5.11.13-300.fc34.x86_64 #1 SMP Sun
                              Apr 11 15:07:42 UTC 2021 x86_64 x86_64
Alert Count                   4
First Seen                    2021-04-14 02:32:08 CEST
Last Seen                     2021-04-14 02:32:08 CEST
Local ID                      19553ffe-61f6-460a-abdd-229c165550aa

Raw Audit Messages
type=AVC msg=audit(1618360328.663:158): avc:  denied  { watch } for  pid=1138 comm="systemd-timesyn" path="/" dev="dm-0" ino=2 scontext=system_u:system_r:systemd_timedated_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir permissive=0


Hash: systemd-timesyn,systemd_timedated_t,root_t,dir,watch


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

selinux-policy-34.3-1.fc34.noarch

How reproducible:
Always on boot but seems to work without warnings if started manually after boot is finished.

Steps to Reproduce:
Boot Fedora 34.

Actual results:
systemd-timesyncd fails to start on boot.

Expected results:
Successful systemd-timesyncd start.

Comment 1 Zdenek Pytela 2021-04-14 07:01:50 UTC
I've submitted a Fedora PR to address the issue:
https://github.com/fedora-selinux/selinux-policy/pull/693

Comment 3 Milos Malik 2021-04-14 15:52:35 UTC
Test coverage for this bug exists in a form of PR:
 * https://src.fedoraproject.org/tests/selinux/pull-request/207

The PR waits for review.

Comment 4 Fedora Update System 2021-04-27 19:56:51 UTC
FEDORA-2021-8d26207af7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8d26207af7

Comment 5 Fedora Update System 2021-04-28 01:35:22 UTC
FEDORA-2021-8d26207af7 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8d26207af7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8d26207af7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-05-04 01:00:51 UTC
FEDORA-2021-8d26207af7 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.