Activity log for bug #1593793

Date Who What changed Old value New value Message
2016-06-17 16:47:15 Steve McLellan bug added bug
2016-06-17 16:47:45 Steve McLellan 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 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"}} 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"}}
2016-06-20 10:01:59 John Davidge neutron: status New Triaged
2016-06-20 10:02:06 John Davidge neutron: importance Undecided Wishlist
2016-06-20 12:17:36 Boden R neutron: assignee Boden R (boden)
2016-06-20 14:32:51 John Davidge summary No notification on floating ip status change [RFE] No notification on floating ip status change
2016-06-20 14:33:01 John Davidge tags rfe
2016-06-22 00:04:34 Travis Tripp bug task added searchlight
2016-06-30 21:57:30 Armando Migliaccio tags rfe
2016-07-20 20:45:31 Boden R neutron: status Triaged In Progress
2016-07-20 20:45:49 Boden R summary [RFE] No notification on floating ip status change No notification on floating ip status change
2016-07-21 15:29:30 Boden R summary No notification on floating ip status change [RFE] No notification on floating ip status change
2016-09-10 15:59:18 Armando Migliaccio neutron: milestone ocata-1
2016-09-16 19:13:35 Steve McLellan searchlight: importance Undecided High
2016-11-16 22:43:33 Armando Migliaccio neutron: milestone ocata-1 ocata-2
2017-01-06 16:04:31 Armando Migliaccio neutron: milestone ocata-2 ocata-3
2017-01-26 23:41:30 Armando Migliaccio neutron: milestone ocata-3 ocata-rc1
2017-02-07 18:15:42 Armando Migliaccio neutron: milestone ocata-rc1 ocata-rc2
2017-02-08 18:12:40 Armando Migliaccio neutron: milestone ocata-rc2 pike-1
2017-02-21 16:31:16 Armando Migliaccio tags rfe
2017-02-21 16:31:22 Armando Migliaccio tags rfe
2017-05-18 01:20:29 Armando Migliaccio neutron: milestone pike-1 pike-2
2018-07-20 01:49:35 Vladimir Astafiev bug added subscriber Vladimir Astafiev
2022-10-19 11:27:07 Rodolfo Alonso neutron: status In Progress Won't Fix