The unshelve notification functional sample test fails intermittently
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Balazs Gibizer | ||
Pike |
Fix Released
|
Low
|
Balazs Gibizer | ||
Queens |
Fix Committed
|
Low
|
Balazs Gibizer | ||
Rocky |
Fix Committed
|
Low
|
Balazs Gibizer | ||
Stein |
Fix Committed
|
Low
|
Balazs Gibizer |
Bug Description
The notification sample test for unshelve waits for the instance to reach ACTIVE state and then asserts if unshelve.end notification is emitted properly. However the instance.vm_state is set to ACTIVE earlier[1] than emitting the unshelve.end notification[2]. This can cause two different test case failures.
1) _test_unshelve_
2) _test_shelve_
[1] https:/
[2] https:/
[3] https:/
Changed in nova: | |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
status: | New → In Progress |
tags: | added: testing |
Changed in nova: | |
importance: | Undecided → Low |
I got reports that both cases happening in a downstream env and I can reproduce it locally. But I did not found occurences of this fault in logstash