Retry attachment delete API call for 504 Gateway Timeout
When cinder-api runs behind a load balancer(eg haproxy), the load
balancer can return 504 Gateway Timeout when cinder-api does not
respond within timeout. This change ensures nova retries deleting
a volume attachment in that case.
Also this change makes nova ignore 404 in the API call. This is
required because cinder might continue deleting the attachment even if
the load balancer returns 504. This also helps us in the situation
where the volume attachment was accidentally removed by users.
Closes-Bug: #1978444
Change-Id: I593011d9f4c43cdae7a3d53b556c6e2a2b939989
(cherry picked from commit 8f4b740ca5292556f8e953a30f2a11ed4fbc2945)
Reviewed: https:/ /review. opendev. org/c/openstack /nova/+ /849212 /opendev. org/openstack/ nova/commit/ b94ffb1123b1a6c f0a8675e0d6f107 2e9625f570
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit b94ffb1123b1a6c f0a8675e0d6f107 2e9625f570
Author: Takashi Kajinami <email address hidden>
Date: Mon Jun 13 14:48:24 2022 +0900
Retry attachment delete API call for 504 Gateway Timeout
When cinder-api runs behind a load balancer(eg haproxy), the load
balancer can return 504 Gateway Timeout when cinder-api does not
respond within timeout. This change ensures nova retries deleting
a volume attachment in that case.
Also this change makes nova ignore 404 in the API call. This is
required because cinder might continue deleting the attachment even if
the load balancer returns 504. This also helps us in the situation
where the volume attachment was accidentally removed by users.
Closes-Bug: #1978444 dae7a3d53b556c6 e2a2b939989 6f8e953a30f2a11 ed4fbc2945)
Change-Id: I593011d9f4c43c
(cherry picked from commit 8f4b740ca529255