Bug 821630

Summary:	RFE: Abrt selinux cases are not including sosreport
Product:	Red Hat Enterprise Linux 6	Reporter:	Yogesh <ychavan>
Component:	libreport	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	jmoskovc, mgrepl, nobody+abrt-devel-list, syeghiay, vgaikwad
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-10 11:35:40 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 Yogesh 2012-05-15 07:35:23 UTC

Description of problem:
Attachment file that comes with selinux cases reported via abrt does not contain sosreport

Version-Release number of selected component (if applicable):
RHEL6.2

How reproducible:
always

Steps to Reproduce:
1. Report any selinux via abrt.
  
Actual results:
attachment contains file content.xml and there is no sosreport included

Expected results:
Sosreport should be included. /var/log/audit.log and ps -efZ will provide important information. 


Additional info:
It should also provide
semanage login -l 
semanage user -l
id -Z

Comment 1 Jiri Moskovcak 2012-05-15 08:00:41 UTC

And did selinux cases ever contain the sosreport or is this a request to add it?

Comment 2 RHEL Program Management 2012-05-19 04:04:05 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Yogesh 2012-05-21 13:32:33 UTC

Hi Jiri,

This is request to add sosreport with selinux report.

Comment 4 Jiri Moskovcak 2012-06-12 13:58:22 UTC

Actually ABRT doesn't catch AVCs in RHEL and libreport just sends the data to bugzilla, so it's setroubleshoot who needs to run sosreport and pass the resulting file to libreport

Comment 5 Yogesh 2012-06-12 15:32:05 UTC

Can we get at least this information?
# ps auxZ
# lsof -Z
# ls -lZ <target file>

Comment 6 Daniel Walsh 2012-06-12 16:14:09 UTC

The setroubleshoot report includes the source context of the process that created the AVC, and in most cases the target context of the object that is being denied.

Comment 7 Yogesh 2012-06-14 06:55:05 UTC

Even if we accept that setroubleshoot alert includes very less information, Can we do post-processing after we get the report in libreport?
For all selinux cases, we need to ask output of these commands as first question.

Comment 8 RHEL Program Management 2012-07-10 06:52:30 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 9 RHEL Program Management 2012-07-11 01:57:48 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 11 Jiri Moskovcak 2013-07-10 11:20:09 UTC

These changes are quite big for this time in devel cycle -> moving to 6.6

Comment 12 RHEL Program Management 2013-07-10 11:35:40 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.