Neutron sending response to rabbitmq exchange with event type "floatingip.update.end" without updating the status of Floating IP
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Neutron is sending response asynchronously, means that it sends the response to rabbitmq without completing the request and that's why it didn't return the updated response. It is not doing this with only attaching and detaching of Floating IP but it is also sending response of floating creation without the ID of floating IP which is also incomplete.
Example (Responses)
1) Creation of Elastic IP (Response)
"event_type": "floatingip.
"payload": {"floatingip": {"router_id": null, "status": "DOWN", "description": "", "tags": [], "updated_at": "2020-07-
As you can see that there is no floatingip_id in the payload.
2) Attaching FloatingIP with Instance
"event_type": "floatingip.
"payload": {"floatingip": {"router_id": "cef1958e-
In the payload you can see that the status of floatingIP remains in the DOWN state even after attaching the floatingIP to Instance

I have a lot of question on this bug, hopefully you can answer them.
1) What release of neutron is this?
2) Where are you capturing these messages? Is it on the neutron-server side right as it's sending to the l3-agent? Do you have the return message?
3) What status is actually reflected in the DB? i.e. output from 'openstack floating ip show $ID'
4) Can you list the commands you're running so I can verify the failure?