You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/07/23 21:58:54 UTC

[jira] [Commented] (CLOUDSTACK-3748) AddS3Cmd NPE

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

Wei Zhou commented on CLOUDSTACK-3748:
--------------------------------------

usehttps should be changed to httpsFlag, I think.

                
> AddS3Cmd NPE 
> -------------
>
>                 Key: CLOUDSTACK-3748
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3748
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>            Reporter: John Burwell
>            Priority: Blocker
>
> When executing the addS3 API command using the following parameters:
> The following NPE occurred:
>     "s3" : {
>         "accesskey": "CIQFFQ7NAACERI99P9_B",
>         "secretkey": "6jmfhptBBvWile1bUTSbnJCYW8qnPoU8WaNpIw==",
>         "bucket": "jsb-cloudstack-templates",
>         "endpoint": "192.168.56.100:8080",
>         "usehttps": false
>     }
> ERROR [cloud.api.ApiServer] (705052256@qtp-836177268-0:) unhandled exception executing api command: addS3
> java.lang.NullPointerException
> 	at org.apache.cloudstack.api.command.admin.storage.AddS3Cmd.execute(AddS3Cmd.java:104)
> 	at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> 	at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
> 	at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
> 	at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
> 	at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
> 	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:326)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> This NPE causes the API call to fail with a 530 error as depicted in the following Marvin traceback:
> Traceback (most recent call last):
>   File "/Users/jburwell/.virtualenvs/cloudstack/bin/nosetests", line 8, in <module>
>     load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py", line 118, in __init__
>     **extra_args)
>   File "/Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py", line 94, in __init__
>     self.parseArgs(argv)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/core.py", line 135, in parseArgs
>     self.config.configure(argv, doc=self.usage())
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/config.py", line 344, in configure
>     self.plugins.configure(options, self)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py", line 284, in configure
>     cfg(options, config)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py", line 99, in __call__
>     return self.call(*arg, **kw)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/nose/plugins/manager.py", line 167, in simple
>     result = meth(*arg, **kw)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/marvinPlugin.py", line 68, in configure
>     deploy.loadCfg() if options.load else deploy.deploy()
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py", line 577, in deploy
>     self.configureS3(self.config.s3)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py", line 571, in configureS3
>     self.apiClient.addS3(command)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 1298, in addS3
>     response = self.connection.marvin_request(command, response_type=response, method=method)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 222, in marvin_request
>     response = jsonHelper.getResultObj(response.json(), response_type)
>   File "/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/jsonHelper.py", line 148, in getResultObj
>     raise cloudstackException.cloudstackAPIException(respname, errMsg)
> marvin.cloudstackException.cloudstackAPIException: Execute cmd: adds3 failed, due to: errorCode: 530, errorText:None

--
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