Comment 7 for bug 1453265

You opened a bug about tempest here, this is not a bug about that tests use in the defcore list. (I have separate opinions about that) When you just look at tempest we actually have tests for 3 of the 4 mechanisms you outlined, the only one which doesn't have tempest tests is the use of tasks. The list test in question uses v2 create because that is the only creation mechanism that works with glance v2 (it doesn't really matter that tasks worked in J) The v1 list test uses glance v1 for the create. You actually won't be able to use image import with tasks in tempest if it doesn't work in K (or now either) unless you backport all the necessary fixes for it to all the branches so it behaves consistently everywhere. (the gate will enforce this)

What you outlined about the multiple ways to create images in glance is actually total terribleness for end users and interop, especially with glance v2. How is an end user supposed to know which of the 4 mechanisms work on Cloud X, and what if they try to use the same code against Cloud Y which happens to only allow a different mechanism. It was honestly something I was hoping defcore was going to address by declaring one way to be the "OpenStack tm" way. (which I'm now starting to have doubts about) There really is not a tempest bug here, instead as just a proxy for the corporate political debate over the defcore list.