Comment 2 for bug 1833069

Turns out there is another thing going on here. When nova services start up, they store their service version in the services table in the database. If the service SIGHUP/restart occurs before this has happened, then the version cap will not be removed since some services will still appear to be running the old version still. This is really all about nova-compute's version.

Testing suggests that it takes about 10 seconds for the version to be updated in an AIO setup on Rocky. This is likely to be more time than Ansible allows between these tasks.

Ideally there would be some nova mechanism (API call or nova-manage) to wait until all computes are running the latest version, then only restart services after that. In the absence of that, a sleep seems the best option right now.