Comment 1 for bug 1403439

So this most likely isn't a tempest bug. The tempest failure is being caused by a 500 response from nova (when using the docker driver) which is normally nova having an unhandled exception. So I've added the nova-docker project here as the primary project, because it raising an exception on a server create that the api layer doesn't know how to handle.

Feel free to re-add tempest in the future if you can show that tempest is doing something invalid to cause this. (or there is a some other bug or gap in tempest causing the failure w/ nova-docker) For example, I could see this being an issue w/ nova-docker not supporting disk-config and tempest not having a way to know that. However in that case it would still be primarily a nova-docker bug because raising a 500 is still incorrect if a feature isn't supported.