yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1444966 ***
    https://bugs.launchpad.net/bugs/1444966

Because we have deprecated this API, I have marked it as will not fix.

** Changed in: nova
       Status: In Progress => 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/1525101

Title:
  floating ip info is not updated correctly when remove a fix ip which
  is associated to a floating ip

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

Bug description:
  [Summary]
  floating ip info is not updated correctly when remove a fix ip which is associated to a floating ip

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  floating ip info can be updated correctly when remove a fix ip which is associated to a floating ip.

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) launch 1 instance:
  root@45-59:/opt/stack/devstack# nova list
  +--------------------------------------+------+--------+------------+-------------+---------------+
  | ID                                   | Name | Status | Task State | Power State | Networks      |
  +--------------------------------------+------+--------+------------+-------------+---------------+
  | 4608feb6-c825-46ae-8dcf-3d8839e51865 | inst | ACTIVE | -          | Running     | net2=2.0.0.30 |
  +--------------------------------------+------+--------+------------+-------------+---------------+

  2) associate a floating ip to it:
  root@45-59:/opt/stack/devstack# nova floating-ip-associate --fixed-address 2.0.0.30 inst 172.168.0.10
  root@45-59:/opt/stack/devstack# nova list
  +--------------------------------------+------+--------+------------+-------------+-----------------------------+
  | ID                                   | Name | Status | Task State | Power State | Networks                    |
  +--------------------------------------+------+--------+------------+-------------+-----------------------------+
  | 4608feb6-c825-46ae-8dcf-3d8839e51865 | inst | ACTIVE | -          | Running     | net2=2.0.0.30, 172.168.0.10 |
  +--------------------------------------+------+--------+------------+-------------+-----------------------------+

  3)remove the fix ip of the instance, the fix ip and floating ip info can be removed when show "nova list":
  root@45-59:/opt/stack/devstack# nova remove-fixed-ip inst 2.0.0.30
  root@45-59:/opt/stack/devstack# nova list
  +--------------------------------------+------+--------+------------+-------------+----------+
  | ID                                   | Name | Status | Task State | Power State | Networks |
  +--------------------------------------+------+--------+------------+-------------+----------+
  | 4608feb6-c825-46ae-8dcf-3d8839e51865 | inst | ACTIVE | -          | Running     |          |
  +--------------------------------------+------+--------+------------+-------------+----------+

  4) but if show the floating ip info via below cmd, the fix ip info still exist:  >>>>ISSUE
  root@45-59:/opt/stack/devstack# neutron floatingip-show  46af70eb-e62b-471c-8694-0dc14060c372
  +---------------------+--------------------------------------+
  | Field               | Value                                |
  +---------------------+--------------------------------------+
  | fixed_ip_address    | 2.0.0.30    >>>>ISSUE                |
  | floating_ip_address | 172.168.0.10                         |
  | floating_network_id | c2592b59-f621-479c-8eaf-9b23f41c64d4 |
  | id                  | 46af70eb-e62b-471c-8694-0dc14060c372 |
  | port_id             | 8c57f3ea-7cbf-4ad6-98d9-8c7a0d743bbb |
  | router_id           | 37b26f1a-6086-4d64-bf8d-bd2ba27e5fee |
  | status              | ACTIVE                               |
  | tenant_id           | f75256da799642e0ab597a7533918714     |
  +---------------------+--------------------------------------+
  root@45-59:/opt/stack/devstack#

  5)the issue results in another problem: the network info of the
  instance in dashboard is incorrect.

  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

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