yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #83216
[Bug 1886426] [NEW] Neutron sending response to rabbitmq exchange with event type "floatingip.update.end" without updating the status of Floating IP
Public bug reported:
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
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1886426
Title:
Neutron sending response to rabbitmq exchange with event type
"floatingip.update.end" without updating the status of Floating IP
Status in neutron:
New
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1886426/+subscriptions
Follow ups