On Mon, Apr 23, 2018 at 3:10 PM, Dafna Ron <dron@redhat.com> wrote:
I can see in the logs that the vm fails to re-start with vm path does not exist.
but what I found odd is that we try to start the vm on the same host that it ran on before and I think that the issue is actually that we set the HA vm as a pin to host vm (which should not be a possibility since HA should start the vm on a different host).

Can you please have a look?

Is it still the issue around the high-perf VM? It has to be (on one hand) pinned to a single host (if we define NUMA topo for it) and on the other hand cannot be used for HA recovery test...
Can you revert the whole commit around high perf VM? I assume we'll need to re-think on how to do it.
Y.


Thanks.
Dafna


On Mon, Apr 23, 2018 at 12:34 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
I'm seeing this fail periodically on a patch I'm working on, and it's not related to my work. Any ideas?

<testcase classname="004_basic_sanity" name="ha_recovery" time="1058.886">

<failure type="exceptions.AssertionError" message="False != True after 600 seconds...

tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 735, in ha_recovery
    lambda:
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 271, in assert_true_within_long
    assert_equals_within_long(func, True, allowed_exceptions)
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, in assert_equals_within_long
    func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in assert_equals_within
    '%s != %s after %s seconds' % (res, value, timeout)
'False != True after 600 seconds

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel