Comment 2 for bug 1709550

Tricky one this as the main nova driver has no knowledge of the nova-lxd driver (and as a result can interrogate the LXD daemon to figure things out).

I'm pretty sure that this is an issue that's common to any of the drivers in Nova as well; it you can the driver after spinning up instances, you effectively island control of an instances created with the previous driver.