STX-OpenStack: After a lock/unlock, "openstack hypervisor list" returns Error 500

[Lucas de Ataides Barreto]

Brief Description
-----------------
After performing a lock/unlock on a controller host, the "openstack hypervisor list" command returned an Error 500

Severity
--------
Major: System/Feature is usable but degraded

Steps to Reproduce
------------------
1. Lock/unlock a host
2. After host is unlocked, send "openstack hypervisor list"

Expected Behavior
------------------
Commands returns the list of hypervisors

Actual Behavior
----------------
Command returns Error 500 - Internal Server Error

Reproducibility
---------------
Seen once

System Configuration
--------------------
Bare metal AIO-DX

Branch/Pull Time/Commit
-----------------------
/mirror/starlingx/master/debian/monolithic/20230131T070000Z/

Last Pass
---------
Was failing for other reasons before.
Passed in this Sanity run: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013776.html

Timestamp/Logs
--------------
openstack --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne hypervisor list
Internal Server Error (HTTP 500)

Test Activity
-------------
Feature Testing

Workaround
----------
Wait for a few minutes and the command works again

[Danilo (ddonasci)]

What we saw is that this issue happens for a second because the hypervisor is restarting the service.
In order to solve this issue we created a loop structure to retry to run the command if it fails at the first attempt.

[Thales Elero Cervi (tcervi)]

Seems to be a timing issue, thanks Danilo.
Will close this LP for now.