Neutron sending response to rabbitmq exchange with event type "floatingip.update.end" without updating the status of Floating IP

Bug #1886426 reported by Syed Haris
8
This bug affects 1 person
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.create.end"

"payload": {"floatingip": {"router_id": null, "status": "DOWN", "description": "", "tags": [], "updated_at": "2020-07-06T13:07:27Z", "dns_domain": "", "floating_network_id": "1af114c6-454b-4442-90a2-b8d825d6ca85", "fixed_ip_address": null, "floating_ip_address": "10.81.1.205", "revision_number": 0, "port_id": null, "id": "21442c9a-4a63-4008-aef4-d95ea3a78d78", "tenant_id": "fc5bf4b73fd2486f99cd596f429155be", "created_at": "2020-07-06T13:07:27Z", "dns_name": "", "project_id": "fc5bf4b73fd2486f99cd596f429155be"}}

As you can see that there is no floatingip_id in the payload.

2) Attaching FloatingIP with Instance

"event_type": "floatingip.update.end"

"payload": {"floatingip": {"router_id": "cef1958e-9017-4d80-bc62-d4a7cb380b30", "status": "DOWN", "description": "", "tags": [], "updated_at": "2020-07-06T13:11:07Z", "dns_domain": "", "floating_network_id": "1af114c6-454b-4442-90a2-b8d825d6ca85", "fixed_ip_address": "199.1.1.52", "floating_ip_address": "10.81.1.209", "revision_number": 17, "port_id": "a48797e9-db22-4521-8100-5d62650cf89e", "id": "14824885-2506-4eed-b68e-6a386a4f9fd2", "dns_name": "", "created_at": "2020-07-06T06:51:54Z", "tenant_id": "fc5bf4b73fd2486f99cd596f429155be", "project_id": "fc5bf4b73fd2486f99cd596f429155be"}}

In the payload you can see that the status of floatingIP remains in the DOWN state even after attaching the floatingIP to Instance

Revision history for this message
Brian Haley (brian-haley) wrote :

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?

Changed in neutron:
status: New → Incomplete
Revision history for this message
Syed Haris (syed-haris-hafeez) wrote :

Dear Brian,

Thanks for your response and following are the answers of your questions

1) Neutron Release
python2-neutronclient-6.12.1-0.20200228162015.450039b.el7.noarch
puppet-neutron-14.4.1-0.20200404011627.4aae155.el7.noarch
python2-neutron-lib-1.25.1-0.20200313055037.3dcc921.el7.noarch

2) We are checking notifications.info queue where neutron sends events notifications.
3) The attached message is from oslo event end notification when attaching or detaching Floating IP.
4) When we attach floating IP to instance
5) Oslo notification should give status active rather "down" status

Revision history for this message
Brian Haley (brian-haley) wrote :
Download full text (10.3 KiB)

Syed, I can't reproduce the issue.

I created a floating ip for my project, it's DOWN since it's not associated:

$ openstack floating ip show 2505936c-8ffc-413d-8665-c105aa0cb722
+---------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+---------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+
| created_at | 2020-07-15T16:46:58Z |
| description | |
| dns_domain | None |
| dns_name | None |
| fixed_ip_address | None |
| floating_ip_address | 172.24.4.147 |
| floating_network_id | 74d94ccb-374d-4428-84a9-4a11f14611fe |
| id | 2505936c-8ffc-413d-8665-c105aa0cb722 |
| location | cloud='', project.domain_id='default', project.domain_name=, project.id='48f6deee945143cf93e870dd18fdf83b', project.name='demo', region_name='RegionOne', zone= |
| name | 172.24.4.147 |
| port_details | None |
| port_id | None |
| project_id | 48f6deee945143cf93e870dd18fdf83b |
| qos_policy_id | None ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.