Description of problem: sudo mdadm --assemble --scan SELinux is preventing mdadm from 'read' accesses on the file mdadm.conf. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that mdadm should be allowed read access on the mdadm.conf file 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: # grep mdadm /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:mdadm_t:s0 Target Context unconfined_u:object_r:user_home_t:s0 Target Objects mdadm.conf [ file ] Source mdadm Source Path mdadm Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-155.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 x86_64 x86_64 Alert Count 2 First Seen 2015-12-11 13:07:46 CET Last Seen 2015-12-11 13:08:59 CET Local ID 56195273-dd71-4521-9679-2cf4671b6889 Raw Audit Messages type=AVC msg=audit(1449835739.679:708): avc: denied { read } for pid=2820 comm="mdadm" name="mdadm.conf" dev="dm-1" ino=2098940 scontext=system_u:system_r:mdadm_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0 Hash: mdadm,mdadm_t,user_home_t,file,read Version-Release number of selected component: selinux-policy-3.13.1-155.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.6-301.fc23.x86_64 type: libreport
Description of problem: sudo mdadm --assemble --scan Version-Release number of selected component: selinux-policy-3.13.1-155.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.6-301.fc23.x86_64 type: libreport
Hi, From strace output I can see this: open("/etc/mdadm.conf", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/mdadm/mdadm.conf", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/mdadm.conf.d", O_RDONLY) = -1 ENOENT (No such file or directory) Could you use restorecon command on these files? # restorecon -v /etc/mdadm* I believe this is caused by mv command. Did you move (using #mv) mdadm config file from your homedir to /etc?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.