]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Properly handle segmentation_id in OVS agent
authorThomas Herve <therve@redhat.com>
Tue, 20 Oct 2015 13:42:59 +0000 (15:42 +0200)
committerThomas Herve <therve@redhat.com>
Tue, 20 Oct 2015 15:36:39 +0000 (17:36 +0200)
commit51f6b2e1c9c2f5f5106b9ae8316e57750f09d7c9
treeedc9ecb73ea7955b8f9af1231218af6d33ba2a23
parent948316190dd445ec387b391cd89b87c19d19b91b
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
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py
neutron/tests/unit/plugins/ml2/drivers/openvswitch/agent/test_ovs_neutron_agent.py