Bug 1435100

Summary:	fcontext --extract does not work when socket entries are present in custom fcontext policy
Product:	Red Hat Enterprise Linux 7	Reporter:	Zdenek Pytela <zpytela>
Component:	policycoreutils	Assignee:	Petr Lautrbach <plautrba>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	dwalsh, lvrabec, mgrepl, mmalik, plautrba, ssekidde
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	policycoreutils-2.5-15.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1435127 (view as bug list)		Environment:
Last Closed:	2017-08-01 16:16:12 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:
Bug Depends On:
Bug Blocks:	1435127

Description Zdenek Pytela 2017-03-23 07:16:21 UTC

Description of problem:
semanage fcontext -E does not work when custom policy contains filetype socket spoecification.

Version-Release number of selected component (if applicable):
policycoreutils-python-2.5-11.el7_3.x86_64

How reproducible:
always

Steps to Reproduce:
1. semanage fcontext -E
2. semanage fcontext -a -f s -t httpd_var_run_t '/var/www/\.sockets(/.*)?'
3. semanage fcontext -E

Actual results:
KeyError: socket
(exit code 1)

Expected results:
list of customizable commands


Additional info:
Seems to be fixed in this commit:
https://github.com/SELinuxProject/selinux/commit/317743bbe2a235a5c68f1066b4153e0726a3118f

semanage fcontext with other file types work correctly
the same is valid for RHEL 7.4 and F25

Comment 8 errata-xmlrpc 2017-08-01 16:16:12 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://access.redhat.com/errata/RHBA-2017:1883