Fix /NetworkDriver.CreateEndpoint to handle the empty Interfaces
The current /NetworkDriver.CreateEndpiont doesn't handle the case
libnetwork gives the empty Interfaces property in the request and it's
failed when it receives the request which has the empty Interfaces
property. However, with the libnetwork CLI in Docker 1.8.0 we can't
specify the Interfaces property and it's always empty.
This patch makes Kuryr put a new entry with the ID 0 if it receives the
empty interface dictionary in the requests. MacAddress and Address or
AddressIPv6 are filled by allocated ones.
Reviewed: https:/ /review. openstack. org/227961 /git.openstack. org/cgit/ openstack/ kuryr/commit/ ?id=c2a1464c91c d1fccb8d25e225b c7d86eaf3f4f2b
Committed: https:/
Submitter: Jenkins
Branch: master
commit c2a1464c91cd1fc cb8d25e225bc7d8 6eaf3f4f2b
Author: Taku Fukushima <email address hidden>
Date: Sat Sep 26 01:02:49 2015 +0900
Fix /NetworkDriver. CreateEndpoint to handle the empty Interfaces
The current /NetworkDriver. CreateEndpiont doesn't handle the case
libnetwork gives the empty Interfaces property in the request and it's
failed when it receives the request which has the empty Interfaces
property. However, with the libnetwork CLI in Docker 1.8.0 we can't
specify the Interfaces property and it's always empty.
This patch makes Kuryr put a new entry with the ID 0 if it receives the
empty interface dictionary in the requests. MacAddress and Address or
AddressIPv6 are filled by allocated ones.
Change-Id: I689d2f3aa8c5d0 47dbdcfee425910 951530fb621
Signed-off-by: Taku Fukushima <email address hidden>
Closes-Bug: #1499779