Should not use an IPNetwork when assigning floating IPs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
John Tran |
Bug Description
Using the iter_hosts() method of an IPNetwork in nova-manage.
>>> help(netaddr.
...
- for IPv4, the network and broadcast adresses are always excluded. Any subnet that contains less than 4 IP addresses yields an empty list
For most users, this isn't a problem because usually IP addresses are over-provisioned, but it can lead to a very annoying bug where 'nova-manage floating create 192.168.0.2' works, but 'nova-manage floating create 192.168.0.2/32' and 'nova-manage floating create 192.168.0.2/31' both fail to affect nova's floating_ips table at all.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: low-hanging-fruit |
tags: | removed: low-hanging-fruit |
Changed in nova: | |
milestone: | none → folsom-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-3 → 2012.2 |
Fix proposed to branch: master /review. openstack. org/9181
Review: https:/