Bug 959954

Summary:	realmd starts with init_t context after "systemctl restart realmd"
Product:	[Fedora] Fedora	Reporter:	Patrik Kis <pkis>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	dominick.grift, dspurek, dwalsh, mgrepl, mmalik, stefw
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	selinux-policy-3.12.1-47.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-30 03:33:14 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:	959458

Description Patrik Kis 2013-05-06 09:54:40 UTC

Description of problem:
relamd starts with init_t context after "systemctl restart realmd"

Version-Release number of selected component (if applicable):
realmd-0.13.91-1.fc19
selinux-policy-targeted-3.12.1-40.fc19
selinux-policy-3.12.1-40.fc19

How reproducible:
always

Steps to Reproduce:
# ps -efZ |grep realmd |grep -v grep
system_u:system_r:realmd_t:s0-s0:c0.c1023 root 2766 1  0 11:52 ?       00:00:00 /usr/lib64/realmd/realmd
#
# systemctl restart realmd
#
# ps -efZ |grep realmd |grep -v grep
system_u:system_r:init_t:s0     root      2781     1  0 11:52 ?        00:00:00 /usr/lib64/realmd/realmd
#

Comment 1 Patrik Kis 2013-05-06 09:56:35 UTC

workaround:
# killall realmd

Comment 2 Miroslav Grepl 2013-05-06 10:41:29 UTC

Ok, this is a new problem.

commit b2809a7b183422396cbcd71152fc0b7236405a29
Author: Miroslav Grepl <mgrepl>
Date:   Mon May 6 12:41:13 2013 +0200

    realmd can be started by systemctl now

Comment 3 Patrik Kis 2013-05-07 07:17:47 UTC

(In reply to comment #2)
> Ok, this is a new problem.
> 
> commit b2809a7b183422396cbcd71152fc0b7236405a29
> Author: Miroslav Grepl <mgrepl>
> Date:   Mon May 6 12:41:13 2013 +0200
> 
>     realmd can be started by systemctl now

I'm just wondering if this could be released today, so we have a fix before the test day (09/05/2013)

Comment 4 Patrik Kis 2013-05-07 07:32:07 UTC

(In reply to comment #3)
> (In reply to comment #2)
> > Ok, this is a new problem.
> > 
> > commit b2809a7b183422396cbcd71152fc0b7236405a29
> > Author: Miroslav Grepl <mgrepl>
> > Date:   Mon May 6 12:41:13 2013 +0200
> > 
> >     realmd can be started by systemctl now
> 
> I'm just wondering if this could be released today, so we have a fix before
> the test day (09/05/2013)

Ok, I did not realized that this was already released:
selinux-policy-3.12.1-42.fc19
selinux-policy-targeted-3.12.1-42.fc19

The bug seems to be fixed.

system_u:system_r:realmd_t:s0-s0:c0.c1023 root 10481 1  0 09:29 ?      00:00:00 /usr/lib64/realmd/realmd

after systemctl restart realmd

Comment 5 Fedora Update System 2013-05-29 14:19:17 UTC

selinux-policy-3.12.1-47.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-47.fc19

Comment 6 Fedora Update System 2013-05-29 17:46:00 UTC

Package selinux-policy-3.12.1-47.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-47.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9565/selinux-policy-3.12.1-47.fc19
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-05-30 03:33:14 UTC

selinux-policy-3.12.1-47.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.