yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

The nova-manage floating IP commands are more or less deprecated, people
should be using python-novaclient instead (or python-openstackclient if
it has support for server floating IP commands).  I don't think this is
probably worth spending time on.

** Tags added: nova-manage

** Changed in: nova
       Status: Confirmed => Opinion

** Changed in: nova
       Status: Opinion => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1369955

Title:
  Double delete a floating ip range using nova-manage command does not
  return not found error

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  I performed following steps -

  1. Create a single floating IP (it may in CIDR format also)
      root@mc1:/home/ubuntu# nova-manage  floating create --pool test-nova --ip_range 68.99.26.170

  2. List floating IPs
      root@mc1:/home/ubuntu# nova-manage floating list
      None    68.99.26.170    None    test-nova       eth0

  3. Delete create IP (or IP pool)
      root@mc1:/home/ubuntu# nova-manage floating delete 68.99.26.170
      2014-09-16 17:43:22.961 15567 WARNING nova.db.sqlalchemy.api [req-85523a81-b6ce-4cfd-b474-fdd3a93f70f9 None None] Change will make usage less than 0 for the following resources:         ['floating_ips']

  4. Check deletion in list -
      root@mc1:/home/ubuntu# nova-manage floating list
      No floating IP addresses have been defined.

  5. Again delete deleted floating IP (or Pool)
      root@mc1:/home/ubuntu# nova-manage floating delete 68.99.26.170
      <here command is successful>
      root@mc1:/home/ubuntu#

  In my opinion at step5 there should be some checks (if not
  implemented) or it should return an Error saying request IP range does
  not exist. (As it is already deleted)

  
  But in this case step 5 is successful without any error message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1369955/+subscriptions