Bug 1624026 – upgraded foreman-selinux has no label for 2375/tcp

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

Bug 1624026 - upgraded foreman-selinux has no label for 2375/tcp

Summary:	upgraded foreman-selinux has no label for 2375/tcp

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	unspecified Severity high (vote)
Target Milestone:	6.3.4
Target Release:	Unused
Assigned To:	Lukas Zapletal
QA Contact:	jcallaha
Docs Contact:

URL:	http://projects.theforeman.org/issues...
Whiteboard:
Keywords:	Regression, Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-30 12:56 EDT by Mike McCune
Modified:	2018-10-11 11:18 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	foreman-selinux-1.15.6.3-1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1563766
Environment:
Last Closed:	2018-10-11 11:18:07 EDT
Type:	---
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
Foreman Issue Tracker	23127	None	None	None	2018-08-30 12:56 EDT
Red Hat Product Errata	RHBA-2018:2915	None	None	None	2018-10-11 11:18 EDT

Groups: None (edit)

Comment 4 Patrick Creech 2018-09-05 10:08:19 EDT

Lukas,

This failed cherrypick, can you take a look?

Comment 7 jcallaha 2018-09-12 13:51:05 EDT

Verified in Satellite 6.3.4 Snap 1

Upgrade from 6.3.4 to 6.3.4 as well as a base 6.3.4 install shows that the port is managed by foreman.

-bash-4.2# semanage port -l | grep foreman
foreman_container_port_t       tcp      2376, 2375

Comment 9 errata-xmlrpc 2018-10-11 11:18:07 EDT

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-2018:2915

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