Bug 2284340

Summary: User home directory is not created with version 40.21-1
Product: [Fedora] Fedora Reporter: Yevhen Popok <xalt7x.service>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: dwalsh, fortnerryan, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---Keywords: Desktop, Regression
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-03 11:12:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yevhen Popok 2024-06-02 22:30:18 UTC
After update to version 40.21-1.fc41 I can't enter user home directory because it's not created.

On TTY I see such messages:

> Could not chdir to home directory /home/user: No such file or directory
>
> Welcome to Fedora Linux Rawhide.20240601.n.0 (Kinoite Prerelease).
>
> mkdir: cannot create directory ‘/home/user’: Permission denied
> touch: cannot touch '/home/user/.config/toolbox/host-welcome-shown': No such file or directory

With journalctl -xb I've spotted such errors:

> Jun 03 00:50:54 fedora systemd[1]: home.mount: Failed with result 'resources'.
> ░░ Subject: Unit failed
> ░░ Defined-By: systemd
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ The unit home.mount has entered the 'failed' state with result 'resources'.
> Jun 03 00:50:54 fedora systemd[1]: Failed to mount home.mount - /home.
> ░░ Subject: A start job for unit home.mount has failed
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ A start job for unit home.mount has finished with a failure.
> ░░
> ░░ The job identifier is 2505 and the job result is failed.
> Jun 03 00:50:54 fedora systemd[1]: Dependency failed for session-2.scope - Session 2 of User y.
> ░░ Subject: A start job for unit session-2.scope has failed
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ A start job for unit session-2.scope has finished with a failure.
> ░░
> ░░ The job identifier is 2397 and the job result is dependency.
> Jun 03 00:50:54 fedora systemd[1]: session-2.scope: Job session-2.scope/start failed with result 'dependency'.
> Jun 03 00:50:54 fedora sshd[1338]: pam_systemd(sshd:session): Failed to create session: Job 2397 for unit 'session-2.scope' failed with 'dependency'
> Jun 03 00:50:54 fedora sshd[1338]: pam_unix(sshd:session): session opened for user y(uid=1000) by y(uid=0)
> Jun 03 00:50:54 fedora systemd[1]: Starting user-runtime-dir - User Runtime Directory /run/user/1000...
> ░░ Subject: A start job for unit user-runtime-dir has begun execution
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ A start job for unit user-runtime-dir has begun execution.
> ░░
> ░░ The job identifier is 2180.

The issue goes away if I roll-back to version 40.20-1.fc41. On Fedora Atomic I can do this by wget-ing packages from Koji (https://koji.fedoraproject.org/koji/buildinfo?buildID=2453834) and performing "override replace" (rpm-ostree override replace selinux-policy-40.20-1.fc41.noarch.rpm selinux-policy-targeted-40.20-1.fc41.noarch.rpm)

Reproducible: Always

Steps to Reproduce:
1. Install Fedora Atomic Desktop (e.g., Kinoite or Silverblue) and switch to Rawhide branch
2. Update to the image that contains updated selinux-policy package (e.g., Rawhide.20240601.n.0)
3.Restart and login as your user
Actual Results:  
User have root directory as home directory because /home directory is not created

Expected Results:  
User have his home directory

Comment 1 Zdenek Pytela 2024-06-03 11:12:34 UTC

*** This bug has been marked as a duplicate of bug 2284276 ***