Small fix to handle the fact that ovsdb sometimes returns ofport of -1
authorEd Warnicke <eaw@cisco.com>
Mon, 6 Apr 2015 16:30:41 +0000 (09:30 -0700)
committerEd Warnicke <eaw@cisco.com>
Mon, 6 Apr 2015 17:19:13 +0000 (10:19 -0700)
commite9443b123419e30776cd40fca5a934a383612375
tree0fce675dd5b1ee1ee39382375c1f62df047aa622
parentfc11e90d023b05d6d3c7f1640b27c95798a68b1b
Small fix to handle the fact that ovsdb sometimes returns ofport of -1

It turns out that sometimes ovsdb returns an ofport of -1 to indicate that
there is no associated ofport value.  We should represent that by *not*
having an ofport value

Change-Id: I2a28a34333ff1b92728286672499714079346444
Signed-off-by: Ed Warnicke <eaw@cisco.com>