Description of problem: I guess I did audit2allow during I was updating modules. Anyways it should not crash but give decent or wait until resource is not busy any more. Version-Release number of selected component: policycoreutils-python-utils-2.8-8.fc29 Additional info: reporter: libreport-2.9.7 cmdline: /usr/bin/python3 -Es /usr/bin/audit2allow -b -x -r -l crash_function: main exception_type: SystemError executable: /usr/bin/audit2allow interpreter: python3-3.7.1-4.fc29.x86_64 kernel: 4.19.6-300.fc29.x86_64 runlevel: unknown type: Python3 uid: 0 Truncated backtrace: audit2allow:360:main:SystemError: <built-in function init> returned a result with an error set ValueError: unable to open /sys/fs/selinux/policy: Device or resource busy The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/bin/audit2allow", line 376, in <module> app.main() File "/usr/bin/audit2allow", line 360, in main audit2why.init() SystemError: <built-in function init> returned a result with an error set Local variables in innermost frame: self: <__main__.AuditToPolicy object at 0x7f6f3aaab668>
Created attachment 1515102 [details] File: backtrace
Created attachment 1515103 [details] File: cgroup
Created attachment 1515104 [details] File: cpuinfo
Created attachment 1515105 [details] File: environ
Created attachment 1515106 [details] File: mountinfo
Created attachment 1515107 [details] File: namespaces
Created attachment 1515108 [details] File: open_fds
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.