| 2022-11-16 15:02:07 |
Arun Mani |
description |
Problem:
When a query to compute server GET all_tenants is sent we receive a cell timeout and no response is received.
Root Cause:
The default Openstack behaviour with Cells is that when any cell does not respond it is skipped and the API continues to return a success 200 response. In the logs we see "Cell %s is not responding and hence is being omitted from the results" . This behaviour caused empty list of resources to be sent back to the caller. Any caller using this API assumes there are no resources in the cell and proceeds.
Workaround:
The solution here was to change the default configuration of "list_records_by_skipping_down_cells" to False. This meant when any cell did not return results a 500 error was returned, which now indicates a problem with the API. This will alert the caller correctly and can be handled in the right way. |
Problem:
When a query to compute server GET all_tenants is sent we receive a cell timeout and no response is received.
Root Cause:
The default Openstack behaviour with Cells is that when any cell does not respond it is skipped and the API continues to return a success 200 response. In the logs we see "Cell %s is not responding and hence is being omitted from the results" . This behaviour caused empty list of resources to be sent back to the caller. Any caller using this API assumes there are no resources in the cell and proceeds.
Workaround:
The solution here was to change the default configuration of "list_records_by_skipping_down_cells" to False. This meant when any cell did not return results a 500 error was returned, which now indicates a problem with the API. This will alert the caller correctly and can be handled in the right way.
PS: This is observed with the wallaby version of Openstack. |
|
