Comment 4 for bug 1833730

The suspicion is this issue is a result of only 1 nova-api-proxy pod running in the system and it was likely running on the standby controller when it was rebooted. Logs would be required from controller-1 to confirm.

Peng please run a test where nova-api-proxy is running on the standby controller, reboot the standby controller, and determine how long it takes before the openstack server-list command starts working again. This time will tell us how long it takes to fail the nova-api-proxy pod and have it come up on the active controller.