It seems the initial issue of "home-srakit-Music.mount: Failed to check directory /home/srakit/Music: Permission denied" was a configuration issue (client ip address changed). After sorting that out NFS mount is mounting like it should.

Still, initial SELinux denial is in effect, systemd is denied "read access on the Music directory".

In addition to that, trying to configure systemd to automount network share to user /home directory is blocked by selinux.


SELinux is preventing systemd from read access on the directory Music.

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

If you believe that systemd should be allowed read access on the Music 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' --raw | audit2allow -M my-systemd
# semodule -X 300 -i my-systemd.pp


Additional Information:
Source Context                system_u:system_r:init_t:s0
Target Context                unconfined_u:object_r:audio_home_t:s0
Target Objects                Music [ dir ]
Source                        systemd
Source Path                   systemd
Port                          <Unknown>
Host                          oldiemodern
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.6.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     oldiemodern
Platform                      Linux oldiemodern 4.9.9-200.fc25.x86_64 #1 SMP Thu
                              Feb 9 17:28:13 UTC 2017 x86_64 x86_64
Alert Count                   13
First Seen                    2017-02-11 16:55:37 CET
Last Seen                     2017-02-15 19:32:36 CET
Local ID                      98331ebf-40b5-4949-8ba8-95039e369248

Raw Audit Messages
type=AVC msg=audit(1487183556.929:630): avc:  denied  { read } for  pid=1 comm="systemd" name="Music" dev="sda3" ino=1704013 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:audio_home_t:s0 tclass=dir permissive=0


Hash: systemd,init_t,audio_home_t,dir,read

SELinux is preventing systemd from mounton access on the directory /home/srakit/Music.

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

If you believe that systemd should be allowed mounton access on the Music 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' --raw | audit2allow -M my-systemd
# semodule -X 300 -i my-systemd.pp


Additional Information:
Source Context                system_u:system_r:init_t:s0
Target Context                unconfined_u:object_r:audio_home_t:s0
Target Objects                /home/srakit/Music [ dir ]
Source                        systemd
Source Path                   systemd
Port                          <Unknown>
Host                          oldiemodern
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.6.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     oldiemodern
Platform                      Linux oldiemodern 4.9.9-200.fc25.x86_64 #1 SMP Thu
                              Feb 9 17:28:13 UTC 2017 x86_64 x86_64
Alert Count                   3
First Seen                    2017-02-15 19:16:59 CET
Last Seen                     2017-02-15 19:32:36 CET
Local ID                      43c3eb47-381c-415a-a0b5-f7eef699edff

Raw Audit Messages
type=AVC msg=audit(1487183556.929:631): avc:  denied  { mounton } for  pid=1 comm="systemd" path="/home/srakit/Music" dev="sda3" ino=1704013 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:audio_home_t:s0 tclass=dir permissive=0


Hash: systemd,init_t,audio_home_t,dir,mounton

I see the 'read' denied part of this when bind-mounting Music directories from a data disk onto home.

# findmnt
...
├─/home                                          /dev/mapper/VGFastAlpine-LVHome
 ├─/home/oliver/Music                           /dev/mapper/VGAlpine-LVData[/oliver/Music]
│ └─/home/oliver/Videos                          /dev/mapper/VGAlpine-LVData[/oliver/Videos]

Videos/ shows no problems but I see these messages in the journal:

avc:  denied  { read } for  pid=1 comm="systemd" name="Music" dev="dm-6" ino=11927598 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:audio_home_t:s0 tclass=dir permissive=0
home-oliver-Music.mount: Failed to check directory /home/oliver/Music: Permission denied

though it's just warnings (it's trying to fsck?) and there's no problem reading the directories. I also see this with "tcontext=unconfined_u:object_r:virt_home_t:s0" bind-mounted directories.

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.

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.