Sorry, I am inclined to say that the problem you are describing is specifically nova issue. I will change affected project to Nova, as I believe this bug report fits better there.
As far as I know regarding the topic - this is pretty much intended behavior and a known dropback. The only workaround I'm aware of is to update the database. So in case a hostname for compute needs to change, we always ensure that no VM is running there before doing so.
Hey,
Sorry, I am inclined to say that the problem you are describing is specifically nova issue. I will change affected project to Nova, as I believe this bug report fits better there.
As far as I know regarding the topic - this is pretty much intended behavior and a known dropback. The only workaround I'm aware of is to update the database. So in case a hostname for compute needs to change, we always ensure that no VM is running there before doing so.