** Changed in: tempest
Assignee: chandan kumar (chkumar246) => (unassigned)
** Changed in: tempest
Importance: Undecided => Medium
** No longer affects: glance
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Marking as invalid for Glance. The problem is occurring in a Compute
API (nova) test. I think your analysis is correct, that this is a
timing problem and that this may be too fine-grained a test; the test
should use a different success criteria.
** Changed in: glance
Status: New =>
As far as I understand, this test shouldn't even exist in scope of
tempest, because you can't guarantee that backend will be slow to
process the request. This kind of interaction would be better served by
a test with better execution flow control. I am not sure if glance have
those, but in neutron
accordingly to avoid description, looks like this is a tempest issue?
** Project changed: nova => tempest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1713163
Title:
4 matches
Mail list logo
