Comment 6 for bug 1930801

The problem has been solved.
Probably, this problem occurs when the hostname that can be obtained by "replacement" and the hostname specified by the zun API are different.
Since the hostname is registered on the zun side and not on the replacement side, no error will occur on the zun side, but an empty list will be returned when querying the resource, resulting in a status error "There are not enough hosts available".

  zun host | placement(nova) host |
hostA_zun | hostA_nova | -> "There are not enough hosts available"
   hostA | hostA | -> No problem

It was not a bug, but a problem with my configuration.
However, I think the error status information should be more detailed.
In this problem, I had enough resources, just not enough hosts to search.
I feel that the error status of "There are not enough hosts available" is insufficient.