Bug 1193483 – SELinux updates are not effective due to packaging issue

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1193483 - SELinux updates are not effective due to packaging issue

Summary:	SELinux updates are not effective due to packaging issue

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	SELinux (Show other bugs)
Sub Component:
Version:	6.0.8
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Lukas Zapletal
QA Contact:	Katello QA List
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-02-17 07:53 EST by Lukas Zapletal
Modified:	2015-08-04 10:57 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-06-30 12:47:58 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:1592	normal	SHIPPED_LIVE	Important: Red Hat Satellite 6.1.1 on RHEL 6	2015-08-12 05:04:35 EDT

Groups: None (edit)

Description Lukas Zapletal 2015-02-17 07:53:40 EST

When you upgrade foreman-selinux package, new policy is not being reloaded automatically.

Workaround is to reboot the server or to reload the policy:

[root@s6 ~]# semodule -l | grep foreman
foreman 1.6.0.5
[root@s6 ~]# foreman-selinux-enable
[root@s6 ~]# semodule -l | grep foreman
foreman 1.6.0.14.1

Comment 11 Bryan Kearney 2015-06-30 12:47:58 EDT

This bug is resolved in the Satellite 6.1 code base in bug. We are not planning to backport this to 6.0, and are therefore closing out this bug. Please feel free to contact bkearney@redhat.com and dcaplan@redhat.com with any issues.

Note You need to log in before you can comment on or make changes to this bug.