Bug 1401699 - semanage no longer works as expected in Atomic Host 7.3.0
Summary: semanage no longer works as expected in Atomic Host 7.3.0
Keywords:
Status: CLOSED DUPLICATE of bug 1398427
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: policycoreutils
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Lautrbach
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 21:04 UTC by James W. Mills
Modified: 2016-12-12 17:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-12 17:47:51 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description James W. Mills 2016-12-05 21:04:46 UTC 
Description of problem:

Attempting to set persistent context with semanage no longer works in Atomic Host 7.3.0

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

Red Hat Enterprise Linux Atomic Host 7.3.0

How reproducible:

Always

Steps to Reproduce:
1. Install AH 7.3.0
2. Run 'semanage fcontext -a -t svirt_sandbox_file_t "/var/lib/kubelet(/.*)?"'


Actual results:

# semanage fcontext -a -t svirt_sandbox_file_t "/var/lib/kubelet(/.*)?"
libsemanage.dbase_llist_query: could not query record value (No such file or directory).
OSError: No such file or directory


Expected results:

semanage correctly sets context

Additional Info:

Potentially similar to https://bugzilla.redhat.com/show_bug.cgi?id=1290659
Comment 1 Petr Lautrbach 2016-12-05 21:19:35 UTC 
This is most likely a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1398427
Comment 3 Milos Malik 2016-12-07 08:11:37 UTC 
(In reply to Petr Lautrbach from comment #1)
> This is most likely a duplicate of
> https://bugzilla.redhat.com/show_bug.cgi?id=1398427

I agree.
Comment 4 James W. Mills 2016-12-12 17:47:51 UTC 

*** This bug has been marked as a duplicate of bug 1398427 ***
Note You need to log in before you can comment on or make changes to this bug.