This may happen when a node is deleted in parallel with calling
the port list API. Ports are fetched, then we try do fetch their
nodes and port groups. If either of them are removed in the meantime,
the API fails with HTTP 400. This change works around it.
Change-Id: Ie2d4c46c031ee86976abb6107433cdde87a4345a
Closes-Bug: #1748893
(cherry picked from commit 52dcc642d372e23fd59be44e0f9f5627fac5cec4)
Reviewed: https:/ /review. openstack. org/545892 /git.openstack. org/cgit/ openstack/ ironic/ commit/ ?id=ae956dcba8c afd7c3d0c07836f 83fdc70e5c5c86
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit ae956dcba8cafd7 c3d0c07836f83fd c70e5c5c86
Author: Dmitry Tantsur <email address hidden>
Date: Thu Feb 15 18:49:12 2018 +0100
Fix rare HTTP 400 from port list API
This may happen when a node is deleted in parallel with calling
the port list API. Ports are fetched, then we try do fetch their
nodes and port groups. If either of them are removed in the meantime,
the API fails with HTTP 400. This change works around it.
Change-Id: Ie2d4c46c031ee8 6976abb6107433c dde87a4345a fd59be44e0f9f56 27fac5cec4)
Closes-Bug: #1748893
(cherry picked from commit 52dcc642d372e23