| 2016-12-20 03:23:57 |
Dongcan Ye |
description |
Problem:
when user use existed neutron network, kuryr-libnetwork will not delete the neutron port which is created for containers.
Reproduct Steps:
1. create neutron network
2. create kuryr network with this existed neutron network.
3. run a container, and delete the container.
Expect Result:
the neutron port which created from container is deleted after the container is deleted.
Actual Result:
the neutron port did not delete.
When ipamdriver release address, it will find the subnet according to poolid. This will assume the subnet need has subnetpool-id.When "existed neutron network" case, the network and subnet is pre-created by EndUser, which do not have subnetpool-id. and subnetpool-id is unchangable after the subnet is created. This will cause kuryr can't release the neutron port. |
Problem:
when user use existed neutron network, kuryr-libnetwork will not delete the neutron port which is created for containers.
Reproduce Steps:
1. create neutron network and subnet
2. create kuryr network with this existed neutron network.
3. run a container, and delete the container.
Expect Result:
the neutron port which created from container is deleted after the container is deleted.
Actual Result:
the neutron port did not delete.
When ipamdriver release address, it will find the subnet according to poolid. This will assume the subnet need has subnetpool-id. When "existed neutron network" case, the network and subnet is pre-created by EndUser, which do not have subnetpool-id. and subnetpool-id is unchangable after the subnet is created. This will cause kuryr can't release the neutron port. |
|
