On the env where the issue was reproduced ^^ I see one compute node in down state. Looking at tempest test code I see that it doesn't check the state of the node when spawning a VM on all nodes - most probably the instance stays in DOWN state because of down compute node.
On the env where the issue was reproduced ^^ I see one compute node in down state. Looking at tempest test code I see that it doesn't check the state of the node when spawning a VM on all nodes - most probably the instance stays in DOWN state because of down compute node.