is a race.
if the first image saves quickly or has not started yet then the second call can succeed without raising an exception.
we should likely remove this form tempest and instead test this with a functional test in nova as we will not be able to reliably gauntee the image will still be saving in tempest.
i suspect this only passed because of slow performance of glance/nova in the gate.
the test is not correct
https:/ /github. com/openstack/ tempest/ blob/348fa311fe 031ff7d04f41aa9 e6ac65f6f6391fe /tempest/ api/compute/ images/ test_images_ oneserver_ negative. py#L109- L114
is a race.
if the first image saves quickly or has not started yet then the second call can succeed without raising an exception.
we should likely remove this form tempest and instead test this with a functional test in nova as we will not be able to reliably gauntee the image will still be saving in tempest.
i suspect this only passed because of slow performance of glance/nova in the gate.