Kuryr deletes the default subnets
Bug #1497994 reported by
Taku Fukushima
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kuryr |
Fix Committed
|
Undecided
|
Taku Fukushima | ||
Bug Description
Kuryr deletes the default subnets when the libnetwork endpoint to be deleted is associated with the default subnets. The default subnets are created with the default subnets specified in the config file and it's a better design not to delete them for the reuse in the near future.
| Changed in kuryr: | |
| assignee: | nobody → Taku Fukushima (tfukushima) |
| Changed in kuryr: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to kuryr (master) | #1 |
| Changed in kuryr: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit c115e5a93234cd9
Author: Taku Fukushima <email address hidden>
Date: Mon Sep 21 13:25:58 2015 +0900
Modify Kuryr not to delete the default subnets
This patch fixes the bug that Kuryr deletes the default subnets
associated with the subnet pools for Kuryr specified in the config
file.
By default Kuryr creates the default subnets with the subnet pools. When
users delete the Docker endpoint, Kuryr deleted the default subnets.
However, the default subnets are used when users don't specify the CIDRs
for interfaces when they create Docker endpoints, so it's a better design
not to delete them.
Change-Id: I0b26895cba7003
Signed-off-by: Taku Fukushima <email address hidden>
Closes-Bug: #1497994