Description of problem:

After the update from 2.0.12 to 2.0.13 in the Fdora 35 channel, 389-ds will not start, complaining:

Jan 27 15:52:28 homeserv.farnz.org.uk ds_selinux_restorecon.sh[3553]: restorecon: lstat(/dev/shm/slapd-IPA-FARNZ-ORG-UK) failed: No such file or directory


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

2.0.13

How reproducible:

All the time

Steps to Reproduce:
1. systemctl start dirsrv@IPA-FARNZ-ORG-UK

Actual results:

Fails to start. journalctl -xeu dirsrv shows:

Jan 27 15:52:28 homeserv.farnz.org.uk systemd[1]: Starting 389 Directory Server IPA-FARNZ-ORG-UK....
░░ Subject: A start job for unit dirsrv has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dirsrv has begun execution.
░░ 
░░ The job identifier is 4524.
Jan 27 15:52:28 homeserv.farnz.org.uk ds_selinux_restorecon.sh[3553]: restorecon: lstat(/dev/shm/slapd-IPA-FARNZ-ORG-UK) failed: No such file or directory
Jan 27 15:52:28 homeserv.farnz.org.uk systemd[1]: dirsrv: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStartPre= process belonging to unit dirsrv has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 255.
Jan 27 15:52:28 homeserv.farnz.org.uk systemd[1]: dirsrv: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit dirsrv has entered the 'failed' state with result 'exit-code'.
Jan 27 15:52:28 homeserv.farnz.org.uk systemd[1]: Failed to start 389 Directory Server IPA-FARNZ-ORG-UK..
░░ Subject: A start job for unit dirsrv has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dirsrv has finished with a failure.
░░ 
░░ The job identifier is 4524 and the job result is failed.


Expected results:

389-ds to start and run

Additional info:
If I hack /usr/libexec/dirsrv/ds_selinux_restorecon.sh to have || true on the end of the restorecon line, everything works again. ipactl restart gets my full FreeIPA stack back up and running. I'm thus not blocked.