Bug 1425725 - Not able to update response
Summary: Not able to update response
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.1.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Piotr Kliczewski
QA Contact: Aleksei Slaikovskii
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-22 08:58 UTC by Dominik Holler
Modified: 2017-05-23 08:14 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:14:57 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: ovirt-4.2+
mgoldboi: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 72821 0 master MERGED incomplete message 2020-09-24 15:53:22 UTC
oVirt gerrit 72916 0 master MERGED Version bump 2020-09-24 15:53:22 UTC
oVirt gerrit 72980 0 master MERGED jsonrpc: version bump 2020-09-24 15:53:22 UTC
oVirt gerrit 73516 0 ovirt-4.1 MERGED incomplete message 2020-09-24 15:53:21 UTC
oVirt gerrit 73517 0 ovirt-4.1 MERGED Version bump 2020-09-24 15:53:21 UTC
oVirt gerrit 73619 0 ovirt-engine-4.1 MERGED Version bump 2020-09-24 15:53:21 UTC
oVirt gerrit 73620 0 ovirt-engine-4.1.1.z ABANDONED Version bump 2020-09-24 15:53:22 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.