Mentioned Bug
https://bugs.launchpad.net/neutron/+bug/1494281
contains :-
Fix merged to neutron (stable/liberty)
Reviewed:
https://review.openstack.org/238485
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=10e07503524cc...
Submitter: Jenkins
Branch: stable/liberty
commit 10e07503524cc244d5c8f1f285db4a4f06dd12e7
Author: Thomas Herve <email address hidden>
Date: Tue Oct 20 15:42:59 2015 +0200
Properly handle segmentation_id in OVS agent
The segmentation_id of a OVS VLAN can be None, but a recent change
assumed that it was always an integer. It highlighted the fact that we
try to store None in the OVS database, which got stored as a string.
This fixes the storage, and handles loading the value while keeping
compatibility.
Change-Id: I6e7df1406c90ddde254467bb87ff1507a4caaadd
Closes-Bug: #1494281
(cherry picked from commit 51f6b2e1c9c2f5f5106b9ae8316e57750f09d7c9)
Looking at build
http://cbs.centos.org/koji/buildinfo?buildID=7850
I was unable to find patch
https://git.openstack.org/cgit/openstack/neutron/patch/?id=10e07503524cc2...
I could be wrong and just failed to find patch, otherwise RDO Liberty (stable Release
),
having openstack-neutron-7.0.0-2.el7, has still problem originally described in
upstream record,
i.e. external flat network provider won't work as expected due to original
version of
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py, packed into RDO
Liberty
until now.
Thank you.
Boris
Yes, RDO Liberty is affected (Delorean Liberty is not).
Please RDO folks advice: should we backport the patch or wait till rebase?
Ihar