004_basic_sanity.test_gen test failed for ovirt-master in vdsm project

Description

The patch that CQ marked seems to be related.
the patch that failed CQ is: https://gerrit.ovirt.org/#/c/93046/
you can look at the build's logs here:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8725/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-004_basic_sanity.py/

the engine log shows several tasks that fail and then there is an exception:
https://pastebin.com/6f5QTZUH

Activity

Show:

Dafna Ron July 31, 2018 at 8:12 AM

this no longer happens and can be resolved.

Dafna Ron July 20, 2018 at 1:43 PM

Thank you.
I'll keep this open until next week and if I do not see it repeat I will close.

Thank you for the help Milan!

Milan Zamazal July 20, 2018 at 1:35 PM

There has already been experience in OST with a similar problem, resolved by using a different check. So I posted a patch changing the check in preview_snapshot_with_memory: https://gerrit.ovirt.org/93216

Dafna Ron July 20, 2018 at 11:28 AM

thanks for looking in to this.
looking again at the last failure it's not in ovirt-engine but in ovirt-ansible-disaster-recovery and in 4.2
usually I would say that because its not in a specific project its probably the test but because its a completely random failure there is a chance that its been merged and not failed CQ.
So lets wait to see if its an actual regression and not skip at this time.

Milan Zamazal July 20, 2018 at 11:18 AM

I looked into the problem and I'm not sure whether the check in the test is based on wrong assumptions or whether there is a bug in Engine / REST API. I've sent a question to oVirt devel mailing list. Depending on the answer either the test in OST should be fixed or oVirt should be fixed. If the failure causes too much trouble in the meantime, you can disable make_snapshot_with_memory + preview_snapshot_with_memory + check_snapshot_with_memory tests in 004_basic_sanity.py.

Fixed

Details

Assignee

Reporter

Priority

Created July 19, 2018 at 9:29 AM
Updated September 2, 2018 at 3:50 PM
Resolved July 31, 2018 at 8:12 AM

Flag notifications