Bug 1260202 - Update selinux policies to allow new openvswitch ports
Summary: Update selinux policies to allow new openvswitch ports
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-selinux
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: z3
: 7.0 (Kilo)
Assignee: Ryan Hallisey
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-04 17:56 UTC by Flavio Leitner
Modified: 2016-04-18 07:12 UTC (History)
8 users (show)

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.
Clone Of:
Environment:
Last Closed: 2015-12-21 17:04:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2676 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 7 Bug Fix and Enhancement Advisory 2015-12-21 21:51:22 UTC

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
Note You need to log in before you can comment on or make changes to this bug.