[RFE] No notification on floating ip status change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Searchlight |
New
|
High
|
Unassigned | ||
neutron |
Won't Fix
|
Wishlist
|
Boden R |
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_
I see the status change after a very short period after in the q-svc log:
New status for floating IP 8470e622-
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-
{"event_type": "floatingip.
$ neutron floatingip-
{"event_type": "floatingip.
description: | updated |
Changed in neutron: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in neutron: | |
assignee: | nobody → Boden R (boden) |
summary: |
- No notification on floating ip status change + [RFE] No notification on floating ip status change |
tags: | added: rfe |
Changed in neutron: | |
status: | Triaged → In Progress |
summary: |
- [RFE] No notification on floating ip status change + No notification on floating ip status change |
summary: |
- No notification on floating ip status change + [RFE] No notification on floating ip status change |
Changed in searchlight: | |
importance: | Undecided → High |
Changed in neutron: | |
milestone: | ocata-1 → ocata-2 |
Changed in neutron: | |
milestone: | ocata-2 → ocata-3 |
Changed in neutron: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in neutron: | |
milestone: | ocata-rc1 → ocata-rc2 |
Changed in neutron: | |
milestone: | ocata-rc2 → pike-1 |
tags: | added: rfe |
tags: | removed: rfe |
Changed in neutron: | |
milestone: | pike-1 → pike-2 |
I assume this one was discussed in the neutron meeting and decided it should be an RFE??
Adding notifications for FIP seemed pretty straight forward to me, and hence I was assuming it could move straight to tech discussions via patch reviews.