Created attachment 1145363 [details] Journal from boot to graphical login Description of problem: Cannot login to kde5 (plasma) before having done a login in virtual console. When loggin in (textual) this results in: ' -- kim: /home/kim: change directory failed: Permission denied' cat /proc/mounts shows nfs mount as 'mounted' and I am allowed to succeed with a 'cd' I can still not make a successful graphical login, before executing: 'ls /home' which triggers something :-0 May be related to Bug 1323291 (https://bugzilla.redhat.com/show_bug.cgi?id=1323291) Version-Release number of selected component (if applicable): systemd-229-7.fc24.x86_64 nfs-utils-1.3.3-7.rc4.fc24.x86_64 selinux-policy-targeted-3.13.1-180.fc24.noarch How reproducible: Always Additional info: Machine upgraded from f23 to f24 at alpha release Journal from boot to graphical login attached /etc/fstab: UUID=6bfbb0ba-c87b-451e-a79a-7ca1c90e8a61 /boot ext3 defaults 1 2 UUID=96474438-2592-433c-9d68-5f5895c4ac2b /opt ext4 defaults 1 2 UUID=1066aafc-8288-4621-a13a-e244c277d608 / ext4 defaults 1 1 UUID=1d7a5fad-241a-4046-b6bc-e8b88db8b882 /data ext4 defaults 1 2 UUID=3ef6d7a8-3002-4005-8dab-c04c7eab91f5 swap swap defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 jukebox:/home /home nfs defaults,comment=systemd.automount 0 0 jukebox:/data /misc/data nfs defaults,comment=systemd.automount 0 0 #jukebox:/home /home nfs defaults,fscontext=unconfined_u:object_r:user_home_dir_t:s0 0 0
Just found a selinux boolean w.r.t. nfs-home-dirs and switched it on. That's not new is it? Does not seem to make a difference though, still same symptoms.
I get there selinux alerts (no idea if they are related): Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:etc_t:s0 Target Objects /etc [ dir ] Source (coredump) Source Path (coredump) Port <Unknown> Host kim.alleroedderne.adsl.dk Source RPM Packages Target RPM Packages filesystem-3.2-37.fc24.x86_64 Policy RPM selinux-policy-3.13.1-180.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name kim.alleroedderne.adsl.dk Platform Linux kim.alleroedderne.adsl.dk 4.5.0-302.fc24.x86_64 #1 SMP Wed Mar 30 15:41:34 UTC 2016 x86_64 x86_64 Alert Count 5 First Seen 2016-04-02 10:52:32 CEST Last Seen 2016-04-10 09:00:22 CEST Local ID ff65eb1c-0822-4433-966b-65df627625f4 Raw Audit Messages type=AVC msg=audit(1460271622.820:342): avc: denied { mounton } for pid=2031 comm="(coredump)" path="/etc" dev="sda3" ino=652802 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=dir permissive=0 and: Additional Information: Source Context system_u:system_r:local_login_t:s0-s0:c0.c1023 Target Context system_u:object_r:unlabeled_t:s0 Target Objects / [ dir ] Source login Source Path login Port <Unknown> Host kim.alleroedderne.adsl.dk Source RPM Packages Target RPM Packages filesystem-3.2-37.fc24.x86_64 Policy RPM selinux-policy-3.13.1-180.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name kim.alleroedderne.adsl.dk Platform Linux kim.alleroedderne.adsl.dk 4.5.0-302.fc24.x86_64 #1 SMP Wed Mar 30 15:41:34 UTC 2016 x86_64 x86_64 Alert Count 20 First Seen 2016-04-03 15:05:25 CEST Last Seen 2016-04-10 08:59:21 CEST Local ID f304f308-d19a-4166-b4ec-47f58d39ff92 Raw Audit Messages type=AVC msg=audit(1460271561.558:304): avc: denied { search } for pid=1434 comm="login" name="/" dev="0:49" ino=2 scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=dir permissive=0
Hi, Yes keep boolean "use_nfs_home_dirs " turned on. Could you run # restorecon -R -v / And then try to reproduce your issue?
Unfortunately after relabling the whole file system I still have the problem :-(
Is is possible to give a kernel boot argument disabling selinux? - so that I can rule out that this is a selinux problem and thus a problem in (systemd/nfs/...)
enforcing=0 will disable SELinux enforcing mode selinux=0 will disable SELinux.
Either of these arguments, makes the problem go away - phew I got lucky to assign this close to where it belongs ;-) selinux-policy-targeted-3.13.1-184.fc24.noarch
Still a problem with: selinux-policy-targeted-3.13.1-191.fc24.2.noarch
Also in f25 with: selinux-policy-targeted-3.13.1-214.fc25.noarch
Still a problem with: selinux-policy-targeted-3.13.1-224.fc25.noarch
I have this problem too. I also have to drop to a console and issue an ls /home to be able to login graphically. To add a bit of information: When I can't log in graphically and drop to the shell, the selinux label is initially unlabelled_t. After doing nothing else but a directory listing of home, the selinux label changes to home_root_t. I scripted the steps, and include the output here: + ls -Zd /home system_u:object_r:unlabeled_t:s0 /home + ls /home anonymous lost+found marty projects root + ls -Zd /home system_u:object_r:home_root_t:s0 /home I suspect it's more related to support for NFS attributes that was added in Fedora 24, but I don't know how to go about diagnosing the problem further.
I had some hopes because of the other NFS bugfix but no - Still a problem with: selinux-policy-3.13.1-225.3.fc25.noarch
Still a problem with: selinux-policy-targeted-3.13.1-249.fc26.noarch
The problem disappeared this boot. Yesterday I upgraded and got: Upgraded rpcbind-0.2.4-7.rc1.fc26.x86_64 @updates-testing Upgrade 0.2.4-7.rc2.fc26.x86_64 @updates-testing Upgraded sssd-nfs-idmap-1.15.2-3.fc26.x86_64 @updates-testing Upgrade 1.15.2-5.fc26.x86_64 @updates-testing and others, but no selinux or systemd - go figure :-)
The problem appears to have disappeared on my system too. The last SELinux alert for that problem is from June 4th. I did an update on that date, but installed over 400 packages which included systemd, selinux, and the aforementioned rpcbind, and sssd-nfs-idmap. I won't be able to identify which package solved the problem.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.