Bug 820286
Summary: | Audit log gets filled with a call to rpm by qemu-kvm that has not been escaped properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Edvard Fagerholm <edvard.fagerholm> |
Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | amit.shah, berrange, cfergeau, dwalsh, dwmw2, ehabkost, itamar, knoel, mgrepl, pbonzini, scottt.tw, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-20 23:54:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Edvard Fagerholm
2012-05-09 14:14:04 UTC
Strange, I don't get this error with setroubleshoot in F17. But we should definitely add a check to make sure the file exists. If you run ausearch -m avc, what output are you getting? Fixed in setroubleshoot-3.1.11-1.fc16 setroubleshoot-3.1.11-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/setroubleshoot-3.1.11-1.fc16 Package setroubleshoot-3.1.11-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing setroubleshoot-3.1.11-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7549/setroubleshoot-3.1.11-1.fc16 then log in and leave karma (feedback). setroubleshoot-3.1.11-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |