It's really unclear to me if there is a tempest change needed here. This seems to be another one of the state race bugs in OpenStack services where the resource doesn't get to it's intended state. Hence tempest is doing exactly it's mission, exposing these.
It's really unclear to me if there is a tempest change needed here. This seems to be another one of the state race bugs in OpenStack services where the resource doesn't get to it's intended state. Hence tempest is doing exactly it's mission, exposing these.