This RFE is to track a request to update from OVS 2.7 in OSP 12 to OVS 2.9 in OSP 13. Upstream OVN 2.9 packaged in OVS 2.9 is developed in tandem with OpenStack Queens, both are supposed to release within a 2 week delay. This RFE intends to track an effort that ensures that downstream OSP/OVS have the same 1:1 relationship between OVS 2.9 and OSP 13 (based on Queens).
*** Bug 1468331 has been marked as a duplicate of this bug. ***
Official OVS 2.9 will be released around mid February 2018. We'll use this BZ to track the effort once it's released.
Will it be release in parallel with Queens RC? https://releases.openstack.org/queens/schedule.html
(In reply to Jon Schlueter from comment #6) > Will it be release in parallel with Queens RC? > > https://releases.openstack.org/queens/schedule.html Pretty much. That's challenging and something we've never done before. We've always consumed a version of OVS that was 6 months behind the equivalent version of OpenStack. Now, with OVN, I argue that OVN (currently delivered within OVS), OVS becomes an OpenStack component, just like openstack-nova. That is because OVN is developed during an OpenStack cycle, and according to the OpenStack release schedule. Releasing OSP 13 with the previous version of OVN (2.8), would be like release OSP 13 with Nova from OSP 12. What we're trying to do for this cycle is to consume OVS 2.9 with OSP 13. However, we won't have time to begin testing OVS 2.9 only after it's released, so we've set up a CI job that tests OSP with OVS from master. That way we hope to proactively deal with issues as they pop, so when OVS 2.9 is released, it'd already be tested and working.
*** Bug 1489045 has been marked as a duplicate of this bug. ***
Verifying this bug, all networking squads working with latest openvswitch 2.9 version
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-2018:2086