[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738013#comment-13738013
 ] 

Sowmya Krishnan commented on CLOUDSTACK-4285:
---------------------------------------------

MS Log:

2013-08-13 14:41:13,375 WARN  [cloud.api.ApiServer] (ApiServer-7:null) Unknown 
API command: configureSimulator
2013-08-13 14:41:13,375 INFO  [cloud.api.ApiServer] (ApiServer-7:null) Unknown 
API command: configureSimulator

                
> confgiureSimulator throwing "Unknown API command" error
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-4285
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4285
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API
>    Affects Versions: 4.2.0
>         Environment: 4.2, compile with simulator
>            Reporter: Sowmya Krishnan
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> configureSimulator API is throwing Unknown API command error:
> Tried with latest 4.2, compiled with simulator:
> mvn -Pdeveloper -Dsimulator clean install
> "http://localhost:8096/client/api?command=configureSimulator&zoneid=1&name=DhcpEntryCommand&value=wait:1000
> --2013-08-13 14:41:13--  
> http://localhost:8096/client/api?command=configureSimulator&zoneid=1&name=DhcpEntryCommand&value=wait:1000
> Resolving localhost... 127.0.0.1
> Connecting to localhost|127.0.0.1|:8096... connected.
> HTTP request sent, awaiting response... 432 Unknown API command: 
> configureSimulator
> 2013-08-13 14:41:13 ERROR 432: Unknown API command: configureSimulator
> commands.properties already has an entry for the api:
> #### host simulator commands
> configureSimulator=1
> This blocks many use cases of performance testing where we induce delay to 
> specific commands using simulator. Hence marking it blocker.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to