Bug 1422181

Summary:	Show SELinux policy options even if setroubleshoot isn't installed
Product:	Red Hat Enterprise Linux 7	Reporter:	Dominik Perpeet <dperpeet>
Component:	cockpit	Assignee:	Dominik Perpeet <dperpeet>
Status:	CLOSED ERRATA	QA Contact:	Jan Ščotka <jscotka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	Keywords:	Extras
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-02 19:10:43 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 Dominik Perpeet 2017-02-14 16:35:21 UTC

Description of problem:
Especially on RHEL Atomic Host, SELinux troubleshooting may not be available. Nevertheless, cockpit can still show the current SELinux policy and if SELinux is enabled, allow toggling between enforcing and permissive mode.

Right now, all the user sees is an error (EmptyState pattern). On Atomic Host, the user can't do anything about this, leaving them with an unusable page.


Version-Release number of selected component (if applicable):
Up to 131-2

How reproducible:
Always

Steps to Reproduce:
Open "SELinux Troubleshooting" in Cockpit

Actual results:
Page shows error / empty state if there is no setroubleshoot-server installed

Expected results:
Show current SELinux policy and allow toggling between permissive/enforcing if it's enabled.

Additional info:
Upstream pull request https://github.com/cockpit-project/cockpit/pull/5868

Comment 5 errata-xmlrpc 2017-03-02 19:10:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0411.html