nova.tests.unit.conductor.test_conductor.ConductorTaskAPITestCase.test_rebuild_instance_with_scheduler_group_failure race fails in the gate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann |
Bug Description
2015-03-19 15:30:04.664 | {5} nova.tests.
2015-03-19 15:30:04.664 |
2015-03-19 15:30:04.664 | Captured traceback:
2015-03-19 15:30:04.664 | ~~~~~~~~~~~~~~~~~~~
2015-03-19 15:30:04.664 | Traceback (most recent call last):
2015-03-19 15:30:04.664 | File "/home/
2015-03-19 15:30:04.664 | return func(*args, **keywargs)
2015-03-19 15:30:04.664 | File "nova/tests/
2015-03-19 15:30:04.664 | exception, request_spec)
2015-03-19 15:30:04.664 | File "/home/
2015-03-19 15:30:04.665 | raise AssertionError(msg)
2015-03-19 15:30:04.665 | AssertionError: Expected to be called once. Called 2 times.
Seeing it on two changes so far:
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
Note that the rebuild_instance test has _set_vm_ state_and_ notify mocked, but we see that when it fails, something else is calling _set_vm_ state_and_ notify from build_instances:
http:// logs.openstack. org/30/ 164330/ 2/gate/ gate-nova- python27/ 19869e2/ console. html#_2015- 03-19_15_ 30_04_669
So there must be another test doing the same mock (or not doing it right) and that's screwing this up, which is probably this test:
test_build_ instances_ scheduler_ group_failure
That does the same mocking.