Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1300531 - selinux changes kill at command jobs
Summary: selinux changes kill at command jobs
Keywords:
Status: CLOSED DUPLICATE of bug 1298192
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 23
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-21 04:22 UTC by John Floyd
Modified: 2016-02-12 08:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-09 09:14:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description John Floyd 2016-01-21 04:22:49 UTC 
Description of problem:

at command stopped working due to selinux.  at command regularly used

Jobs were accepted and queued.  at job was activated but there was no output.  Jobs that should have taken a long time terminated immediately.  Simple jobs of "echo SOMETHING" also failed whether user or root activated with no output.

set selinux to permissive, problem disappeared.  Could not find the component that was causing it.  Checked all logs...

selinux-policy-3.13.1-158.fc23 installed

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

selinux-policy-3.13.1-158.fc23 installed

How reproducible:

Every time job was created.

Steps to Reproduce:
1.
2.
3.

Actual results:

no result

Expected results:

at least a mail message with errors


Additional info:
Comment 1 Petr Lautrbach 2016-01-21 07:11:18 UTC 
Does kernel update https://bodhi.fedoraproject.org/updates/FEDORA-2016-b59fd603be fix the problem? It seems to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1298192
Comment 2 John Floyd 2016-02-08 22:45:46 UTC 
I did not have the capability of checking the test kernel update.

However I can report that kernel-4.3.4 (installed today) solves the problem.
Comment 3 Miroslav Grepl 2016-02-12 08:55:53 UTC 

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