Bug 1266050

Summary: [RFE] [Neutron] [OVS] Update OVS version with RHEL OSP 8.0
Product: Red Hat OpenStack Reporter: Nir Yechiel <nyechiel>
Component: openvswitchAssignee: Nir Yechiel <nyechiel>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: apevec, chrisw, ddomingo, fleitner, jschluet, kzhang, mschuppe, nyechiel, ohochman, rhos-maint, rkhan, yeylon
Target Milestone: betaKeywords: FutureFeature
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvswitch-2.4.0-1.el7 Doc Type: Release Note
Doc Text:
The Open vSwitch (openvswitch) package is now re-based to upstream version 2.4.0.
Story Points: ---
Clone Of:
: 1267017 (view as bug list) Environment:
Last Closed: 2016-04-07 21:09:00 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:
Bug Depends On:    
Bug Blocks: 1271974    

Comment 9 Toni Freger 2015-12-21 11:08:57 UTC
Itzik, please run Tempest on osp-8 env ( there are failures in automation team so please run it by yourself)

We would like to check the we don't have regression with new openvswitch package - openvswitch-2.4.0-1.el7.src.rpm   

Please run all available upstream tests - 

Network Basic Ops - https://github.com/openstack/tempest/blob/master/tempest/scenario/test_network_basic_ops.py 
Network Advanced Server Ops - https://github.com/openstack/tempest/blob/master/tempest/scenario/test_network_advanced_server_ops.py 
Network IPV6 - https://github.com/openstack/tempest/blob/master/tempest/scenario/test_network_v6.py 
Security group cross tenant -https://github.com/openstack/tempest/blob/master/tempest/scenario/test_security_groups_basic_ops.py

Comment 10 Itzik Brown 2015-12-23 13:11:39 UTC
Ran the requested tests.

Comment 15 errata-xmlrpc 2016-04-07 21:09:00 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://rhn.redhat.com/errata/RHEA-2016-0603.html