Re: [ovirt-devel] [OST Failure Report] [oVirt master] [09.02.2017] [test-repo_ovirt_experimental_master]

A deep analysis of the logfiles gives details about the unexpected behavior, but I regret to not provide the fault causing the unexpected behavior. To get this fault, the help of someone familiar with org.ovirt.vdsm.jsonrpc.client.JsonRpcClient is needed. In the failing test "assign_labeled_network" a (labeld) network is assigned to the cluster. For this reason the network has to be added to the hosts. After that, the test "assign_labeled_network" checks, if the engine acknowledges that hosts are in the labeld network. This execution of the test failed, because this acknowledge of the engine is missing after 180 seconds [3]. There are two hosts lago-basic-suite-master-host0 and lago-basic-suite-master-host1 in the scenario. lago-basic-suite-master-host1 fails and lago-basic-suite-master-host0 succeeds, so only lago-basic-suite-master-host1 is analyzed below. Please find here the most relevant steps causing this error: 1. The engine sends Host.setupNetworks to the hosts in line 40279 - 40295 in [1] with "id":"02298344-165f-47e4-9ea4-7c17a55d37f8". 2. The host executes the Host.setupNetworks RPC call successfully in line 1286 in [2]. 3. The engine receives the acknowledgment of the successful execution in line 40716 and 40717 in [1]. 4. The error occurs in line 40718: '[org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for "02298344-165f-47e4-9ea4-7c17a55d37f8"'. This means the engine can not process the acknowledgment of the successful execution. 5. The command HostSetupNetworksVDS is aborted. So Host.getCapabilities is skipped and the engine database is not updated with the new network configuration of the host. 6. Since the test script relays on the information from database about host network configuration, it does not see that Host.setupNetworks is successfully executed and stops with the error "False != True after 180 seconds" [3] So the fault happens before or in step 4 and is around the jsonrpc communication. It is an open action item to precise the location of the fault. [1] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217/art... [2] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217/art... [3] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217/tes... On Thu, 9 Feb 2017 14:52:52 +0200 Shlomo Ben David <sbendavi(a)redhat.com&gt; wrote: