[jira] [Commented] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size < 500, CloudStack will keep on popping up Status message box every time user logs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744233#comment-14744233 ] Yichi Lu commented on CLOUDSTACK-8782: -- Yes I did. > If pagesize is greater than default.page.size in API call, and > default.page.size < 500, CloudStack will keep on popping up Status message > box every time user logs in. > -- > > Key: CLOUDSTACK-8782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.5.2 > Environment: OS: CentOS 6.6, CloudStack 4.5.2 >Reporter: Yichi Lu > > Set default.page.size to a value < 500. > Next in a list API call (for instance, try using cloudmonkey), set page size > > default.page.size. The call will fail because page size is too big, and a > Status message box will pop up in GUI. > The problem is that the Status message box will keep popping up every time a > usr logs in, even though 'Close' has been clicked to the message box. The > message box also pops up to other users who did not issue the API call. > The problem disappears when the default.page.size is reset to 500. > Another problem is that an API call leads to the message box. Why should an > API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size < 500, CloudStack will keep on popping up Status message box every time user
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744233#comment-14744233 ] Yichi Lu edited comment on CLOUDSTACK-8782 at 9/14/15 8:49 PM: --- Yes I did. Without restarting management server, the new default.page.size value will not take effect, and therefore cloudstack should not throw exception at all. was (Author: yichi.lu): Yes I did. Without restarting management server, the new default.page.size will not take effect, and therefore cloudstack should not throw exception at all. > If pagesize is greater than default.page.size in API call, and > default.page.size < 500, CloudStack will keep on popping up Status message > box every time user logs in. > -- > > Key: CLOUDSTACK-8782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.5.2 > Environment: OS: CentOS 6.6, CloudStack 4.5.2 >Reporter: Yichi Lu > > Set default.page.size to a value < 500. > Next in a list API call (for instance, try using cloudmonkey), set page size > > default.page.size. The call will fail because page size is too big, and a > Status message box will pop up in GUI. > The problem is that the Status message box will keep popping up every time a > usr logs in, even though 'Close' has been clicked to the message box. The > message box also pops up to other users who did not issue the API call. > The problem disappears when the default.page.size is reset to 500. > Another problem is that an API call leads to the message box. Why should an > API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size < 500, CloudStack will keep on popping up Status message box every time user
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744233#comment-14744233 ] Yichi Lu edited comment on CLOUDSTACK-8782 at 9/14/15 8:49 PM: --- Yes I did. Without restarting management server, the new default.page.size will not take effect, and therefore cloudstack should not throw exception at all. was (Author: yichi.lu): Yes I did. > If pagesize is greater than default.page.size in API call, and > default.page.size < 500, CloudStack will keep on popping up Status message > box every time user logs in. > -- > > Key: CLOUDSTACK-8782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.5.2 > Environment: OS: CentOS 6.6, CloudStack 4.5.2 >Reporter: Yichi Lu > > Set default.page.size to a value < 500. > Next in a list API call (for instance, try using cloudmonkey), set page size > > default.page.size. The call will fail because page size is too big, and a > Status message box will pop up in GUI. > The problem is that the Status message box will keep popping up every time a > usr logs in, even though 'Close' has been clicked to the message box. The > message box also pops up to other users who did not issue the API call. > The problem disappears when the default.page.size is reset to 500. > Another problem is that an API call leads to the message box. Why should an > API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size < 500, CloudStack will keep on popping up Status message box every time user logs in
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu updated CLOUDSTACK-8782: - Description: Set default.page.size to a value < 500, and restart management server. Next in a list API call (for instance, try using cloudmonkey), set page size > default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that an API call leads to the message box. Why should an API call lead to a Status message box on GUI? was: Set default.page.size to a value < 500. Next in a list API call (for instance, try using cloudmonkey), set page size > default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that an API call leads to the message box. Why should an API call lead to a Status message box on GUI? > If pagesize is greater than default.page.size in API call, and > default.page.size < 500, CloudStack will keep on popping up Status message > box every time user logs in. > -- > > Key: CLOUDSTACK-8782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.5.2 > Environment: OS: CentOS 6.6, CloudStack 4.5.2 >Reporter: Yichi Lu > > Set default.page.size to a value < 500, and restart management server. > Next in a list API call (for instance, try using cloudmonkey), set page size > > default.page.size. The call will fail because page size is too big, and a > Status message box will pop up in GUI. > The problem is that the Status message box will keep popping up every time a > usr logs in, even though 'Close' has been clicked to the message box. The > message box also pops up to other users who did not issue the API call. > The problem disappears when the default.page.size is reset to 500. > Another problem is that an API call leads to the message box. Why should an > API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size < 500, CloudStack will keep on popping up Status message box every time user
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744233#comment-14744233 ] Yichi Lu edited comment on CLOUDSTACK-8782 at 9/14/15 9:29 PM: --- Yes I did. was (Author: yichi.lu): Yes I did. Without restarting management server, the new default.page.size value will not take effect, and therefore cloudstack should not throw exception at all. > If pagesize is greater than default.page.size in API call, and > default.page.size < 500, CloudStack will keep on popping up Status message > box every time user logs in. > -- > > Key: CLOUDSTACK-8782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.5.2 > Environment: OS: CentOS 6.6, CloudStack 4.5.2 >Reporter: Yichi Lu > > Set default.page.size to a value < 500, and restart management server. > Next in a list API call (for instance, try using cloudmonkey), set page size > > default.page.size. The call will fail because page size is too big, and a > Status message box will pop up in GUI. > The problem is that the Status message box will keep popping up every time a > usr logs in, even though 'Close' has been clicked to the message box. The > message box also pops up to other users who did not issue the API call. > The problem disappears when the default.page.size is reset to 500. > Another problem is that an API call leads to the message box. Why should an > API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size 500, CloudStack will keep on popping up Status message box every time user logs in
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu updated CLOUDSTACK-8782: - Description: Set default.page.size to a value 500. Next in a list API call (for instance, try using cloudmonkey), set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that the message box is caused by an API call. Why should an API call lead to a Status message box on GUI? was: Set default.page.size to a value 500. Next in a list API call, set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. If pagesize is greater than default.page.size in API call, and default.page.size 500, CloudStack will keep on popping up Status message box every time user logs in. -- Key: CLOUDSTACK-8782 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.5.2 Environment: OS: CentOS 6.6, CloudStack 4.5.2 Reporter: Yichi Lu Set default.page.size to a value 500. Next in a list API call (for instance, try using cloudmonkey), set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that the message box is caused by an API call. Why should an API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size 500, CloudStack will keep on popping up Status message box every time user logs in
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu updated CLOUDSTACK-8782: - Description: Set default.page.size to a value 500. Next in a list API call (for instance, try using cloudmonkey), set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that an API call leads to the message box. Why should an API call lead to a Status message box on GUI? was: Set default.page.size to a value 500. Next in a list API call (for instance, try using cloudmonkey), set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that the message box is caused by an API call. Why should an API call lead to a Status message box on GUI? If pagesize is greater than default.page.size in API call, and default.page.size 500, CloudStack will keep on popping up Status message box every time user logs in. -- Key: CLOUDSTACK-8782 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.5.2 Environment: OS: CentOS 6.6, CloudStack 4.5.2 Reporter: Yichi Lu Set default.page.size to a value 500. Next in a list API call (for instance, try using cloudmonkey), set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. Another problem is that an API call leads to the message box. Why should an API call lead to a Status message box on GUI? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8782) If pagesize is greater than default.page.size in API call, and default.page.size 500, CloudStack will keep on popping up Status message box every time user logs in
Yichi Lu created CLOUDSTACK-8782: Summary: If pagesize is greater than default.page.size in API call, and default.page.size 500, CloudStack will keep on popping up Status message box every time user logs in. Key: CLOUDSTACK-8782 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8782 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.5.2 Environment: OS: CentOS 6.6, CloudStack 4.5.2 Reporter: Yichi Lu Set default.page.size to a value 500. Next in a list API call, set page size default.page.size. The call will fail because page size is too big, and a Status message box will pop up in GUI. The problem is that the Status message box will keep popping up every time a usr logs in, even though 'Close' has been clicked to the message box. The message box also pops up to other users who did not issue the API call. The problem disappears when the default.page.size is reset to 500. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu reassigned CLOUDSTACK-6015: Assignee: sebastien goasguen (was: Yichi Lu) I won't have time to work on this issue anytime soon. Assign back to Sebastien. Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: sebastien goasguen Assignee: sebastien goasguen Labels: gsoc2014 To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu updated CLOUDSTACK-6015: - Affects Version/s: (was: 4.4.0) 4.5.0 Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: sebastien goasguen Assignee: Yichi Lu Labels: gsoc2014 To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6202) Support signature version 3 in Cloudmonkey
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu reassigned CLOUDSTACK-6202: Assignee: Yichi Lu Support signature version 3 in Cloudmonkey -- Key: CLOUDSTACK-6202 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6202 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Cloudmonkey Reporter: Chiradeep Vittal Assignee: Yichi Lu Cloudstack has signatureVersion=3 which supports an 'expires' timestamp. This enhances security by making replay attacks less likely. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13913018#comment-13913018 ] Yichi Lu commented on CLOUDSTACK-6015: -- https://reviews.apache.org/r/18516/ Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: sebastien goasguen Assignee: Yichi Lu Labels: gsoc2014 To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yichi Lu reassigned CLOUDSTACK-6015: Assignee: Yichi Lu Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: sebastien goasguen Assignee: Yichi Lu Labels: gsoc2014 To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905877#comment-13905877 ] Yichi Lu commented on CLOUDSTACK-6015: -- https://reviews.apache.org/r/18277/ Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: sebastien goasguen Labels: gsoc2014 To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893853#comment-13893853 ] Yichi Lu commented on CLOUDSTACK-6015: -- I'll start working on this. Code will be checked in to test/selenium. I'll post my progress here. Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: sebastien goasguen Labels: gsoc2014 To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5079) listConfigurations for cluster is resulting in NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13843229#comment-13843229 ] Yichi Lu commented on CLOUDSTACK-5079: -- Harikrishna: Should I just discard what I did? Please advise (I am quite new). Yichi On Tue, Nov 26, 2013 at 12:34 AM, Harikrishna Patnala (JIRA) listConfigurations for cluster is resulting in NPE -- Key: CLOUDSTACK-5079 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5079 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Srikanteswararao Talluri Assignee: Harikrishna Patnala Priority: Critical Fix For: 4.3.0 API issued: http://ms:8080/client/api?command=listConfigurationsclusterid=e3ab8dc1-f8df-4a4f-b42b-51867e36ab76response=jsonsessionkey=8CRucersMGM2I7SCzeT9nYHls34%3Dpage=1pageSize=20listAll=true_=1383845615692 ===START=== 10.101.255.73 -- GET command=listConfigurationsclusterid=e3ab8dc1-f8df-4a4f-b42b-51867e36ab76response=jsonsessionkey=8CRucersMGM2I7SCzeT9nYHls34%3Dpage=1pageSize=20listAll=true_=1383845615692 2013-11-08 04:24:41,742 ERROR [c.c.a.ApiServer] (catalina-exec-19:ctx-2380ad6b ctx-5d5d232e) unhandled exception executing api command: listConfigurations java.lang.NullPointerException at com.cloud.server.ConfigurationServerImpl.getConfigListByScope(ConfigurationServerImpl.java:778) at com.cloud.server.ManagementServerImpl.searchForConfigurations(ManagementServerImpl.java:1675) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy222.searchForConfigurations(Unknown Source) at org.apache.cloudstack.api.command.admin.config.ListCfgsByCmd.execute(ListCfgsByCmd.java:115) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:322) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:52) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:114) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:111) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at
[jira] [Commented] (CLOUDSTACK-5079) listConfigurations for cluster is resulting in NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825414#comment-13825414 ] Yichi Lu commented on CLOUDSTACK-5079: -- a review request (15633) submitted listConfigurations for cluster is resulting in NPE -- Key: CLOUDSTACK-5079 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5079 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Srikanteswararao Talluri Priority: Critical Fix For: 4.3.0 API issued: http://ms:8080/client/api?command=listConfigurationsclusterid=e3ab8dc1-f8df-4a4f-b42b-51867e36ab76response=jsonsessionkey=8CRucersMGM2I7SCzeT9nYHls34%3Dpage=1pageSize=20listAll=true_=1383845615692 ===START=== 10.101.255.73 -- GET command=listConfigurationsclusterid=e3ab8dc1-f8df-4a4f-b42b-51867e36ab76response=jsonsessionkey=8CRucersMGM2I7SCzeT9nYHls34%3Dpage=1pageSize=20listAll=true_=1383845615692 2013-11-08 04:24:41,742 ERROR [c.c.a.ApiServer] (catalina-exec-19:ctx-2380ad6b ctx-5d5d232e) unhandled exception executing api command: listConfigurations java.lang.NullPointerException at com.cloud.server.ConfigurationServerImpl.getConfigListByScope(ConfigurationServerImpl.java:778) at com.cloud.server.ManagementServerImpl.searchForConfigurations(ManagementServerImpl.java:1675) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy222.searchForConfigurations(Unknown Source) at org.apache.cloudstack.api.command.admin.config.ListCfgsByCmd.execute(ListCfgsByCmd.java:115) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:322) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:52) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:114) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:111) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:73) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at
[jira] [Commented] (CLOUDSTACK-5044) Configuration Framework Issue
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825425#comment-13825425 ] Yichi Lu commented on CLOUDSTACK-5044: -- The source of this bug could be the same one as 5079. Configuration Framework Issue - Key: CLOUDSTACK-5044 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5044 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: Mac OS X 10.8.3 Reporter: Mike Tutkowski Fix For: 4.3.0 When you click on the Settings tab of a cluster, an error is displayed in its table: http://i.imgur.com/k7oPoEp.jpg From the MS console: ERROR [c.c.a.ApiServer] (1243517273@qtp-1404190447-6:ctx-a7d38106 ctx-82029652) unhandled exception executing api command: listConfigurations java.lang.NullPointerException at com.cloud.server.ConfigurationServerImpl.getConfigListByScope(ConfigurationServerImpl.java:778) at com.cloud.server.ManagementServerImpl.searchForConfigurations(ManagementServerImpl.java:1674) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy233.searchForConfigurations(Unknown Source) at org.apache.cloudstack.api.command.admin.config.ListCfgsByCmd.execute(ListCfgsByCmd.java:115) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:322) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:52) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:114) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:111) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:73) 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
[jira] [Created] (CLOUDSTACK-5184) Home Global Settings slow to populate
Yichi Lu created CLOUDSTACK-5184: Summary: Home Global Settings slow to populate Key: CLOUDSTACK-5184 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5184 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Yichi Lu Log into CloudStack GUI. From left pane, click Global Settings. Once clicked, only a very limited items are shown. Each time the right sliding bar is moved to the bottom, again only a limited items are displayed. It would take some efforts in order to see the items whose names start with, say, x, y, z. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4969) Cannot change Host OS preference from xyz - None
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824205#comment-13824205 ] Yichi Lu commented on CLOUDSTACK-4969: -- A review request (15566) submitted. Cannot change Host OS preference from xyz - None - Key: CLOUDSTACK-4969 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4969 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Reporter: Marty Sweet Using the API (or Web Interface) users are unable to change Hosts OS Preference away from an OS to None. Reproduce: 1) Infrastructure Hosts (View All) Click Host Edit 2) Change OS Preference to Ubuntu 3) Save 4) Refresh go back into menu, it is Ubuntu 5) Edit Change OS Preference to None 6) Save 7) Refresh go back into menu, it is Ubuntu Changing from an OS - None does not save. This functionality doesn't work when manipulating the API commands either. The following requests are sent from the WebUI: Changing to Ubuntu: client/api?command=updateHost id=864e1675-92e3-45cd-a184-54d65e61d3da hosttags= osCategoryId=47c65292-32f7-4000-8786-1eb722072cb4 response=json Request sent changing to None: client/api?command=updateHost id=864e1675-92e3-45cd-a184--4d65e61d3da hosttags= response=json It appears that osCategoryId should contain the UUID for the `guest_os_category`, when this is set to 11 (as set for 'None' in my DB), it does not work either. The JSON response from the API simply returns the old value with no errors. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-5137) SNMP test requires successful resolution of build host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820601#comment-13820601 ] Yichi Lu commented on CLOUDSTACK-5137: -- RDP client will fail too. SNMP test requires successful resolution of build host -- Key: CLOUDSTACK-5137 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5137 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Marcus Sorensen Priority: Minor MVN build fails if local machine cannot resolve its host name to an IP. This is common in dev environment or many default OS installs. -- This message was sent by Atlassian JIRA (v6.1#6144)
