| Summary: | should be setroubleshoot-server be pulling setroubleshoot, in other words be dependant of | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lejeczek <peljasz> |
| Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | dan, dwalsh, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | setroubleshoot-3.0.37-1.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-06 21:24:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
SEtroubleshoot requires X, which we do not want to require. This is a bug, since sealert/setroubleshoot should not require setroubleshoot. What version are you seeing this on. *** Bug 716515 has been marked as a duplicate of this bug. *** Fixed in setroubleshoot-3.0.37-1.fc14 setroubleshoot-3.0.37-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/setroubleshoot-3.0.37-1.fc14 Package setroubleshoot-3.0.37-1.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing setroubleshoot-3.0.37-1.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/setroubleshoot-3.0.37-1.fc14 then log in and leave karma (feedback). setroubleshoot-3.0.37-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: sealert -l f214450c-9e1a-4b0c-911c-446b8cd33333 Opps, sealert hit an error! Traceback (most recent call last): File "/usr/bin/sealert", line 712, in <module> command_line_lookup_id(local_id) File "/usr/bin/sealert", line 197, in command_line_lookup_id cl = SECommandLine(lookup_local_id) File "/usr/bin/sealert", line 438, in __init__ from setroubleshoot.serverconnection import ServerConnectionHandler ImportError: No module named serverconnection Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: