Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1431516 - Support for OVS2.6 Security groups with OSP
Support for OVS2.6 Security groups with OSP
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-odl (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
medium Severity medium
: Upstream M2
: 12.0 (Pike)
Assigned To: Yariv
Yariv
: FutureFeature, TestOnly, Triaged
Depends On:
Blocks: 1442136 1431513 1469731
  Show dependency treegraph
 
Reported: 2017-03-12 23:18 EDT by atelang
Modified: 2018-02-05 14:04 EST (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 16:13:42 EST
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description atelang 2017-03-12 23:18:39 EDT
Description of problem: OVS2.6 Security groups support with OSP
Stateless and stateful security groups requires neutron new implementation based on OpenFlow rules only, and requires the conntrack support of OVS. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 10 Ziv 2017-10-25 08:30:08 EDT
Has been verified.

Thanks,
Ziv
Comment 13 errata-xmlrpc 2017-12-13 16:13:42 EST
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/RHEA-2017:3462

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