Comment 2 for bug 1368954

no, the endpoint is there. the heat api was not responding at the time of trove instance creation. I had to restart heat-api/engine before it became responsive again. But the same issue can happen, if there is a problem with network connectivity. Trove should not get stuck forever in BUILDING state and not allow you to fix it without database manipulations.