[ovirt-users] fakevdsm vs ovirt engine 4.0.4

Tue Oct 18 09:29:31 UTC 2016

Hi Roman, i did , but i redid it :)
IS there any reason these changes would not be persisted on the 
ovirt-engine?
Either way it does work now so thanks.
When i made the changes i did this from the psql console perhaps thats 
the issue.
either way thank you so much, its great to be able to use this tool for 
performance testing.

Awesome Job!!!!!

Roman Mohr schreef op 2016-10-18 10:15:
> On Tue, Oct 18, 2016 at 10:04 AM, <joost at familiealbers.nl [17]> 
> wrote:
>
>> Hi Roman, thanks for the quick response, i have followed your advice
>> but still see the following fakevdsm console.
>
> Could it be that you did not disable the SSL encryption on the engine
> side? Did you follow the steps in [15] and restarted ovirt-engine?
>
>> 2016-10-18 07:49:34,105 Message sent: null
>> 2016-10-18 07:49:34,105 Unable to process messages
>> java.io.IOException: Broken pipe
>>         at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
>>         at
>> sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
>>         at
>> sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
>>         at sun.nio.ch.IOUtil.write(IOUtil.java:65)
>>         at
>> sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:492)
>>         at
>>
> 
> org.ovirt.vdsm.jsonrpc.client.reactors.PlainClient.write(PlainClient.java:55)
>>         at
>>
> 
> org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.processOutgoing(ReactorClient.java:241)
>>         at
>>
> 
> org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.process(ReactorClient.java:204)
>>         at
>>
> 
> org.ovirt.vdsm.jsonrpc.client.reactors.Reactor.processChannels(Reactor.java:89)
>>         at
>> org.ovirt.vdsm.jsonrpc.client.reactors.Reactor.run(Reactor.java:65)
>> 2016-10-18 07:49:34,106
>>
>> 2016-10-18 07:49:34,106 Message sent: null
>> 2016-10-18 07:49:34,107 Failure in processing request
>> java.lang.IllegalArgumentException: method field missing in node
>>         at
>>
> 
> org.ovirt.vdsm.jsonrpc.client.JsonRpcRequest.fromJsonNode(JsonRpcRequest.java:79)
>>         at
>>
> 
> org.ovirt.vdsm.jsonrpc.client.JsonRpcRequest.fromByteArray(JsonRpcRequest.java:103)
>>         at
>>
> 
> org.ovirt.vdsmfake.rpc.json.JsonRpcServer$MessageHandler.run(JsonRpcServer.java:122)
>>         at
>>
> 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>         at
>> java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>         at
>>
> 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>         at
>>
> 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>         at java.lang.Thread.run(Thread.java:745)
>> 2016-10-18 07:49:37,095 CONNECT
>> accept-version:1.2
>> heart-beat:0,21234
>> host:null
>>
>> Roman Mohr schreef op 2016-10-18 09:06:
>>
>>> Hi,
>>>
>>> On Tue, Oct 18, 2016 at 12:28 AM, <joost at familiealbers.nl [1]
>>> [13]> wrote:
>>>
>>>> Hi All,
>>>> I am trying to start load tests against my newly installed
>>>> ovirt
>>>> engine version 4.0.4
>>>
>>> Note that latest fakevdsm is currently broken when using it with
>>> 4.0
>>> releases, it only works on master.
>>>
>>> You can check out the code from here
>>>
>>> https://gerrit.ovirt.org/#/c/65333/ [2] [14]
>>>
>>> to get a working version for 4.0.
>>>  
>>>
>>>> I can run fakevdsm as follows (minor changes to pom.xml (mainly
>>>> jetty plugin version)
>>>> i also changed vdsm-jsonrpc-java-client to match that of the
>>>> server.
>>>>
>>>>                        
>>>> <groupId>org.ovirt.vdsm-jsonrpc-java</groupId>
>>>>                        
>>>> <artifactId>vdsm-jsonrpc-java-client</artifactId>
>>>>                         <version>1.2.5</version>
>>>>
>>>> i can run the app using
>>>>
>>>> mvn jetty:run -Dfake.host=0.0.0.0 -DjsonListenPort=54321
>>>> -DvdsmPort=54322
>>>
>>> could you try running "mvn clean" before starting it again?
>>> Fakevdsm
>>> has a cache and if something is wrong with that data there (e.g.
>>> a bug
>>> or switching between engine versions) you can end up in such
>>> situations. Running "mvn clean" cleans the cache too.Roman
>>>
>>> Links:
>>> ------
>>> [1] http://iqn.1994-05.com [3]
>>> [2] http://52.25.68.41 [4]
>>> [3] http://52.25.68.41 [5]
>>> [4] http://r.monitoring.HostMonitoring.re [6]
>>> [5] http://org.quartz.core.JobRunShell.ru [7]
>>> [6] http://52.25.68.41 [8]
>>> [7] http://52.25.68.41 [9]
>>> [8] http://r.monitoring.HostMonitoring.re [10]
>>> [9] http://org.quartz.core.JobRunShell.ru [11]
>>> [10] http://52.25.68.41 [12]
>>> [11] mailto:Users at ovirt.org [13]
>>> [12] http://lists.ovirt.org/mailman/listinfo/users [14]
>>> [13] mailto:joost at familiealbers.nl [15]
>>> [14] https://gerrit.ovirt.org/#/c/65333/ [16]
>
> [15] https://github.com/oVirt/ovirt-vdsmfake#prepare-ovirt-engine
> [18] 
>
>
> Links:
> ------
> [1] mailto:joost at familiealbers.nl
> [2] https://gerrit.ovirt.org/#/c/65333/
> [3] http://iqn.1994-05.com
> [4] http://52.25.68.41
> [5] http://52.25.68.41
> [6] http://r.monitoring.HostMonitoring.re
> [7] http://org.quartz.core.JobRunShell.ru
> [8] http://52.25.68.41
> [9] http://52.25.68.41
> [10] http://r.monitoring.HostMonitoring.re
> [11] http://org.quartz.core.JobRunShell.ru
> [12] http://52.25.68.41
> [13] mailto:Users at ovirt.org
> [14] http://lists.ovirt.org/mailman/listinfo/users
> [15] mailto:joost at familiealbers.nl
> [16] https://gerrit.ovirt.org/#/c/65333/
> [17] mailto:joost at familiealbers.nl
> [18] https://github.com/oVirt/ovirt-vdsmfake#prepare-ovirt-engine