Anton Kurbatov 6395b4fe8e Fixing the 500 HTTP code in the metadata service if Nova is down ... If the Nova metadata service is unavailable, the requests.request() function may raise a ConnectionError. This results in the upper code returning a 500 HTTP status code to the user along with a traceback. Let's handle this scenario and instead return a 503 HTTP status code (service unavailable). If the Nova service is down and is behind another proxy (such as Nginx), then instead of a ConnectionError, the request may result in receiving a 502 or 503 HTTP status code. Let's also consider this situation and add support for an additional 504 code. Closes-Bug: #2059032 Change-Id: I16be18c46a6796224b0793dc385b0ddec01739c4		2024-03-26 12:14:08 +00:00
..
notes	Fixing the 500 HTTP code in the metadata service if Nova is down	2024-03-26 12:14:08 +00:00
source	Update master for stable/2024.1	2024-03-15 14:50:30 +00:00