Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1425725

Summary: Not able to update response
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: Backend.CoreAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED CURRENTRELEASE QA Contact: Aleksei Slaikovskii <aslaikov>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.1CC: bugs, eedri, lsvaty, lveyde, mgoldboi, mperina, oourfali, pkliczew, pstehlik
Target Milestone: ovirt-4.1.2Flags: rule-engine: ovirt-4.1+
rule-engine: ovirt-4.2+
mgoldboi: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+
Target Release: 4.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-23 08:14:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dominik Holler 2017-02-22 08:58:14 UTC 
Description of problem:

During a run of ovirt-system-test, the engine has unexpected behavior
[org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for "02298344-165f-47e4-9ea4-7c17a55d37f8"
which causes the test to fail.

Please find details in
http://lists.ovirt.org/pipermail/devel/2017-February/029626.html

How reproducible:
May happen during running 005_network_by_label.py in basic-suit-master of ovirt-system-tests


Steps to Reproduce:
1. run basic-suit-master of ovirt-system-tests
2. search engine.log for "Not able to update response"
3.

Actual results:
test may fail

Expected results:


Additional info:
Comment 1 Lukas Svaty 2017-03-08 15:14:55 UTC 
Do you have any verification steps for this? Can this be reproduced in real scenario or is it cause by specific scenario in ovirt-system-tests?
Comment 2 Piotr Kliczewski 2017-03-13 08:04:31 UTC 
Lucas,

This issue is hard to test and there is no specific scenario which could trigger it. The only thing I would recommend is to run ovirt-system-tests many times and make sure that it is not occurring. Since the fix was introduced there was not tests failure due to it.
Comment 3 Aleksei Slaikovskii 2017-05-11 17:58:21 UTC 
Verified on ovirt-system-tests bc31ebe7d31c5fc5b28f604a6d3ac161a6dfde18

I've ran basic-suit-master for 10 times and no tests failed.