Turning on 'enable_dhcp' on subnet update cause request failure for pluggable IPAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Gary Kotton |
Bug Description
Bug reproducible only if pluggable IPAM is in effect.
Steps to reproduce:
1. Enable pluggable IPAM by setting ipam_driver to 'internal' (or another ipam driver).
2. Create Network.
3. Create Subnet with unchecked 'Enable DHCP' option.
4. Verify Subnet is created.
5. Edit Subnet and check 'Enable DHCP' option, press 'Save'
Observed error in UI:
"Error: Failed to update subnet "90.90.0.0/24": No more IP addresses available on network a9bb6abf-
Error in neutron log:
2015-11-10 12:07:09.656 DEBUG neutron.api.v2.base [req-c585fc85-
': u'90.90.0.2', u'end': u'90.90.0.254'}], u'host_routes': [], u'name': u'niny', u'enable_dhcp': True}} from (pid=29244) prepare_
2015-11-10 12:07:09.754 INFO neutron.
bf-98ec-
Root cause:
Query in _validate_subnet is not compatible with pluggable IPAM.
It directly queries tables for built-in IPAM.
range_qry = context.
https:/
Need to reword this validation to support pluggable IPAM.
Changed in neutron: | |
assignee: | nobody → Pavel Bondar (pasha117) |
tags: | added: l3-ipam-dhcp |
tags: | added: liberty-backport-potential |
description: | updated |
Changed in neutron: | |
status: | New → Confirmed |
Changed in neutron: | |
importance: | Medium → High |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
tags: | removed: liberty-backport-potential |
looping in Carl Baldwin to the bug.