[jira] [Resolved] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-7026. -- Resolution: Fixed > mark the test_01_primary_storage_iscsi as test that requires hardware > - > > Key: CLOUDSTACK-7026 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7026 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Bharat Kumar >Assignee: Bharat Kumar > Fix For: 4.4.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6834) [Windows] Feedback Items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052157#comment-14052157 ] ASF subversion and git services commented on CLOUDSTACK-6834: - Commit 4607c26949b6b925fdc0eb2a5253d536dd333439 in cloudstack's branch refs/heads/master from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4607c26 ] Revert "CLOUDSTACK-6834 : 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox" This reverts commit ce5061e107f743e52b23445fd97fcf60d8160ec6. > [Windows] Feedback Items > > > Key: CLOUDSTACK-6834 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6834 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: Future >Reporter: Damodar Reddy T >Assignee: Damodar Reddy T > Fix For: 4.5.0 > > > The feed back items received internally. > 1. Need to add more fields to the database creation wizard > 2. Remove Complete Option > 3. Some description changes words like CloudStack etc > 4. Change Default installation location if possible include version number > 5. Mysql Connector Installer along with other dependecies > 6. Add run Service Checkbox > 7. Add ReadMe checkbox > 8. If possible enable logs for Custom Actions that are executed as part of > installation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051483#comment-14051483 ] ASF subversion and git services commented on CLOUDSTACK-7047: - Commit 29b09b1e21132d1c6c2739dbd0df99d895aef039 in cloudstack's branch refs/heads/4.4 from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=29b09b1 ] CLOUDSTACK-7047: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Changes: - removing unused imports Conflicts: server/src/com/cloud/deploy/DeploymentPlanningManagerImpl.java (cherry picked from commit f37b1524892ab805615dbff2c59e5a1d10c116d3) > DeploymentPlanner should include disabled resources only when the VM owner is > Admin account > --- > > Key: CLOUDSTACK-7047 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Prachi Damle >Assignee: Prachi Damle > Fix For: 4.4.0, 4.5.0 > > > Currently planner includes the disabled resources if caller of the deployVM > API is admin. So if admin calls the API on behalf of a user (by passing in > account and domainid of user) then disabled resources get included in the > planning search. This is not right as the VM owner is a user account and the > VM should not go to disabled resources then. > Fix needed: DeploymentPlanner should include disabled resources only when the > VM owner is Admin account. The disabled resources should be ignored when VM > is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051482#comment-14051482 ] ASF subversion and git services commented on CLOUDSTACK-7047: - Commit b70bd23be37bb7d8fa581b26a0bb6d8c657c9098 in cloudstack's branch refs/heads/4.4 from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b70bd23 ] CLOUDSTACK-7047: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Changes: -DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. (cherry picked from commit 40e28de7275804f4483868ba8a737878ff54fba8) > DeploymentPlanner should include disabled resources only when the VM owner is > Admin account > --- > > Key: CLOUDSTACK-7047 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Prachi Damle >Assignee: Prachi Damle > Fix For: 4.4.0, 4.5.0 > > > Currently planner includes the disabled resources if caller of the deployVM > API is admin. So if admin calls the API on behalf of a user (by passing in > account and domainid of user) then disabled resources get included in the > planning search. This is not right as the VM owner is a user account and the > VM should not go to disabled resources then. > Fix needed: DeploymentPlanner should include disabled resources only when the > VM owner is Admin account. The disabled resources should be ignored when VM > is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6926) Usage service fails to start when java 1.6 is not installed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051420#comment-14051420 ] ASF subversion and git services commented on CLOUDSTACK-6926: - Commit 3bf4c294313eb0bdb9597f0af2cf6b81a8b4 in cloudstack's branch refs/heads/4.3 from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3bf4c29 ] CLOUDSTACK-6926: removed hard coded jdk dirs and setting java home using readlink and dirname Signed-off-by: Sebastien Goasguen > Usage service fails to start when java 1.6 is not installed > --- > > Key: CLOUDSTACK-6926 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6926 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Usage >Affects Versions: 4.2.1 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > > was able to start only after editing JDK_DIRS in /etc/init.d/cloudstack-usage > it is searching only 1.6 java install directories by default -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7062) Creating storage pool failing with xenserver with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051385#comment-14051385 ] ASF subversion and git services commented on CLOUDSTACK-7062: - Commit 8c61566d612700f79b26e4e074502274cd676dcb in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8c61566 ] CLOUDSTACK-7062: Tagging test case with bug Id > Creating storage pool failing with xenserver with NullPointerException > -- > > Key: CLOUDSTACK-7062 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7062 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Storage Controller >Affects Versions: 4.4.0 > Environment: XenServer >Reporter: Gaurav Aradhye > Fix For: 4.4.0 > > > test case related to iscsi failing with "Failed to add data store" and log > shows nullPointerException > Management Server Log: > 2014-07-02 11:32:49,504 DEBUG > [o.a.c.s.d.l.CloudStackPrimaryDataStoreLifeCycleImpl] > (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) > createPool Par > ams @ scheme - iscsi storageHost - 172.16.88.27 hostPath - > /iqn.2006-01.com.openfiler:tsn.b7c10b2d6ab6 port - -1 > 2014-07-02 11:32:49,505 DEBUG [c.c.a.m.DirectAgentAttache] > (DirectAgent-40:ctx-d91132bb) Seq 2-177610710304424049: Executing request > 2014-07-02 11:32:49,509 DEBUG [c.c.s.StorageManagerImpl] > (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) Failed > to add data store: null > java.lang.NullPointerException > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.initialize(CloudStackPrimaryDataStoreLifeCycleImpl.java:263) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:666) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:178) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:163) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:682) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:511) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) > at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) > 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:115) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) > 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) > 2014-07-02 11:32:49,510 INFO
[jira] [Commented] (CLOUDSTACK-6834) [Windows] Feedback Items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051380#comment-14051380 ] ASF subversion and git services commented on CLOUDSTACK-6834: - Commit ce5061e107f743e52b23445fd97fcf60d8160ec6 in cloudstack's branch refs/heads/master from [~damoder.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ce5061e ] CLOUDSTACK-6834 : 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox Signed-off-by: Koushik Das > [Windows] Feedback Items > > > Key: CLOUDSTACK-6834 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6834 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: Future >Reporter: Damodar Reddy T >Assignee: Damodar Reddy T > Fix For: 4.5.0 > > > The feed back items received internally. > 1. Need to add more fields to the database creation wizard > 2. Remove Complete Option > 3. Some description changes words like CloudStack etc > 4. Change Default installation location if possible include version number > 5. Mysql Connector Installer along with other dependecies > 6. Add run Service Checkbox > 7. Add ReadMe checkbox > 8. If possible enable logs for Custom Actions that are executed as part of > installation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7062) Creating storage pool failing with xenserver with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051368#comment-14051368 ] ASF subversion and git services commented on CLOUDSTACK-7062: - Commit f5139f78395146ee99b9e0fdc376351b28c34063 in cloudstack's branch refs/heads/4.4-forward from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f5139f7 ] CLOUDSTACK-7062: Tagging test case with BugId > Creating storage pool failing with xenserver with NullPointerException > -- > > Key: CLOUDSTACK-7062 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7062 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Storage Controller >Affects Versions: 4.4.0 > Environment: XenServer >Reporter: Gaurav Aradhye > Fix For: 4.4.0 > > > test case related to iscsi failing with "Failed to add data store" and log > shows nullPointerException > Management Server Log: > 2014-07-02 11:32:49,504 DEBUG > [o.a.c.s.d.l.CloudStackPrimaryDataStoreLifeCycleImpl] > (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) > createPool Par > ams @ scheme - iscsi storageHost - 172.16.88.27 hostPath - > /iqn.2006-01.com.openfiler:tsn.b7c10b2d6ab6 port - -1 > 2014-07-02 11:32:49,505 DEBUG [c.c.a.m.DirectAgentAttache] > (DirectAgent-40:ctx-d91132bb) Seq 2-177610710304424049: Executing request > 2014-07-02 11:32:49,509 DEBUG [c.c.s.StorageManagerImpl] > (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) Failed > to add data store: null > java.lang.NullPointerException > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.initialize(CloudStackPrimaryDataStoreLifeCycleImpl.java:263) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:666) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:178) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:163) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:682) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:511) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) > at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) > 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:115) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) > 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) > 2014-07-02 11:32:49,510 I
[jira] [Created] (CLOUDSTACK-7062) Creating storage pool failing with xenserver with NullPointerException
Gaurav Aradhye created CLOUDSTACK-7062: -- Summary: Creating storage pool failing with xenserver with NullPointerException Key: CLOUDSTACK-7062 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7062 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Storage Controller Affects Versions: 4.4.0 Environment: XenServer Reporter: Gaurav Aradhye Fix For: 4.4.0 test case related to iscsi failing with "Failed to add data store" and log shows nullPointerException Management Server Log: 2014-07-02 11:32:49,504 DEBUG [o.a.c.s.d.l.CloudStackPrimaryDataStoreLifeCycleImpl] (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) createPool Par ams @ scheme - iscsi storageHost - 172.16.88.27 hostPath - /iqn.2006-01.com.openfiler:tsn.b7c10b2d6ab6 port - -1 2014-07-02 11:32:49,505 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-40:ctx-d91132bb) Seq 2-177610710304424049: Executing request 2014-07-02 11:32:49,509 DEBUG [c.c.s.StorageManagerImpl] (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) Failed to add data store: null java.lang.NullPointerException at org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.initialize(CloudStackPrimaryDataStoreLifeCycleImpl.java:263) at com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:666) at com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:178) at org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:163) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:682) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:511) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) 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:115) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) 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) 2014-07-02 11:32:49,510 INFO [c.c.a.ApiServer] (1501785494@qtp-1004950349-6:ctx-966a5b97 ctx-7e89c3e9 ctx-fcfd86a0) Failed to add data store: null -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7061) Cloudstack web-application: Missing X-Frame-Options header
Glenn created CLOUDSTACK-7061: - Summary: Cloudstack web-application: Missing X-Frame-Options header Key: CLOUDSTACK-7061 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7061 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Glenn Priority: Critical Provides Clickjacking protection. Values: deny - no rendering within a frame, sameorigin - no rendering if origin mismatch, allow-from: DOMAIN - allow rendering if framed by frame loaded from DOMAIN Advice: Please add the following header: X-Frame-Options: sameorigin Overall score: High -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6999) Creating storage pool failing with simulator with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye closed CLOUDSTACK-6999. -- Resolution: Not a Problem > Creating storage pool failing with simulator with NullPointerException > -- > > Key: CLOUDSTACK-6999 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6999 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Simulator >Affects Versions: 4.4.0 > Environment: Simulator >Reporter: Gaurav Aradhye > Labels: automation, simulator > Fix For: 4.4.0 > > > test_01_primary_storage_iscsi failing due to this. > Log: > 2014-06-25 20:15:59,952 DEBUG > [o.a.c.s.d.l.CloudStackPrimaryDataStoreLifeCycleImpl] > (1620500439@qtp-937650164-7:ctx-8360ebb1 ctx-7a8161ac ctx-3aaf2686) > createPool Para > ms @ scheme - iscsi storageHost - 172.16.88.27 hostPath - > /iqn.2006-01.com.openfiler:tsn.b7c10b2d6ab6 port - -1 > 2014-06-25 20:15:59,972 DEBUG [c.c.a.ApiServlet] > (277793082@qtp-937650164-8:ctx-beafdd28 ctx-f3cc7056 ctx-9b4f7c82) ===END=== > 172.16.88.7 -- GET username=test-accoun > t-TestReleaseIP-test_delete_account-806IFK&domainid=5caac9be-fcde-11e3-89a0-00163e0af42c&firstname=test&lastname=test&email=test-account%40test.com&apiKey=js8xe3_Av3Yz > nD5n-7c1_atVWE8RTzu0HSmGUsjfWNyXigOWgB8FL0VBNgIv7S9U0wm7vYFb2gmQwY9O3ZaV3w&command=createAccount&accounttype=2&signature=vopZJ5wHC0zIurr1geOWk%2FupGVo%3D&response=json > 2014-06-25 20:15:59,977 DEBUG [c.c.s.StorageManagerImpl] > (1620500439@qtp-937650164-7:ctx-8360ebb1 ctx-7a8161ac ctx-3aaf2686) Failed to > add data store: null > java.lang.NullPointerException > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.initialize(CloudStackPrimaryDataStoreLifeCycleImpl.java:263) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:666) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:178) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:163) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:682) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:511) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) > at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) > 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:115) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) > 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
[jira] [Commented] (CLOUDSTACK-6999) Creating storage pool failing with simulator with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051296#comment-14051296 ] Gaurav Aradhye commented on CLOUDSTACK-6999: It has been marked with "required_hardware". Not an issue now. Closing this. > Creating storage pool failing with simulator with NullPointerException > -- > > Key: CLOUDSTACK-6999 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6999 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Simulator >Affects Versions: 4.4.0 > Environment: Simulator >Reporter: Gaurav Aradhye > Labels: automation, simulator > Fix For: 4.4.0 > > > test_01_primary_storage_iscsi failing due to this. > Log: > 2014-06-25 20:15:59,952 DEBUG > [o.a.c.s.d.l.CloudStackPrimaryDataStoreLifeCycleImpl] > (1620500439@qtp-937650164-7:ctx-8360ebb1 ctx-7a8161ac ctx-3aaf2686) > createPool Para > ms @ scheme - iscsi storageHost - 172.16.88.27 hostPath - > /iqn.2006-01.com.openfiler:tsn.b7c10b2d6ab6 port - -1 > 2014-06-25 20:15:59,972 DEBUG [c.c.a.ApiServlet] > (277793082@qtp-937650164-8:ctx-beafdd28 ctx-f3cc7056 ctx-9b4f7c82) ===END=== > 172.16.88.7 -- GET username=test-accoun > t-TestReleaseIP-test_delete_account-806IFK&domainid=5caac9be-fcde-11e3-89a0-00163e0af42c&firstname=test&lastname=test&email=test-account%40test.com&apiKey=js8xe3_Av3Yz > nD5n-7c1_atVWE8RTzu0HSmGUsjfWNyXigOWgB8FL0VBNgIv7S9U0wm7vYFb2gmQwY9O3ZaV3w&command=createAccount&accounttype=2&signature=vopZJ5wHC0zIurr1geOWk%2FupGVo%3D&response=json > 2014-06-25 20:15:59,977 DEBUG [c.c.s.StorageManagerImpl] > (1620500439@qtp-937650164-7:ctx-8360ebb1 ctx-7a8161ac ctx-3aaf2686) Failed to > add data store: null > java.lang.NullPointerException > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.initialize(CloudStackPrimaryDataStoreLifeCycleImpl.java:263) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:666) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:178) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:163) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:682) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:511) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) > at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) > 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:115) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) > 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(SelectChannelEndPo
[jira] [Created] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs
Srikanteswararao Talluri created CLOUDSTACK-7053: Summary: [Automation] Tasks for writing automated test cases for few product bugs Key: CLOUDSTACK-7053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-7051: --- Assignee: Kishan Kavala > [Automation] Failed to create SSVM and CPVM in KVM, > > > Key: CLOUDSTACK-7051 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.5.0 > Environment: RHEL : 6.3 > build : 4.5 >Reporter: Rayees Namathponnan >Assignee: Kishan Kavala >Priority: Blocker > Fix For: 4.5.0 > > Attachments: agent.rar, management-server.rar > > > SSVM and CPVM not creating with latest 4.5 build, copy command failing form > agent observed below error in agent log, > 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Execution is successful. > 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7 > 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 > size=262144 encryption=off clus > ter_size=65536 preallocation='off' > 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Executing: qemu-img info --o > utput json > /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8 > 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Exit value is 1 > 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) info: invalid option -- '-'q > emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: > qemu-img command [command options]QEMU d > isk image utilityCommand syntax: check [-f fmt] filename create [-f fmt] > [-o options] filename [size] commi > t [-f fmt] [-t cache] filename convert [-c] [-p] [-f fmt] [-t cache] [-O > output_fmt] [-o options] [-S sparse_ > size] filename [filename2 [...]] output_filename info [-f fmt] filename > snapshot [-l | -a snapshot | -c snap > shot | -d snapshot] filename rebase [-f fmt] [-t cache] [-p] [-u] -b > backing_file [-F backing_fmt] filename > resize filename [+ | -]sizeCommand parameters: 'filename' is a disk image > filename 'fmt' is the disk image f > ormat. It is guessed automatically in most cases 'cache' is the cache mode > used to write the output disk imag > e, the validoptions are: 'none', 'writeback' (default), 'writethrough' > and 'unsafe' 'size' is the disk im > age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' > (megabyte, 1024k), 'G' (gigabyte, 102 > 4M)and T (terabyte, 1024G) are supported. 'b' is ignored. > 'output_filename' is the destination disk image > filename 'output_fmt' is the destination format 'options' is a comma > separated list of format specific opti > ons in aname=value format. Use -o ? for an overview of the options > supported by theused format '-c' i > ndicates that target image must be compressed (qcow format only) '-u' > enables unsafe rebasing. It is assumed > that old and new backing file match exactly. The image doesn't need a > working backing file before > rebasing in this case (useful for renaming the backing file) '-h' with or > without a command shows this help a > nd lists the supported formats '-p' show progress of command (only certain > commands) '-S' indicates the cons > ecutive number of bytes that must contain only zeros for qemu-img to > create a sparse image during conver > sionParameters to snapshot subcommand: 'snapshot' is the name of the > snapshot to create, apply or delete '-a > ' applies a snapshot (revert disk to saved state) '-c' creates a snapshot > '-d' deletes a snapshot '-l' lists all snapshots in the given imageSupported > formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels > nbd blkdebug host_cdrom host_floppy host_device file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-6360) Usage server failed to start with 4.4 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi reopened CLOUDSTACK-6360: - In addition to packaging/centos63/cloud-usage.rc, this fix needs to be there in packaging/debian/init/cloud-usage for debian packages > Usage server failed to start with 4.4 build > --- > > Key: CLOUDSTACK-6360 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6360 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0, 4.4.0 > Environment: 4.4 Build >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.4.0 > > > step 1 : Create 4.4 build and install usage server > step 2 : start usage sever > Result > Failed to start usage server with below error > java.lang.UnsupportedClassVersionError: com/cloud/usage/UsageServer : > Unsupported major.minor version 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:634) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) > at java.net.URLClassLoader.access$000(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:212) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:205) > at java.lang.ClassLoader.loadClass(ClassLoader.java:321) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > at > org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:151) > 08/04/2014 12:32:19 5982 jsvc.exec error: Cannot load daemon > 08/04/2014 12:32:19 5980 jsvc.exec error: Service exit with a return value of > 3 > cloudstack-usage.err (END) > We already defined 4.4 support with JAVA IP, but usage server trying to start > with 1.6 > we need to fix this in vi /etc/rc.d/init.d/cloudstack-usage > # The first existing directory is used for JAVA_HOME (if JAVA_HOME is not > defined in $DEFAULT) > JDK_DIRS="/usr/lib/jvm/java-6-openjdk /usr/lib/jvm/java-6-openjdk-i386 > /usr/lib/jvm/java-6-openjdk-amd64 /usr/lib/jvm/java-6-sun > /usr/lib/jvm/jre-1.6.0 /usr/lib/j2sdk1.5-sun /usr/lib/jre-openjdk" -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6920) Support listing of LBHealthcheck policy with LBHealthcheck policy ID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-6920. Resolution: Fixed > Support listing of LBHealthcheck policy with LBHealthcheck policy ID > > > Key: CLOUDSTACK-6920 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6920 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.4.0 >Reporter: Rajesh Battala >Assignee: Rajesh Battala > Fix For: 4.4.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7037) Unable to add new vm/service to existing LB rule of SSL protocol
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-7037. Resolution: Fixed > Unable to add new vm/service to existing LB rule of SSL protocol > > > Key: CLOUDSTACK-7037 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7037 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.5.0 >Reporter: Rajesh Battala >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.5.0 > > > Exception is thrown from nitro api when try to add new vm to LB rule. > INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-20:ctx-eb12ce6b job-82) > Add job-82 into job monitoring > ERROR [c.c.n.r.NetscalerResource] (DirectAgent-418:ctx-6caefe76) Failed to > execute LoadBalancerConfigCommand due to > com.citrix.netscaler.nitro.exception.nitro_exception: Operation not permitted > at > com.citrix.netscaler.nitro.resource.base.base_resource.put_data(base_resource.java:693) > at > com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:196) > at > com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:180) > at > com.citrix.netscaler.nitro.resource.config.lb.lbvserver_service_binding.add(lbvserver_service_binding.java:256) > at > com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:650) > at > com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427) > at > com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:416) > at > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > 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 > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6891) [Automation] - port 8096 is being used when executing the suite when admin’s keys are not generated before execution of the suite.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Ojha reassigned CLOUDSTACK-6891: -- Assignee: Sonal Ojha > [Automation] - port 8096 is being used when executing the suite when admin’s > keys are not generated before execution of the suite. > -- > > Key: CLOUDSTACK-6891 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6891 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.4.0 > Environment: Marvin builds from 4.4-forward branch >Reporter: Sangeetha Hariharan >Assignee: Sonal Ojha > > port 8096 is being used for the entire suite in the following scenario: > api/secret key is not present for the admin user and as part of executing a > test suite , we generate the secret and api key for admin user.This happens > when the very first test suite is executed after the setup is created and > admin’s keys are not generated yet. > In __createApiClient method of cloudstackTestClient.py , mgmt_details.port is > not set explicitly to “8080” , when there is a need to generate the keys. In > such cases , we default to using port “8096” which is defined as part of the > configuration file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6191) Volume provisioning type option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051138#comment-14051138 ] Ilia Shakitko edited comment on CLOUDSTACK-6191 at 7/3/14 7:15 AM: --- [~ynojima] When I was testing, I build, start it from the source (run the management with jetty), also master branch, also 14.04. Maybe it'll help to reproduce was (Author: svscorp): [~ynojima] When I was testing, I build, start it from the source (run the management with jetty), also master branch, also 14.04. May be it'll help to reproduce > Volume provisioning type option > --- > > Key: CLOUDSTACK-6191 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Management Server >Reporter: Yoshikazu Nojima >Assignee: Yoshikazu Nojima >Priority: Minor > Fix For: 4.5.0 > > > Thin provisioning of a volume saves consumption of a storage, and fat > provisioning minimizes IOPS performance overhead. > This feature implements a global setting to provide users an option to select > how to provision volumes. > Design doc: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6191) Volume provisioning type option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051138#comment-14051138 ] Ilia Shakitko commented on CLOUDSTACK-6191: --- [~ynojima] When I was testing, I build, start it from the source (run the management with jetty), also master branch, also 14.04. May be it'll help to reproduce > Volume provisioning type option > --- > > Key: CLOUDSTACK-6191 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Management Server >Reporter: Yoshikazu Nojima >Assignee: Yoshikazu Nojima >Priority: Minor > Fix For: 4.5.0 > > > Thin provisioning of a volume saves consumption of a storage, and fat > provisioning minimizes IOPS performance overhead. > This feature implements a global setting to provide users an option to select > how to provision volumes. > Design doc: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option -- This message was sent by Atlassian JIRA (v6.2#6252)
