nova-manage floating create strange behavior

Bug #1006881 reported by Vasyl Khomenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Triaged
Wishlist
Unassigned

Bug Description

Try
# nova-manage floating create --ip_range=10.10.10.10/32

no errors and nothing done

# nova-manage floating list
2012-05-31 08:54:26 DEBUG nova.utils [req-a6e1a118-eb5e-426c-9f04-ca0de543476b None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from (pid=11414) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658
None 10.0.0.1 None nova eth0
None 10.0.0.2 None nova eth0

Revision history for this message
Vish Ishaya (vishvananda) wrote :

if you give it a range, it will ignore the broadcast and network address. to add a single ip, remove the /32
nova-manage floating create --ip_range=10.10.10.10

perhaps a message is warranted.

Changed in nova:
status: New → Invalid
status: Invalid → Triaged
importance: Undecided → Wishlist
Revision history for this message
Vasyl Khomenko (vkhomenko) wrote :

I'm mostly talking about that there should be error if no action produced.
if i specify 10.10.10.0/30, i will get 4 floating ips, not 2 as it should be (with net and broadcast). Another bug?
In general - 10.10.10.10/32 should be treated as 10.10.10.10 i think.

Revision history for this message
Joel Friedly (joelfriedly) wrote :

This looks like a duplicate of https://bugs.launchpad.net/nova/+bug/1017682

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.