This behavior is expected in specific circumstances. When we loose a connection to a host we stop tracking responses for this connection. When we reconnect we could see responses that we do not track anymore.
Can you give more context about this specific log? On Tue, Dec 13, 2016 at 2:14 PM, Roy Golan <[email protected]> wrote: > > > On 13 December 2016 at 12:53, Yaniv Kaul <[email protected]> wrote: > >> Can someone explain what it means? >> (Background: getting again host non-operational when installing). I've >> grepp'ed the relevant UUID, and this is what I'm getting: >> >> {"jsonrpc":"2.0","method":"Host.ping","params":{},"id":"873e >> a6a7-d892-4398-bd2a-26d07cc85b60"} >> <JsonRpcRequest id: "873ea6a7-d892-4398-bd2a-26d07cc85b60", method: >> Host.ping, params: {}> >> {"jsonrpc": "2.0", "id": "873ea6a7-d892-4398-bd2a-26d07cc85b60", >> "result": true} >> 2016-12-13 05:45:17,689-05 DEBUG >> [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] >> (ResponseWorker) [] Message received: {"jsonrpc": "2.0", "id": >> "873ea6a7-d892-4398-bd2a-26d07cc85b60", "result": true} >> 2016-12-13 05:45:17,690-05 ERROR >> [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] >> (ResponseWorker) [] *Not able to update response for >> "873ea6a7-d892-4398-bd2a-26d07cc85b60* >> > > > +pkliczew > > I saw similar problems on scale lab and started explore that yesterday. > Response tracker is trying to track a stomp message with that ID but the > call that is asociated with it is empty. I suspect that the worse that can > happen is that we might have request from the engine that will never be > treated. > Piotr may have looked further by now. > >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.phx.ovirt.org/mailman/listinfo/devel >> > >
_______________________________________________ Devel mailing list [email protected] http://lists.phx.ovirt.org/mailman/listinfo/devel
