FIXED_RANGE_V6 not set to sane value in neutron_plugins/services/l3
Bug #1643055 reported by
Jay Faulkner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Clark Boylan |
Bug Description
The awk statement here: https:/
2016-11-18 19:40:58.306 | +++ lib/neutron_
This is a bad request, as 64 is not a valid IPv6 subnet. Fix will be to fix the awk statement linked.
Changed in devstack: | |
assignee: | nobody → Clark Boylan (cboylan) |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/399762 /git.openstack. org/cgit/ openstack- dev/devstack/ commit/ ?id=a5afa7d81ad 380eeb91f7c58dd 07facb214b347b
Committed: https:/
Submitter: Jenkins
Branch: master
commit a5afa7d81ad380e eb91f7c58dd07fa cb214b347b
Author: Clark Boylan <email address hidden>
Date: Fri Nov 18 12:32:19 2016 -0800
Fix default ipv6 fixed range var
The intent was to make any ipv6 safe addr range bigger than a /64 a /64
when setting the fixed range. Unfortunately the awk only emited the mask
and not the addr. Fix this by sprinkling the address back in.
Fixes-Bug: 1643055 ecb3c77afcbb056 aa95090c409
Change-Id: I526d4c748fd404