Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1260202

Summary:	Update selinux policies to allow new openvswitch ports
Product:	Red Hat OpenStack	Reporter:	Flavio Leitner <fleitner>
Component:	openstack-selinux	Assignee:	Ryan Hallisey <rhallise>
Status:	CLOSED ERRATA	QA Contact:	yeylon <yeylon>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.0 (Kilo)	CC:	dnavale, jschluet, lhh, mgrepl, rhallise, sasha, srevivo, yeylon
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-selinux-0.6.42-2.el7ost	Doc Type:	Bug Fix
Doc Text:	With this update, OpenvSwitch changed from using port 6633 to 6653. SELinux expects OpenvSwitch to use port 6633 causing OVS to fail when running. To fix the issue, you need to tell SELinux that OVS is running on port 6653 instead of 6633.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-21 17:04:30 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:

Description Flavio Leitner 2015-09-04 17:56:16 UTC

Description of problem:

Since 2.4.0, the OVS has changed to use IANA ports so the selinux policies need to be updated. See the upstream commit below:
https://github.com/openvswitch/ovs/commit/d4763d1d4efbbcfd884df2d668980d61ec89d75a

OSP openvswitch is going to be updated to 2.4.0 soon.

fbl

Comment 4 Flavio Leitner 2015-11-09 16:35:16 UTC

Ryan,

Is there anything missing here?
Let me know if I can help somehow.

Thanks,
fbl

Comment 5 Ryan Hallisey 2015-11-09 18:38:52 UTC

All set. Lost this in a pile of emails.

Comment 7 Lon Hohberger 2015-12-01 15:25:55 UTC

Verified: no port issues during automation runs.

Comment 10 errata-xmlrpc 2015-12-21 17:04:30 UTC

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-2015:2676