Comment 6 for bug 1896621

I've been able to reproduce the `block copy still active` error when attempting to retype multiple volumes attached to the same instance. I'll write up a fix for this now as it's trivial.

As discussed in #openstack-nova you're also seeing your Windows AD instances fail to start after either rebooting themselves *or* being rebooted by users.

I think this is due to Nova not correctly reverting the active domain configuration back to the original volume when we hit this failure thus leaving it writing to the new volume. We eventually disconnect this new volume from the underlying host as well that I assume would cause the disk within the instance to enter a RO state.

I'm going to try to reproduce this part locally now.