Comment 4 for bug 1628448

I found the same problem in my mitaka version. It dose not happen every time. So I feel that maybe the connection between config drive is not disconnected from instance, it shows busy status.