Bug 1278810
Summary: | sosreport gets avc messages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marius Vollmer <mvollmer> |
Component: | sos | Assignee: | Bryn M. Reeves <bmr> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | bmr, jmoran |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-20 15:27:18 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
Marius Vollmer
2015-11-06 13:26:56 UTC
How are you running sos here? Is this in a container or other namespaced configuration? I'm assuming you're running as root with all normal capabilities? I can see we're running in virt and I can guess at what plugin was running (from the fact we're touching sysctls) but generally it's good to fill out the full bug template unless it's a simple open-and-shut case like the other recent Fedora bugs. > generally it's good to fill out the full bug template unless it's a simple open-and-shut case like the other recent Fedora bugs. True, I was going too fast here, apologies. The messages in comment 0 are from our integration tests, where we run "sosreport --batch" in a fully-dnf-upgraded Fedora 23 VM with setenforce 1. You can also reproduce this with these steps: # virt-builder fedora-23 <start a VM with fedora-23.img> Inside the VM: # dnf install sos # tail -f /var/log/audit/audit.log | grep sos # sosreport --batch You will get a lot of messages. I don't know what they mean and whether something needs fixing, actually... :-) 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. |