nova-manage floating delete fails using --ip_range

Bug #932070 reported by Lorin Hochstein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Russell Bryant

Bug Description

Version: Diablo (2011.3.1)

I accidentally created the wrong list of floating IPs using --ip_range. I tried to delete it using --ip_range and got an error.

To reproduce:

FLOATING_RANGE="192.168.20.1/24"
nova-manage floating create --ip_range=$FLOATING_RANGE
nova-manage floating delete --ip_range=$FLOATING_RANGE

Error in nova-manage.log:

2012-02-14 08:53:41,478 CRITICAL nova [3fc850b8-82eb-48fb-a7b6-4bc728ac45c2 None None] Floating ip not found for address 192.168.20.0.
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/usr/bin/nova-manage", line 2149, in <module>
(nova): TRACE: main()
(nova): TRACE: File "/usr/bin/nova-manage", line 2137, in main
(nova): TRACE: fn(*fn_args, **fn_kwargs)
(nova): TRACE: File "/usr/bin/nova-manage", line 702, in delete
(nova): TRACE: str(address))
(nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/api.py", line 252, in floating_ip_destroy
(nova): TRACE: return IMPL.floating_ip_destroy(context, address)
(nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 119, in wrapper
(nova): TRACE: return f(*args, **kwargs)
(nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 566, in floating_ip_destroy
(nova): TRACE: session=session)
(nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 119, in wrapper
(nova): TRACE: return f(*args, **kwargs)
(nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 649, in floating_ip_get_by_address
(nova): TRACE: raise exception.FloatingIpNotFoundForAddress(address=address)
(nova): TRACE: FloatingIpNotFoundForAddress: Floating ip not found for address 192.168.20.0.
(nova): TRACE:

Revision history for this message
Russell Bryant (russellb) wrote :

This was fixed in master by this commit:

commit 9e21a2228c191896223daae2379fcf1352cc736c
Author: Dean Troyer <email address hidden>
Date: Tue Jan 10 15:18:07 2012 -0600

    nova-manage floating ip fixes

    * Add pool, interface to 'floating list' output
      These columns were added to the floating_ips table in
      https://review.openstack.org/2892 and are not visible elsewhere
    * Fix 'floating delete' to skip network/broadcast addresses
      Makes the delete command match the create command behaviour
      introduced in https://review.openstack.org/2663
    * Address changes listed in bug 817281
      Change host column in output to project ID, change hostname
      column to uuid

    Change-Id: Ibbfbe9ed5543927a6b2a1e676f5617901a32f897

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/diablo)

Fix proposed to branch: stable/diablo
Review: https://review.openstack.org/4217

Revision history for this message
Russell Bryant (russellb) wrote :

I marked this as "fix released" for essex, but also nominated the bug for the diablo series.

Changed in nova:
status: New → Fix Released
assignee: nobody → Russell Bryant (russellb)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/diablo)

Reviewed: https://review.openstack.org/4217
Committed: http://github.com/openstack/nova/commit/ff30847e50a7924f0ccb5be699643c02f689fea4
Submitter: Jenkins
Branch: stable/diablo

commit ff30847e50a7924f0ccb5be699643c02f689fea4
Author: Russell Bryant <email address hidden>
Date: Wed Feb 15 17:40:36 2012 -0500

    Fix nova-manage floating delete with --ip_range.

    This patch fixes an error when trying to delete a range of floating IPs
    as reported in bug 932070.

    This was fixed in master as a part of:
     9e21a2228c191896223daae2379fcf1352cc736c

    Change-Id: I165e59a258d728c222cfea0406d4bc78cfab669c

tags: added: in-stable-diablo
Sean Dague (sdague)
no longer affects: nova/diablo
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.