Kuryr should not give allocation_pools in the request to Neutron
Bug #1503183 reported by
Taku Fukushima
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kuryr |
Fix Committed
|
Undecided
|
Taku Fukushima | ||
Bug Description
Kuryr is filling the "allocation_pools" as None and make a request against Neutron. However, this field should be just left out as None gives you the validation error.
| Changed in kuryr: | |
| assignee: | nobody → Taku Fukushima (tfukushima) |
| Changed in kuryr: | |
| status: | New → In Progress |
| summary: |
- Kuryr should not give allocation_poosl in the request to Neutron + Kuryr should not give allocation_pools in the request to Neutron |
| description: | updated |
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 ea0221140202421
Author: Taku Fukushima <email address hidden>
Date: Tue Oct 6 17:58:33 2015 +0900
Remove allocation_pools in the subnet request against Neutron
This patch removes the allocation_pools from the request for the subnet
creation, which is not supposed to contain that field for allocating all
IP addresses. allocation_pools with null leads the validation error and
this causes the failures of the endpoint creation.
Change-Id: I3ef43ed32a65cc
Signed-off-by: Taku Fukushima <email address hidden>
Closes-Bug: #1503183