← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1593793] Re: [RFE] No notification on floating ip status change

 

Bug closed due to lack of activity, please feel free to reopen if
needed.

** Changed in: neutron
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1593793

Title:
  [RFE] No notification on floating ip status change

Status in neutron:
  Won't Fix
Status in OpenStack Searchlight:
  New

Bug description:
  Tested on neutron/master in devstack.

  When I associate or disassociate a floating IP I get a notification
  indicating the new fixed IP and port association, but the status still
  indicates the current value (so for associate, the notification
  contains "fixed_ip_address":"a.b.c.d", "status": "DOWN") because
  there's a short latency time before the FIP is marked as ACTIVE.

  I see the status change after a very short period after in the q-svc
  log:

      New status for floating IP 8470e622-0f3b-419f-ac21-deed658d3260:
  ACTIVE

  There's no notification emitted representing this state change,
  however. The same is true on disassociate; the port and fixed IP are
  cleared but the status is indicated ACTIVE and there's no notification
  marking it DOWN.

  E.g.
  $ neutron floatingip-create 0e97853d-3ac0-4c08-a8b3-f6bfa443dd24

  {"event_type": "floatingip.create.end", "payload": {"floatingip":
  {"router_id": null, "status": "DOWN", "description": "", "tenant_id":
  "c1b853bf78bc43c69daa8d42cb9fb07f", "floating_network_id":
  "0e97853d-3ac0-4c08-a8b3-f6bfa443dd24", "fixed_ip_address": null,
  "floating_ip_address": "172.25.0.11", "port_id": null, "id":
  "6442165e-4caa-437c-9377-196f4db638f9"}}, "publisher_id":
  "network.devstack", "ctxt": {...}, "metadata": {"timestamp":
  "2016-06-17 16:44:20.600943", "message_id":
  "547b0f34-1bc0-4fbc-8e58-a0c2d2dc1751"}}

  $ neutron floatingip-associate 6442165e-4caa-437c-9377-196f4db638f9
  8068c884-1ab4-42d9-97d0-f65848fca2b0

  {"event_type": "floatingip.update.end", "payload": {"floatingip":
  {"router_id": "390ab366-0eee-46e9-a07f-f49cf0b31652", "status":
  "DOWN", "description": "", "tenant_id":
  "c1b853bf78bc43c69daa8d42cb9fb07f", "floating_network_id":
  "0e97853d-3ac0-4c08-a8b3-f6bfa443dd24", "fixed_ip_address":
  "172.40.0.4", "floating_ip_address": "172.25.0.11", "port_id":
  "8068c884-1ab4-42d9-97d0-f65848fca2b0", "id":
  "6442165e-4caa-437c-9377-196f4db638f9"}}, "publisher_id":
  "network.devstack", "ctxt": {...}, "metadata": {"timestamp":
  "2016-06-17 16:44:50.149631", "message_id":
  "f6f7ec1f-6363-49b0-b10f-84fd81e0a506"}}

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



References