What were you trying to do that didn't work?

Our test checking selinux contexts on the installed filesystem failed:

Would relabel /usr/sbin/smartd from system_u:object_r:bin_t:s0 to system_u:object_r:fsdaemon_exec_t:s0 

The context listed via semodule in the installation environment is the expected one:

[anaconda root@kvm-04-guest11 ~]# semanage fcontext -l | grep /usr/sbin/smartd
/usr/sbin/smartd                                   regular file       system_u:object_r:fsdaemon_exec_t:s0 
[anaconda root@kvm-04-guest11 ~]# ls -Z /mnt/sysroot/sbin/smartd
system_u:object_r:bin_t:s0 /mnt/sysroot/sbin/smartd

Also, after removing and installing the smartmontools package again in the installed system, the context is set properly. Based on this observation, I believe the issue may be caused by Anaconda, even though the particular mechanism is not clear to me.

What is the impact of this issue to you?

It may potentially cause issues to smartd due to possible AVC denials.

Please provide the package NVR for which the bug is seen:

anaconda-40.22.3.32-1.el10 (smartmontools-selinux-7.4-8.el10, selinux-policy-42.1.7-1.el10) on RHEL-10.1-20250826.2

How reproducible is this bug?:

Always.

Steps to reproduce

1. Install with the default package set (%packages --default in kickstart).
2. Run restorecon -vn /usr/sbin/smartd to check if the selinux file context is set properly.

Expected results

The file context is set properly, no warnings from restorecon are printed.

Actual results

restorecon shows an improper selinux context.