Bug 1411008
Summary: | [abrt] setroubleshoot-server: __init__.py:53:info:RuntimeError: Policy not loaded | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pat Kelly <pmkellly72> | ||||||
Component: | setroubleshoot | Assignee: | Petr Lautrbach <plautrba> | ||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 24 | CC: | dwalsh, mgrepl, plautrba, pmkellly72, pmoore, titaniumkeys, vmojzis | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/5ab33a7304e4a536fd01d248dd1ad63a28e20796 | ||||||||
Whiteboard: | abrt_hash:ee92ec6922200e99a972e5024f4e6196ea1621cb;VARIANT_ID=workstation; | ||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2017-08-08 19:33:09 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: | |||||||||
Attachments: |
|
Description
Pat Kelly
2017-01-07 12:48:14 UTC
Created attachment 1238219 [details]
File: backtrace
Created attachment 1238220 [details]
File: environ
Thank you for reporting the issue. Could you provide more information? The following would be useful: What were you doing when the issue occured (are you able to reproduce it)? What is the output of "sestatus"? Is your system up to date? Similar problem has been detected: Starting SELinux Troubleshooter. Crashed on startup GUI did not appear reporter: libreport-2.7.2 cmdline: /usr/bin/python3 -Es /usr/bin/sealert -b event_log: 2017-01-12-07:21:21> ('report_uReport' completed successfully) executable: /usr/bin/sealert kernel: 4.8.15-200.fc24.x86_64 package: setroubleshoot-server-3.3.11-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: __init__.py:53:info:RuntimeError: Policy not loaded runlevel: N 5 type: Python3 uid: 1000 Please try removing "firewalld-selinux" package from your system in case it is present an reinstalling "selinux-policy" and "selinux-policy-targeted" (or whichever policy type you are using). After restarting your machine, run "#sestatus" to make sure selinux is in enforcing mode (if not, please change "SELINUX" field in "/etc/selinux/config" to "enforcing"). "sealert" is not designed to work without active SELinux module. Similar problem has been detected: Clicked SELinux icon SELinux Troubleshooter did not start. However the title appeared in the top bar for a while like it was going to start. I sent e'mail with more information when additional information was requested. reporter: libreport-2.7.2 cmdline: /usr/bin/python3 -Es /usr/bin/sealert -b event_log: 2017-01-13-06:46:51> ('report_uReport' completed successfully) executable: /usr/bin/sealert kernel: 4.8.15-200.fc24.x86_64 package: setroubleshoot-server-3.3.11-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: __init__.py:53:info:RuntimeError: Policy not loaded runlevel: N 5 type: Python3 uid: 1000 The issue was resolved by enabling SELinux, which was disabled due to temporarily missing "selinux-policy" package. Sealert should still not crash in case policy package is missing. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. |