[jira] [Created] (CLOUDSTACK-8068) test_ps_project_iimits.py - 'not all arguments converted during string formatting' - test_ps_project_limits.py
Gaurav Aradhye created CLOUDSTACK-8068: -- Summary: test_ps_project_iimits.py - 'not all arguments converted during string formatting' - test_ps_project_limits.py Key: CLOUDSTACK-8068 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8068 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8063) list secondary Ips information in VM response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-8063. -- Resolution: Fixed Fix Version/s: 4.6.0 > list secondary Ips information in VM response > - > > Key: CLOUDSTACK-8063 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8063 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou >Priority: Minor > Fix For: 4.6.0 > > > and display it on UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8063) list secondary Ips information in VM response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243881#comment-14243881 ] ASF subversion and git services commented on CLOUDSTACK-8063: - Commit dcb7fcc6df6137b143e6809e67429ed24a0ae19e in cloudstack's branch refs/heads/master from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dcb7fcc ] CLOUDSTACK-8063: list secondary Ips information in VM response > list secondary Ips information in VM response > - > > Key: CLOUDSTACK-8063 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8063 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou >Priority: Minor > Fix For: 4.6.0 > > > and display it on UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8068) test_ps_project_iimits.py - 'not all arguments converted during string formatting' - test_ps_project_limits.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-8068: --- Status: Reviewable (was: In Progress) > test_ps_project_iimits.py - 'not all arguments converted during string > formatting' - test_ps_project_limits.py > -- > > Key: CLOUDSTACK-8068 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8068 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8064) UpdatePortForwardingRuleCmd implementation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243901#comment-14243901 ] ASF subversion and git services commented on CLOUDSTACK-8064: - Commit fec31d53c362293087942f20fed974104fcbaa8b in cloudstack's branch refs/heads/master from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fec31d5 ] CLOUDSTACK-8064: UpdatePortForwardingRuleCmd implementation > UpdatePortForwardingRuleCmd implementation > -- > > Key: CLOUDSTACK-8064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > > it is not implemented -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8064) UpdatePortForwardingRuleCmd implementation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-8064. -- Resolution: Fixed Fix Version/s: 4.6.0 > UpdatePortForwardingRuleCmd implementation > -- > > Key: CLOUDSTACK-8064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.6.0 > > > it is not implemented -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8055) Tagging test cases which can't be run on simulator accordingly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-8055: --- Status: Reviewable (was: In Progress) > Tagging test cases which can't be run on simulator accordingly > -- > > Key: CLOUDSTACK-8055 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8055 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test cases which can't be run on simulator should be tagged accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8062) test_multiple_ip_ranges.py - Fix the test case to avoid using same vlan IP range in each test case
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye resolved CLOUDSTACK-8062. Resolution: Fixed > test_multiple_ip_ranges.py - Fix the test case to avoid using same vlan IP > range in each test case > -- > > Key: CLOUDSTACK-8062 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8062 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > Each test case in this test suite uses the same vlan IP range, adds it and > deletes it. In some cases, the vlan IP range deletion fails due to this > operation. > Change the test case to use different vlan IP range each time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8057) test_dedicate_guest_vlan_ranges.TestDeleteVlanRange.test_04_dedicate_guest_vlan_in_project - Mark test as invalid
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye resolved CLOUDSTACK-8057. Resolution: Fixed > test_dedicate_guest_vlan_ranges.TestDeleteVlanRange.test_04_dedicate_guest_vlan_in_project > - Mark test as invalid > - > > Key: CLOUDSTACK-8057 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8057 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test case dedicates the vlan range to account but creates guest network > in project, and then checks if the vlan of the network is from dedicated > range. > This is an invalid scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8058) test_reset_ssh_keypair.py - test cases failing on EIP setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye resolved CLOUDSTACK-8058. Resolution: Fixed > test_reset_ssh_keypair.py - test cases failing on EIP setup > --- > > Key: CLOUDSTACK-8058 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8058 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The publicIP of the VM changes on EIP setup after stop and start operation. > Hence it is necessary that on such setup, new publicip should be used for the > SSH. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8021) Remove hard coded host password from test cases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye resolved CLOUDSTACK-8021. Resolution: Fixed > Remove hard coded host password from test cases > --- > > Key: CLOUDSTACK-8021 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8021 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > Many test cases use "host_password" from test_data.py, while it should read > data from configurableData section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-255) Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd
[ https://issues.apache.org/jira/browse/CLOUDSTACK-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243937#comment-14243937 ] ASF subversion and git services commented on CLOUDSTACK-255: Commit c9d492d7140dd53f1630bc5ea14b948184233612 in cloudstack's branch refs/heads/master from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c9d492d ] CLOUDSTACK-255: fix NPE in createPortForwardingRule due to no PortForwarding provider > Null pointer exception while creating portforwarding rule after performing > UpdateNetworkCmd > > > Key: CLOUDSTACK-255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Sailaja Mada >Assignee: Ram Ganesh > Fix For: 4.4.3 > > Attachments: api-server.log, management-server-pf.log > > > Steps : > 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server. > 2. Create new account > 3. Create Network offering1 with Redundant Router enabled , > Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, > Lb, Dhcp, StaticNat > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false > 4. Create Network with the above offering. > 5. Deploy instance with this network > 6. Both Routers and instance got deployed. > 7. Configure LB rule with 22 port , Enable VPN , Once the key is generated > , disable VPN > 8. Create Network offering 2 with Single Router and > Supported ServicesPortForwarding, SourceNat, Firewall, Dns, Dhcp > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > false > 9. Edit Network details and update the Network offering 1 to Network offering > 2. > 10.It created new Router and deleted Redundant Routers. LB Rules are not > deleted. > 11. Now tried to create Port forwarding Rule with 22 . > Observation: > It failed with Null Pointer exception : > 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] > (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd: > java.lang.NullPointerException > at > com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863) > at > com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895) > at > com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205) > at > com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231) > at > com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > 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 > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExec
[jira] [Resolved] (CLOUDSTACK-255) Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd
[ https://issues.apache.org/jira/browse/CLOUDSTACK-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-255. - Resolution: Fixed Fix Version/s: 4.6.0 4.5.0 > Null pointer exception while creating portforwarding rule after performing > UpdateNetworkCmd > > > Key: CLOUDSTACK-255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Sailaja Mada >Assignee: Ram Ganesh > Fix For: 4.5.0, 4.6.0, 4.4.3 > > Attachments: api-server.log, management-server-pf.log > > > Steps : > 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server. > 2. Create new account > 3. Create Network offering1 with Redundant Router enabled , > Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, > Lb, Dhcp, StaticNat > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false > 4. Create Network with the above offering. > 5. Deploy instance with this network > 6. Both Routers and instance got deployed. > 7. Configure LB rule with 22 port , Enable VPN , Once the key is generated > , disable VPN > 8. Create Network offering 2 with Single Router and > Supported ServicesPortForwarding, SourceNat, Firewall, Dns, Dhcp > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > false > 9. Edit Network details and update the Network offering 1 to Network offering > 2. > 10.It created new Router and deleted Redundant Routers. LB Rules are not > deleted. > 11. Now tried to create Port forwarding Rule with 22 . > Observation: > It failed with Null Pointer exception : > 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] > (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd: > java.lang.NullPointerException > at > com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863) > at > com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895) > at > com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205) > at > com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231) > at > com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > 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 > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > 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:679) > 2012-10-04 13:17:21,003 DEBUG [agent.manager.AgentManagerImpl] > (AgentManager-Handler-7:null) Ping from 4 > Fire bug log: > "NetworkError: 530 - > http://10.102.125.211:8080/c
[jira] [Commented] (CLOUDSTACK-255) Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd
[ https://issues.apache.org/jira/browse/CLOUDSTACK-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243939#comment-14243939 ] ASF subversion and git services commented on CLOUDSTACK-255: Commit 10248515d798f6186be37ae4eec7c0848483d029 in cloudstack's branch refs/heads/4.4 from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1024851 ] CLOUDSTACK-255: fix NPE in createPortForwardingRule due to no PortForwarding provider (cherry picked from commit c9d492d7140dd53f1630bc5ea14b948184233612) > Null pointer exception while creating portforwarding rule after performing > UpdateNetworkCmd > > > Key: CLOUDSTACK-255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Sailaja Mada >Assignee: Ram Ganesh > Fix For: 4.5.0, 4.6.0, 4.4.3 > > Attachments: api-server.log, management-server-pf.log > > > Steps : > 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server. > 2. Create new account > 3. Create Network offering1 with Redundant Router enabled , > Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, > Lb, Dhcp, StaticNat > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false > 4. Create Network with the above offering. > 5. Deploy instance with this network > 6. Both Routers and instance got deployed. > 7. Configure LB rule with 22 port , Enable VPN , Once the key is generated > , disable VPN > 8. Create Network offering 2 with Single Router and > Supported ServicesPortForwarding, SourceNat, Firewall, Dns, Dhcp > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > false > 9. Edit Network details and update the Network offering 1 to Network offering > 2. > 10.It created new Router and deleted Redundant Routers. LB Rules are not > deleted. > 11. Now tried to create Port forwarding Rule with 22 . > Observation: > It failed with Null Pointer exception : > 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] > (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd: > java.lang.NullPointerException > at > com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863) > at > com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895) > at > com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205) > at > com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231) > at > com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > 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 > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(T
[jira] [Commented] (CLOUDSTACK-255) Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd
[ https://issues.apache.org/jira/browse/CLOUDSTACK-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243938#comment-14243938 ] ASF subversion and git services commented on CLOUDSTACK-255: Commit 76dc20a0ee199d0b2d15f7ffe21fc9c45c72e9cc in cloudstack's branch refs/heads/4.5 from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=76dc20a ] CLOUDSTACK-255: fix NPE in createPortForwardingRule due to no PortForwarding provider (cherry picked from commit c9d492d7140dd53f1630bc5ea14b948184233612) > Null pointer exception while creating portforwarding rule after performing > UpdateNetworkCmd > > > Key: CLOUDSTACK-255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Sailaja Mada >Assignee: Ram Ganesh > Fix For: 4.5.0, 4.6.0, 4.4.3 > > Attachments: api-server.log, management-server-pf.log > > > Steps : > 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server. > 2. Create new account > 3. Create Network offering1 with Redundant Router enabled , > Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, > Lb, Dhcp, StaticNat > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false > 4. Create Network with the above offering. > 5. Deploy instance with this network > 6. Both Routers and instance got deployed. > 7. Configure LB rule with 22 port , Enable VPN , Once the key is generated > , disable VPN > 8. Create Network offering 2 with Single Router and > Supported ServicesPortForwarding, SourceNat, Firewall, Dns, Dhcp > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > false > 9. Edit Network details and update the Network offering 1 to Network offering > 2. > 10.It created new Router and deleted Redundant Routers. LB Rules are not > deleted. > 11. Now tried to create Port forwarding Rule with 22 . > Observation: > It failed with Null Pointer exception : > 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] > (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd: > java.lang.NullPointerException > at > com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863) > at > com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895) > at > com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205) > at > com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231) > at > com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > 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 > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(T
[jira] [Assigned] (CLOUDSTACK-255) Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd
[ https://issues.apache.org/jira/browse/CLOUDSTACK-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou reassigned CLOUDSTACK-255: --- Assignee: Wei Zhou (was: Ram Ganesh) > Null pointer exception while creating portforwarding rule after performing > UpdateNetworkCmd > > > Key: CLOUDSTACK-255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Sailaja Mada >Assignee: Wei Zhou > Fix For: 4.5.0, 4.6.0, 4.4.3 > > Attachments: api-server.log, management-server-pf.log > > > Steps : > 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server. > 2. Create new account > 3. Create Network offering1 with Redundant Router enabled , > Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, > Lb, Dhcp, StaticNat > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false > 4. Create Network with the above offering. > 5. Deploy instance with this network > 6. Both Routers and instance got deployed. > 7. Configure LB rule with 22 port , Enable VPN , Once the key is generated > , disable VPN > 8. Create Network offering 2 with Single Router and > Supported ServicesPortForwarding, SourceNat, Firewall, Dns, Dhcp > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > false > 9. Edit Network details and update the Network offering 1 to Network offering > 2. > 10.It created new Router and deleted Redundant Routers. LB Rules are not > deleted. > 11. Now tried to create Port forwarding Rule with 22 . > Observation: > It failed with Null Pointer exception : > 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] > (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd: > java.lang.NullPointerException > at > com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863) > at > com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895) > at > com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205) > at > com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231) > at > com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > 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 > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > 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:679) > 2012-10-04 13:17:21,003 DEBUG [agent.manager.AgentManagerImpl] > (AgentManager-Handler-7:null) Ping from 4 > Fire bug log: > "NetworkError: 530 - > http://10.102.125.211:8080/client/api?command=createPortFo
[jira] [Closed] (CLOUDSTACK-5494) the dns resolver servers on the VRs are open to the world
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-5494. Resolution: Duplicate This issue has been already fixed by Sheng Yang https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a554ebd > the dns resolver servers on the VRs are open to the world > - > > Key: CLOUDSTACK-5494 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5494 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0, 4.3.0 >Reporter: Wei Zhou >Assignee: Jayapal Reddy >Priority: Critical > Labels: security > Fix For: Future > > > Currently the port 53 (tcp and udp) on virtual routers are open, so everyone > on the internet can visit the dns service on virtual routers. This may cause > overload and security issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8014) Failed to create a volume from snapshot - Discrepency in the resource count ?
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243978#comment-14243978
]
France commented on CLOUDSTACK-8014:
Hi Rohit,
thank you again for your time. It is much appreciated.
Before I "undelete" that snapshot in DB, please answer this.
If this was the case, should not creating a template from this snapshot also
fail (due to deleted template)?
In my case id does not. Only when creating volume we get a failure.
> Failed to create a volume from snapshot - Discrepency in the resource count ?
> -
>
> Key: CLOUDSTACK-8014
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8014
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.1
>Reporter: France
>Assignee: Rohit Yadav
>
> As sent to mailing list:
> Hi all.
> We are on XS 6.0.2+Hotfixes and CS 4.3.1.
> (All errors we are getting nowadays have come up only after upgrade from
> 4.1.1, 4.1.1 worked perfectly.)
> After successfully creating s snapshot, I want to create a volume from it, so
> it can be downloaded offsite.
> After clicking “Create volume” I get an error Failed to create a volume.
> If i got to list of volumes, there is a volume with name as defined, but
> Status is empty, and only buttons for attach and destroy exist.
> I have taken a look at catalina.out and management-server.log. Here is the
> log detailing a failure.
> Can you see the problem? How should I fix it? Please advise me.
> Should I create a bug report?
> I have also manually checked space on all storages and it seems there is LOTS
> of free space. Resources based on CS Web GUI are:
> Primary Storage Allocated 15%
> Secondary Storage 5%
> 2014-12-03 12:20:42,493 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-2d51baa2) Zone 1 is ready to launch console proxy
> 2014-12-03 12:20:42,580 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-53354d18) Zone 1 is ready to launch secondary storage VM
> 2014-12-03 12:20:42,894 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-108:ctx-a228ce49) ===START=== 111.client.ip.111 -- GET
> command=listZones&available=true&response=json&sessionkey=CENSORED%3D&_=1417605814964
> 2014-12-03 12:20:42,909 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-108:ctx-a228ce49 ctx-74e696ca) ===END=== 111.client.ip.111 --
> GET
> command=listZones&available=true&response=json&sessionkey=CENSORED%3D&_=1417605814964
> 2014-12-03 12:20:46,482 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-107:ctx-4a28e57c) ===START=== 111.client.ip.111 -- GET
> command=createVolume&response=json&sessionkey=CENSORED%3D&snapshotid=49e4bba9-844d-4b7b-aca2-95a318f17dc4&name=testbrisi567&_=1417605818552
> 2014-12-03 12:20:46,490 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-107:ctx-4a28e57c ctx-d7a11540) Access to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,494 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-107:ctx-4a28e57c ctx-d7a11540) Access to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,507 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-107:ctx-4a28e57c ctx-d7a11540) Access to
> com.cloud.storage.SnapshotVO$$EnhancerByCGLIB$$3490cea0@60c95391 granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,571 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-166:ctx-d915e890) Add job-2804 into job monitoring
> 2014-12-03 12:20:46,571 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-166:ctx-d915e890) Executing AsyncJobVO {id:2804, userId: 59,
> accountId: 60, instanceType: Volume, instanceId: 617, cmd:
> org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd, cmdInfo:
> {"id":"617","response":"json","sessionkey":"CENSORED\u003d","cmdEventType":"VOLUME.CREATE","ctxUserId":"59","snapshotid":"49e4bba9-844d-4b7b-aca2-95a318f17dc4","name":"testbrisi567","httpmethod":"GET","_":"1417605818552","ctxAccountId":"60","ctxStartEventId":"62488"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 95545481387, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-12-03 12:20:46,577 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-166:ctx-d915e890 ctx-d7a11540) Access to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,578 DEBUG [o.a.c.f.j.i.AsyncJobManage
[jira] [Created] (CLOUDSTACK-8069) component.test_tags.TestResourceTags.test_15_project_tag failing while listing tags
Gaurav Aradhye created CLOUDSTACK-8069: -- Summary: component.test_tags.TestResourceTags.test_15_project_tag failing while listing tags Key: CLOUDSTACK-8069 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8069 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 Test case failed while listing tags because it passed projectid instead of resourceIds parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8069) component.test_tags.TestResourceTags.test_15_project_tag failing while listing tags
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-8069: --- Status: Reviewable (was: In Progress) > component.test_tags.TestResourceTags.test_15_project_tag failing while > listing tags > --- > > Key: CLOUDSTACK-8069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8069 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > Test case failed while listing tags because it passed projectid instead of > resourceIds parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8055) Tagging test cases which can't be run on simulator accordingly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244091#comment-14244091 ] ASF subversion and git services commented on CLOUDSTACK-8055: - Commit d2ed5fb9a3d8ac615e7fc8dbaa59ee3c516fcf93 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d2ed5fb ] CLOUDSTACK-8055: Tagging test cases which can't be run on simulator accordingly Signed-off-by: SrikanteswaraRao Talluri > Tagging test cases which can't be run on simulator accordingly > -- > > Key: CLOUDSTACK-8055 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8055 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test cases which can't be run on simulator should be tagged accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8055) Tagging test cases which can't be run on simulator accordingly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244096#comment-14244096 ] ASF subversion and git services commented on CLOUDSTACK-8055: - Commit 47ee7c0319351267ff5370a20ec5e1a66583f688 in cloudstack's branch refs/heads/4.5 from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=47ee7c0 ] CLOUDSTACK-8055: Tagging test cases which can't be run on simulator accordingly Signed-off-by: SrikanteswaraRao Talluri > Tagging test cases which can't be run on simulator accordingly > -- > > Key: CLOUDSTACK-8055 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8055 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test cases which can't be run on simulator should be tagged accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8068) test_ps_project_iimits.py - 'not all arguments converted during string formatting' - test_ps_project_limits.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244123#comment-14244123 ] ASF subversion and git services commented on CLOUDSTACK-8068: - Commit 44d295e5c0ae2ecf8a6b0e6abf32fa665db8e83e in cloudstack's branch refs/heads/4.5 from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=44d295e ] CLOUDSTACK-8068: Fixing test script issue in test_ps_project_limits.py Signed-off-by: SrikanteswaraRao Talluri > test_ps_project_iimits.py - 'not all arguments converted during string > formatting' - test_ps_project_limits.py > -- > > Key: CLOUDSTACK-8068 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8068 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8068) test_ps_project_iimits.py - 'not all arguments converted during string formatting' - test_ps_project_limits.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244124#comment-14244124 ] ASF subversion and git services commented on CLOUDSTACK-8068: - Commit fab005478286f188208e287e6b5c0fba044100cd in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fab0054 ] CLOUDSTACK-8068: Fixing test script issue in test_ps_project_limits.py Signed-off-by: SrikanteswaraRao Talluri > test_ps_project_iimits.py - 'not all arguments converted during string > formatting' - test_ps_project_limits.py > -- > > Key: CLOUDSTACK-8068 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8068 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8055) Tagging test cases which can't be run on simulator accordingly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244126#comment-14244126 ] ASF subversion and git services commented on CLOUDSTACK-8055: - Commit ff15320a4e0bd11d90b799e9a2ff24d91750bfc6 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ff15320 ] CLOUDSTACK-8055: Tagging test cases which can't be run on simulator accordingly Signed-off-by: SrikanteswaraRao Talluri > Tagging test cases which can't be run on simulator accordingly > -- > > Key: CLOUDSTACK-8055 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8055 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test cases which can't be run on simulator should be tagged accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8055) Tagging test cases which can't be run on simulator accordingly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244128#comment-14244128 ] ASF subversion and git services commented on CLOUDSTACK-8055: - Commit ecbeb003ec94149adfeb8234f11979b5d99fba7b in cloudstack's branch refs/heads/4.5 from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ecbeb00 ] CLOUDSTACK-8055: Tagging test cases which can't be run on simulator accordingly Signed-off-by: SrikanteswaraRao Talluri > Tagging test cases which can't be run on simulator accordingly > -- > > Key: CLOUDSTACK-8055 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8055 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test cases which can't be run on simulator should be tagged accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7882) SSH Keypair Creation/Selection in UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244134#comment-14244134 ] ASF subversion and git services commented on CLOUDSTACK-7882: - Commit 19e99848c83eca52e5bb980cd6d0632ca73c5525 in cloudstack's branch refs/heads/master from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=19e9984 ] CLOUDSTACK-7882: SSH Keypair Creation/Selection in UI Thanks Ilia Shakitko for the porting and testing. > SSH Keypair Creation/Selection in UI > > > Key: CLOUDSTACK-7882 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7882 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 > Environment: CloudStack 4.4.0 w/ KVM Hypervisor on Ubuntu 14.04 LTS >Reporter: Logan B >Assignee: Wei Zhou >Priority: Minor > Fix For: 4.5.0, 4.6.0 > > > Currently the API allows for creating SSH keypairs, and specifying keypairs > to use when deploying a VM (if the correct script is installed in the > template). > I would suggest adding a section in the UI (perhaps as a drop down option in > the instances menu) to create SSH keypairs. I would then suggest adding an > option in the Instance Wizard to select a keypair to inject into the instance > upon creation. > It may also be worth adding a button to the instance menu to inject a new > keypair upon reboot (like we have for password resets now). This could be > enabled/disabled with a template flag (e.g., "SSH Key Enabled," like the > "Password Enabled" flag we have now) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8069) component.test_tags.TestResourceTags.test_15_project_tag failing while listing tags
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244132#comment-14244132 ] ASF subversion and git services commented on CLOUDSTACK-8069: - Commit e791e8ec6d6484c5ea7853bf7e8184103846a75e in cloudstack's branch refs/heads/4.5 from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e791e8e ] CLOUDSTACK-8069: Fixed test script in test_tags.py Signed-off-by: SrikanteswaraRao Talluri > component.test_tags.TestResourceTags.test_15_project_tag failing while > listing tags > --- > > Key: CLOUDSTACK-8069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8069 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > Test case failed while listing tags because it passed projectid instead of > resourceIds parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8069) component.test_tags.TestResourceTags.test_15_project_tag failing while listing tags
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244138#comment-14244138 ] ASF subversion and git services commented on CLOUDSTACK-8069: - Commit 9c7f50aaac83313d7f3e71ddd5b83a001402d7f7 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9c7f50a ] CLOUDSTACK-8069: Fixed test script in test_tags.py Signed-off-by: SrikanteswaraRao Talluri > component.test_tags.TestResourceTags.test_15_project_tag failing while > listing tags > --- > > Key: CLOUDSTACK-8069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8069 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > Test case failed while listing tags because it passed projectid instead of > resourceIds parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
Rohit Yadav created CLOUDSTACK-8070: --- Summary: Upgrade to 4.3.2 from 4.3.1 fails due to encryption error Key: CLOUDSTACK-8070 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.2 Reporter: Rohit Yadav Assignee: Rohit Yadav Priority: Blocker Fix For: 4.3.2 The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this caused jasypt to complain when mgmt server starts up. The fix would be encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-1703) Management Server access error: "Error while decrypting..."
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav closed CLOUDSTACK-1703. --- Resolution: Won't Fix > Management Server access error: "Error while decrypting..." > --- > > Key: CLOUDSTACK-1703 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1703 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.1 > Environment: CentOS 6.3 x86_64 >Reporter: Dusan Batas > > 2013-03-17 17:15:38,874 INFO [utils.component.ComponentLocator] (main:null) > Starting DAO: Site2SiteVpnConnectionDao > 2013-03-17 17:15:38,910 DEBUG [utils.crypt.DBEncryptionUtil] (main:null) > Error while decrypting: XXX > 2013-03-17 17:15:38,910 ERROR [cloud.servlet.CloudStartupServlet] (main:null) > Exception starting management server > org.jasypt.exceptions.EncryptionOperationNotPossibleException > at > org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:981) > at > org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725) > at > com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:65) > at > com.cloud.configuration.ConfigurationVO.getValue(ConfigurationVO.java:92) > at > com.cloud.configuration.dao.ConfigurationDaoImpl.getValue(ConfigurationDaoImpl.java:158) > at > com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34) > at > com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:153) > at > com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34) > at > com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:47) > at javax.servlet.GenericServlet.init(GenericServlet.java:212) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173) > at > org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993) > at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4187) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4496) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) > at > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) > at > org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) > at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) > at > org.apache.catalina.core.StandardService.start(StandardService.java:516) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:710) > at org.apache.catalina.startup.Catalina.start(Catalina.java:593) > 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) > 2013-03-17 17:15:39,099 DEBUG [db.Transaction.Transaction] (main:null) > Rolling back the transaction: Time = 4 Name = getConfigValue; called by > -Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-DatabaseCallback.interceptComplete:71-DatabaseCallback.intercept:36-EC2MainServlet.init:62-StandardWrapper.loadServlet:1173-StandardWrapper.load:993-StandardContext.loadOnStartup:4187-StandardContext.start:4496-ContainerBase.addChildInternal:791-ContainerBase.addChild:771 > 2013-03-17 17:15:39,674 DEBUG [db.Transaction.Transaction] (main:null) > Rolling back the transaction: Time = 10 Nam
[jira] [Commented] (CLOUDSTACK-8014) Failed to create a volume from snapshot - Discrepency in the resource count ?
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244161#comment-14244161
]
Rohit Yadav commented on CLOUDSTACK-8014:
-
Hi France, the NPE is a corner case that occurs only when you create a volume
since it goes through that code path. IMO, this is not a fatal operation to
undelete the template and test its behaviour, you can also set the removed
field to the original value (make sure to note the original value and take DB
dump in case).
> Failed to create a volume from snapshot - Discrepency in the resource count ?
> -
>
> Key: CLOUDSTACK-8014
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8014
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.1
>Reporter: France
>Assignee: Rohit Yadav
>
> As sent to mailing list:
> Hi all.
> We are on XS 6.0.2+Hotfixes and CS 4.3.1.
> (All errors we are getting nowadays have come up only after upgrade from
> 4.1.1, 4.1.1 worked perfectly.)
> After successfully creating s snapshot, I want to create a volume from it, so
> it can be downloaded offsite.
> After clicking “Create volume” I get an error Failed to create a volume.
> If i got to list of volumes, there is a volume with name as defined, but
> Status is empty, and only buttons for attach and destroy exist.
> I have taken a look at catalina.out and management-server.log. Here is the
> log detailing a failure.
> Can you see the problem? How should I fix it? Please advise me.
> Should I create a bug report?
> I have also manually checked space on all storages and it seems there is LOTS
> of free space. Resources based on CS Web GUI are:
> Primary Storage Allocated 15%
> Secondary Storage 5%
> 2014-12-03 12:20:42,493 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-2d51baa2) Zone 1 is ready to launch console proxy
> 2014-12-03 12:20:42,580 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-53354d18) Zone 1 is ready to launch secondary storage VM
> 2014-12-03 12:20:42,894 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-108:ctx-a228ce49) ===START=== 111.client.ip.111 -- GET
> command=listZones&available=true&response=json&sessionkey=CENSORED%3D&_=1417605814964
> 2014-12-03 12:20:42,909 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-108:ctx-a228ce49 ctx-74e696ca) ===END=== 111.client.ip.111 --
> GET
> command=listZones&available=true&response=json&sessionkey=CENSORED%3D&_=1417605814964
> 2014-12-03 12:20:46,482 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-107:ctx-4a28e57c) ===START=== 111.client.ip.111 -- GET
> command=createVolume&response=json&sessionkey=CENSORED%3D&snapshotid=49e4bba9-844d-4b7b-aca2-95a318f17dc4&name=testbrisi567&_=1417605818552
> 2014-12-03 12:20:46,490 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-107:ctx-4a28e57c ctx-d7a11540) Access to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,494 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-107:ctx-4a28e57c ctx-d7a11540) Access to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,507 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-107:ctx-4a28e57c ctx-d7a11540) Access to
> com.cloud.storage.SnapshotVO$$EnhancerByCGLIB$$3490cea0@60c95391 granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,571 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-166:ctx-d915e890) Add job-2804 into job monitoring
> 2014-12-03 12:20:46,571 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-166:ctx-d915e890) Executing AsyncJobVO {id:2804, userId: 59,
> accountId: 60, instanceType: Volume, instanceId: 617, cmd:
> org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd, cmdInfo:
> {"id":"617","response":"json","sessionkey":"CENSORED\u003d","cmdEventType":"VOLUME.CREATE","ctxUserId":"59","snapshotid":"49e4bba9-844d-4b7b-aca2-95a318f17dc4","name":"testbrisi567","httpmethod":"GET","_":"1417605818552","ctxAccountId":"60","ctxStartEventId":"62488"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 95545481387, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-12-03 12:20:46,577 DEBUG [c.c.u.AccountManagerImpl]
> (Job-Executor-166:ctx-d915e890 ctx-d7a11540) Access to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] granted to
> Acct[7d6da3bc-0d70-44eb-8a70-422e4eea184e-userName] by DomainChecker
> 2014-12-03 12:20:46,578 DE
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244236#comment-14244236 ] Rohit Yadav commented on CLOUDSTACK-8070: - cc [~harikrishna.patnala] [~kishan] I think this may be applicable for upgrades to 4.5.0 as well as the 442 to 450 sql simply update the router.ram.size value without using a clean decrypt util like the fix for this issue in case of 4.3; if so, please pick the fix and apply for 4.5 branch as well. > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244237#comment-14244237 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 5519095a2970103ac3acbd948ae1908aa2612c41 in cloudstack's branch refs/heads/4.3 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5519095 ] CLOUDSTACK-8070: during 4.3.1 to 4.3.2 upgrade encrypt config that are hidden In case there is an encryption key/password is provided the value, specifically for router.ram.size will be encrypted otherwise it will remain plain text. Signed-off-by: Rohit Yadav > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244252#comment-14244252 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 94cad49e07d45c7e252fbe9f35e4fab8e543c259 in cloudstack's branch refs/heads/4.4 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=94cad49 ] CLOUDSTACK-8070: during 4.4.2 to 4.4.3 upgrade encrypt config that are hidden In case there is an encryption key/password is provided the value, specifically for router.ram.size will be encrypted otherwise it will remain plain text. Signed-off-by: Rohit Yadav > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav resolved CLOUDSTACK-8070. - Resolution: Fixed > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav closed CLOUDSTACK-8070. --- Tested on DevCloud KVM. > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8067) NPEs in MS log related to console proxy VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244382#comment-14244382 ] ASF GitHub Bot commented on CLOUDSTACK-8067: Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/56 > NPEs in MS log related to console proxy VM > -- > > Key: CLOUDSTACK-8067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8067 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar > > I have set up a new VmWare environment and observing Null Pointer Exceptions > in the MS Log , related to console proxy VM. > Intermittently the agent state for CPVM in cloudstack is going to alert state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8067) NPEs in MS log related to console proxy VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244379#comment-14244379 ] ASF subversion and git services commented on CLOUDSTACK-8067: - Commit 1115bc9cc6ebf2b321bb5a3ff6958d649150cfe5 in cloudstack's branch refs/heads/master from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1115bc9 ] CLOUDSTACK-8067: Fixed NPEs in MS log related to console proxy VM > NPEs in MS log related to console proxy VM > -- > > Key: CLOUDSTACK-8067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8067 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar > > I have set up a new VmWare environment and observing Null Pointer Exceptions > in the MS Log , related to console proxy VM. > Intermittently the agent state for CPVM in cloudstack is going to alert state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8067) NPEs in MS log related to console proxy VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244380#comment-14244380 ] ASF subversion and git services commented on CLOUDSTACK-8067: - Commit aa92f5d4835b87d24a55e79c33c9fd072aee02da in cloudstack's branch refs/heads/master from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aa92f5d ] Merge remote-tracking branch 'anshulg/CLOUDSTACK-8067' This closes #56 Signed-off-by: Rohit Yadav > NPEs in MS log related to console proxy VM > -- > > Key: CLOUDSTACK-8067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8067 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar > > I have set up a new VmWare environment and observing Null Pointer Exceptions > in the MS Log , related to console proxy VM. > Intermittently the agent state for CPVM in cloudstack is going to alert state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8067) NPEs in MS log related to console proxy VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244384#comment-14244384 ] ASF subversion and git services commented on CLOUDSTACK-8067: - Commit b07c9b7a9c0c4bfff63c722a7d619a96280102f1 in cloudstack's branch refs/heads/4.5 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b07c9b7 ] CLOUDSTACK-8067: Fixed NPEs in MS log related to console proxy VM (cherry picked from commit 1115bc9cc6ebf2b321bb5a3ff6958d649150cfe5) Signed-off-by: Rohit Yadav > NPEs in MS log related to console proxy VM > -- > > Key: CLOUDSTACK-8067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8067 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar > > I have set up a new VmWare environment and observing Null Pointer Exceptions > in the MS Log , related to console proxy VM. > Intermittently the agent state for CPVM in cloudstack is going to alert state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244412#comment-14244412 ] Harikrishna Patnala commented on CLOUDSTACK-8070: - Yes Rohit, you are right this needs to fix in master as well. Will do it asap > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244412#comment-14244412 ] Harikrishna Patnala edited comment on CLOUDSTACK-8070 at 12/12/14 4:32 PM: --- Thank you Rohit, you are right this needs to fix in master as well. Will do it asap was (Author: harikrishna.patnala): Yes Rohit, you are right this needs to fix in master as well. Will do it asap > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7455) Unable to connect to management server ?since SAML2 merge?
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti closed CLOUDSTACK-7455.
this has been fixed in recent builds
> Unable to connect to management server ?since SAML2 merge?
> --
>
> Key: CLOUDSTACK-7455
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7455
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Alex Brett
>Priority: Blocker
> Fix For: 4.5.0
>
> Attachments: management-server.log
>
>
> In builds that have the SAML2 merge in, while I can start the management
> server, it appears not to fully startup, and doesn't give the UI or API.
> management-server.log (attached) stops at:
> {noformat}
> 2014-08-29 14:55:02,097 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
> (main:null) Starting CloudStack Components
> 2014-08-29 14:55:02,098 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
> (main:null) Done Starting CloudStack Components
> 2014-08-29 14:55:02,098 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) Starting module [core]
> 2014-08-29 14:55:02,098 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
> (main:null) Starting CloudStack Components
> 2014-08-29 14:55:02,106 INFO [c.c.h.h.m.HypervManagerImpl] (main:null)
> Cleanup mounted mount points used in previous session
> 2014-08-29 14:55:02,141 INFO [c.c.u.DatabaseIntegrityChecker] (main:null)
> Grabbing lock to check for database integrity.
> 2014-08-29 14:55:02,143 INFO [c.c.u.DatabaseIntegrityChecker] (main:null)
> Performing database integrity check
> 2014-08-29 14:55:02,144 DEBUG [c.c.u.DatabaseIntegrityChecker] (main:null) No
> duplicate hosts with the same local storage found in database
> 2014-08-29 14:55:02,146 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) Checking
> to see if the database is at a version before it was the version table is
> created
> 2014-08-29 14:55:02,150 INFO [c.c.c.ClusterManagerImpl] (main:null) Starting
> Cluster manager, msid : 99326614648649
> 2014-08-29 14:55:02,155 INFO [c.c.c.ClusterManagerImpl] (main:null)
> Management server 99326614648649, runId 1409324073632 is being started
> 2014-08-29 14:55:02,156 INFO [c.c.c.ClusterManagerImpl] (main:null)
> Management server (host id : 1) is being started at 127.0.0.1:9090
> 2014-08-29 14:55:02,162 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster
> manager was started successfully
> 2014-08-29 14:55:02,167 DEBUG [c.c.u.s.Script] (main:null) Executing:
> /bin/bash -c /sbin/route | grep default
> 2014-08-29 14:55:02,183 DEBUG [c.c.u.s.Script] (main:null) Execution is
> successful.
> 2014-08-29 14:55:02,185 WARN [c.c.c.ConfigurationManagerImpl] (main:null)
> Management network CIDR is not configured originally. Set it default to
> 10.220.128.0/19
> 2014-08-29 14:55:02,190 WARN [o.a.c.alerts] (main:null) alertType:: 14 //
> dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: Management
> network CIDR is not configured originally. Set it default to 10.220.128.0/19
> 2014-08-29 14:55:02,215 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-0:null) Starting work
> 2014-08-29 14:55:02,224 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-3:null) Starting work
> 2014-08-29 14:55:02,224 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-4:null) Starting work
> 2014-08-29 14:55:02,218 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-2:null) Starting work
> 2014-08-29 14:55:02,218 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-1:null) Starting work
> 2014-08-29 14:55:02,290 DEBUG [c.c.n.l.LBHealthCheckManagerImpl] (main:null)
> LB HealthCheckmanager is getting Started
> 2014-08-29 14:55:02,307 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (NetworkStatsUpdater-1:ctx-5b259b22) Successfully updated aggregate network
> stats
> 2014-08-29 14:55:11,061 INFO [c.c.u.c.ComponentContext] (main:null)
> Configuring
> com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_156f5045
> 2014-08-29 14:55:11,066 INFO [c.c.u.c.ComponentContext] (main:null)
> Configuring
> com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_aa79bf9f
> 2014-08-29 14:55:11,066 INFO [c.c.u.c.ComponentContext] (main:null)
> Configuring
> com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_c720af97
> 2014-08-29 14:55:11,066 INFO [c.c.u.c.ComponentContext] (main:null)
> Configuring
> com.cloud.bridge.persist.dao.MultipartMetaDaoImpl_EnhancerByCloudStack_ae893256
> 2014-08-29 14:55:11,067 INFO [c.c.u.c.ComponentContext] (main:null)
> Configuring
> com.cloud.bridge.persist.dao.UserCredentialsDaoImpl_EnhancerByCloudStack_68227ab
[jira] [Updated] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-8070: Fix Version/s: 4.4.3 4.5.0 > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.5.0, 4.4.3, 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244591#comment-14244591 ] Rohit Yadav commented on CLOUDSTACK-8070: - Cool, just wanted to confirm. I already have a fix in one of my branches, will push it right away. > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.5.0, 4.4.3, 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244598#comment-14244598 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 6321a29e4336de9ffe96e27968f896ec5a8bf37d in cloudstack's branch refs/heads/4.5 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6321a29 ] CLOUDSTACK-8070: Upgrade router.ram.size using encryption util Upgrade fails if value is set using plain text encoding, the value needs to be encrypted (if a key was provided during db was setup). Signed-off-by: Rohit Yadav > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.5.0, 4.4.3, 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244599#comment-14244599 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 1a66b3b5c6b88e9180377e1b5e1206fe2f892c46 in cloudstack's branch refs/heads/master from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1a66b3b ] CLOUDSTACK-8070: Upgrade router.ram.size using encryption util Upgrade fails if value is set using plain text encoding, the value needs to be encrypted (if a key was provided during db was setup). Signed-off-by: Rohit Yadav (cherry picked from commit 6321a29e4336de9ffe96e27968f896ec5a8bf37d) Signed-off-by: Rohit Yadav > Upgrade to 4.3.2 from 4.3.1 fails due to encryption error > - > > Key: CLOUDSTACK-8070 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.2 >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Blocker > Fix For: 4.5.0, 4.4.3, 4.3.2 > > > The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this > caused jasypt to complain when mgmt server starts up. The fix would be > encrypt the config values when upgrades are done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8008) [Automation] Unable to list project tags using projectId parameter
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244660#comment-14244660
]
Prachi Damle commented on CLOUDSTACK-8008:
--
This is not critical as it has alternate way of listing the tags for the
project using the same listTag API, just set resourceid to projectid and
Set resourcetype to Project.
> [Automation] Unable to list project tags using projectId parameter
> --
>
> Key: CLOUDSTACK-8008
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8008
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: Prachi Damle
>Priority: Critical
> Fix For: 4.5.0
>
>
> Unable to list tags using project id
>
> *Test Case Error Log:*
>
> {noformat}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: STARTED
> : TC: test_15_project_tag :::
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Payload: {'apiKey':
> u's8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ',
> 'name': 'Project-V0LCNV', 'command': 'createProject', 'signature':
> 'm/TgWlNz5nCZhvQk2ijMmaDal18=', 'displaytext': 'Test project', 'response':
> 'json'}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Sending GET
> Cmd : createProject===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.130.163
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=s8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ&name=Project-V0LCNV&displaytext=Test+project&signature=m%2FTgWlNz5nCZhvQk2ijMmaDal18%3D&command=createProject&response=json
> HTTP/1.1" 200 122
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: === Jobid:
> 560af5c6-7aab-4e22-8112-69827a6534c1 Started ===
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Payload:
> {'signature': 'pgHH+YwrPyJJkUaofltWoq/VsJc=', 'apiKey':
> u's8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'560af5c6-7aab-4e22-8112-69827a6534c1'}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Sending GET
> Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.130.163
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=560af5c6-7aab-4e22-8112-69827a6534c1&apiKey=s8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ&command=queryAsyncJobResult&response=json&signature=pgHH%2BYwrPyJJkUaofltWoq%2FVsJc%3D
> HTTP/1.1" 200 1323
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-12-02T15:36:29-0800', jobresult :
> {primarystorageavailable : u'200', domain : u'ROOT', domainid :
> u'226d5a1a-6e93-11e4-b54b-0689ea0007ab', vpclimit : u'20', iplimit : u'20',
> memorytotal : 0, secondarystorageavailable : u'400', vmtotal : 0, displaytext
> : u'Test project', vpctotal : 0, id :
> u'510ce7d4-6fa1-4fa4-ada9-7362b3774462', networkavailable : u'20',
> networklimit : u'20', iptotal : 0, volumetotal : 0, snapshotlimit : u'20',
> state : u'Active', networktotal : 0, vpcavailable : u'20', cpuavailable :
> u'40', primarystoragetotal : 0, templatelimit : u'20', snapshottotal : 0,
> templateavailable : u'20', vmlimit : u'20', tags : [], volumelimit : u'20',
> templatetotal : 0, memoryavailable : u'40960', secondarystoragetotal : 0,
> account : u'test-TestResourceTags-WNDF0D', secondarystoragelimit : u'400',
> volumeavailable : u'20', name : u'Project-V0LCNV', vmavailable : u'20',
> ipavailable : u'1', memorylimit : u'40960', primarystoragelimit : u'200',
> cputotal : 0, cpulimit : u'40', snapshotavailable : u'20'}, cmd :
> u'org.apache.cloudstack.api.command.user.project.CreateProjectCmd', userid :
> u'173f139b-5379-4f5b-9aee-eefc77362fe7', jobstatus : 1, jobid :
> u'560af5c6-7aab-4e22-8112-69827a6534c1', jobresultcode : 0, jobresulttype :
> u'object', jobinstancetype : u'None', accountid :
> u'96202eae-f933-41f9-ac94-e2ad37cbdfe6'}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG:
> ===Jobid:560af5c6-7aab-4e22-8112-69827a6534c1 ; StartTime:Tue Dec 2 15:36:46
> 2014 ; EndTime:Tue Dec 2 15:36:46 2014 ; TotalTime:0===
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-12-02T15:36:29-0800', jobresult :
> {primarystorageavailable : u'20
[jira] [Updated] (CLOUDSTACK-8008) [Automation] Unable to list project tags using projectId parameter
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Damle updated CLOUDSTACK-8008:
-
Fix Version/s: (was: 4.5.0)
4.6.0
Future
> [Automation] Unable to list project tags using projectId parameter
> --
>
> Key: CLOUDSTACK-8008
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8008
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: Prachi Damle
>Priority: Critical
> Fix For: Future, 4.6.0
>
>
> Unable to list tags using project id
>
> *Test Case Error Log:*
>
> {noformat}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: STARTED
> : TC: test_15_project_tag :::
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Payload: {'apiKey':
> u's8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ',
> 'name': 'Project-V0LCNV', 'command': 'createProject', 'signature':
> 'm/TgWlNz5nCZhvQk2ijMmaDal18=', 'displaytext': 'Test project', 'response':
> 'json'}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Sending GET
> Cmd : createProject===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.130.163
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=s8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ&name=Project-V0LCNV&displaytext=Test+project&signature=m%2FTgWlNz5nCZhvQk2ijMmaDal18%3D&command=createProject&response=json
> HTTP/1.1" 200 122
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: === Jobid:
> 560af5c6-7aab-4e22-8112-69827a6534c1 Started ===
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Payload:
> {'signature': 'pgHH+YwrPyJJkUaofltWoq/VsJc=', 'apiKey':
> u's8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'560af5c6-7aab-4e22-8112-69827a6534c1'}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Sending GET
> Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.130.163
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=560af5c6-7aab-4e22-8112-69827a6534c1&apiKey=s8-w4P-KNpZug22P4xScxPGflYEQ77OQEJfIDF6uIkZGXiXp8hKCc1AGMqpMgyWihHuDY80PD7NDks-ZgxqOAQ&command=queryAsyncJobResult&response=json&signature=pgHH%2BYwrPyJJkUaofltWoq%2FVsJc%3D
> HTTP/1.1" 200 1323
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-12-02T15:36:29-0800', jobresult :
> {primarystorageavailable : u'200', domain : u'ROOT', domainid :
> u'226d5a1a-6e93-11e4-b54b-0689ea0007ab', vpclimit : u'20', iplimit : u'20',
> memorytotal : 0, secondarystorageavailable : u'400', vmtotal : 0, displaytext
> : u'Test project', vpctotal : 0, id :
> u'510ce7d4-6fa1-4fa4-ada9-7362b3774462', networkavailable : u'20',
> networklimit : u'20', iptotal : 0, volumetotal : 0, snapshotlimit : u'20',
> state : u'Active', networktotal : 0, vpcavailable : u'20', cpuavailable :
> u'40', primarystoragetotal : 0, templatelimit : u'20', snapshottotal : 0,
> templateavailable : u'20', vmlimit : u'20', tags : [], volumelimit : u'20',
> templatetotal : 0, memoryavailable : u'40960', secondarystoragetotal : 0,
> account : u'test-TestResourceTags-WNDF0D', secondarystoragelimit : u'400',
> volumeavailable : u'20', name : u'Project-V0LCNV', vmavailable : u'20',
> ipavailable : u'1', memorylimit : u'40960', primarystoragelimit : u'200',
> cputotal : 0, cpulimit : u'40', snapshotavailable : u'20'}, cmd :
> u'org.apache.cloudstack.api.command.user.project.CreateProjectCmd', userid :
> u'173f139b-5379-4f5b-9aee-eefc77362fe7', jobstatus : 1, jobid :
> u'560af5c6-7aab-4e22-8112-69827a6534c1', jobresultcode : 0, jobresulttype :
> u'object', jobinstancetype : u'None', accountid :
> u'96202eae-f933-41f9-ac94-e2ad37cbdfe6'}
> test_15_project_tag (test_tags.TestResourceTags): DEBUG:
> ===Jobid:560af5c6-7aab-4e22-8112-69827a6534c1 ; StartTime:Tue Dec 2 15:36:46
> 2014 ; EndTime:Tue Dec 2 15:36:46 2014 ; TotalTime:0===
> test_15_project_tag (test_tags.TestResourceTags): DEBUG: Response :
> {jobprocstatus : 0, created : u'2014-12-02T15:36:29-0800', jobresult :
> {primarystorageavailable : u'200', domain : u'ROOT', domainid :
> u'226d5a1a-6e93-11e4-b54b-0689ea0007ab', vpclimit : u'20', iplimit : u'20',
> memorytotal : 0, seconda
[jira] [Commented] (CLOUDSTACK-8022) [Automation] Deletion of Domain with Cleanup set to "true" fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244731#comment-14244731
]
Prachi Damle commented on CLOUDSTACK-8022:
--
This is a race condition between the deleteDomain thread and AccountChecker
thread. DeleteDomain thread marks the domain as inactive and proceeds for
cleanup, AccountChecker thread that runs at the same time cleans up any domains
marked as inactive.
2014-12-03 02:53:03,465 DEBUG [c.c.u.DomainManagerImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Marking domain id=7 as Inactive before actually deleting it
2014-12-03 02:53:03,468 DEBUG [c.c.u.DomainManagerImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Cleaning up domain id=7
2014-12-03 02:53:03,476 DEBUG [c.c.u.DomainManagerImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Deleting account
Acct[5f032e8c-fdef-443e-b1a4-5af572bfa168-test-a-TestVPCNetworkOperations-test_vpc_force_delete_domain-1XBSTB]
as a part of domain id=7 cleanup
2014-12-03 02:53:26,888 DEBUG [c.c.u.AccountManagerImpl]
(AccountChecker-1:ctx-3e11737f) (logid:e842fa1a) Removing inactive domain id=7
2014-12-03 02:53:56,884 DEBUG [c.c.u.AccountManagerImpl]
(AccountChecker-1:ctx-38510231) (logid:8536d8ef) Removing inactive domain id=7
2014-12-03 02:54:16,762 DEBUG [c.c.u.DomainManagerImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Deleting account
Acct[1e04fea4-f50b-44d3-8e20-83fe4f83cee1-test-a-TestVPCNetworkOperations-test_vpc_force_delete_domain-W7VIER]
as a part of domain id=7 cleanup
2014-12-03 02:54:26,881 DEBUG [c.c.u.AccountManagerImpl]
(AccountChecker-1:ctx-6ed07f3d) (logid:dddb67b8) Removing inactive domain id=7
2014-12-03 02:54:33,808 DEBUG [c.c.u.DomainManagerImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Deleting networks for domain id=7
2014-12-03 02:54:33,812 ERROR [c.c.d.d.DomainDaoImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Unable to remove domain as domain 7 no longer exists
2014-12-03 02:54:33,817 ERROR [c.c.u.DomainManagerImpl]
(API-Job-Executor-72:ctx-1a1bd808 job-1474 ctx-2ac8b66c) (logid:b373c063)
Exception deleting domain with id 7
> [Automation] Deletion of Domain with Cleanup set to "true" fails
>
>
> Key: CLOUDSTACK-8022
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8022
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: Prachi Damle
>Priority: Critical
> Fix For: 4.5.0
>
> Attachments: management-server.zip
>
>
> The following test case in test_persistent_rules.py fails:
> {code}
> @attr(tags=["advanced"])
> def test_vpc_force_delete_domain(self):
> # steps
> # 1. Create account and create VPC network in the account
> # 2. Create two persistent networks within this VPC
> # 3. Restart/delete VPC network
> # Validations
> # 1. In case of Restart operation, restart should be successful
> #and persistent networks should be back in persistent state
> # 2. In case of Delete operation, VR servicing the VPC should
> #get destroyed and sourceNAT ip should get released
> child_domain = Domain.create(self.apiclient,
> services=self.services["domain"],
> parentdomainid=self.domain.id)
> try:
> account_1 = Account.create(
> self.apiclient, self.services["account"],
> domainid=child_domain.id
> )
> account_2 = Account.create(
> self.apiclient, self.services["account"],
> domainid=child_domain.id
> )
> self.services["vpc"]["cidr"] = "10.1.1.1/16"
> vpc_1 = VPC.create(
> self.apiclient,
> self.services["vpc"],
> vpcofferingid=self.vpc_off.id,
> zoneid=self.zone.id,
> account=account_1.name,
> domainid=account_1.domainid)
> vpcs = VPC.list(self.apiclient, id=vpc_1.id)
> self.assertEqual(
> validateList(vpcs)[0],
> PASS,
> "VPC list validation failed, vpc list is %s" %
> vpcs)
> vpc_2 = VPC.create(
> self.apiclient,
> self.services["vpc"],
> vpcofferingid=self.vpc_off.id,
> zoneid=se
[jira] [Resolved] (CLOUDSTACK-8025) SEGV in libvirtd when live migrating CentOS 6.6 x86_64
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee Webb resolved CLOUDSTACK-8025.
--
Resolution: Fixed
After some more testing I've identified that this appears to be an issue only
when the Cloudstack agent.properties cpu.host.mode is host-model or
host-passthrough on the CPU model I've got available
There are references here:
https://sourceware.org/ml/libc-alpha/2013-08/msg00257.html which are a close
match for my issue even though they are from last year.
When the cpu.host.mode is custom & a choice is made from libvirtd's cpu_map.xml
the problem doesn't occur.
In my case I had to set the cpu.host.model to SandyBridge, a retest confirmed
that the segfault was avoided.
Here's what I ended up with in agent.properties
{code}
cpu.host.mode=custom
cpu.host.model=SandyBridge
{code}
It might be worth making a documentation note for the Agent that reference to
the libvirtd documentation on the cpu model & topology should be made if
wanting to set the mode to anything other than whatever the default is as there
are warnings regarding doing so.
> SEGV in libvirtd when live migrating CentOS 6.6 x86_64
> --
>
> Key: CLOUDSTACK-8025
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8025
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
>Affects Versions: 4.4.1
> Environment: CentOS 6.6 x86_64
> Dell PowerEdge M420
> Intel E5-2470 v2 @ 2.40GHz
> libvirt-0.10.2-46.el6_6.2.x86_64
>Reporter: Lee Webb
>
> Hi There,
> I'm not entirely sure whether I should raise with against libvirt project,
> however ...
> When attempting to live migrate an instance from one compute node to another
> libvirtd dies with a Segmentation Fault & it's 100% reproducible on 5
> different hosts.
> Steps to reproduce:
> 1. Start Instance of CentOS 6.6 x86_64, then wait for it to come up
> 2. Migrate Instance to another available Compute Node
> 3. Popup message appears stating Input / Ouput Error
> On the target Compute node libvirtd states that there has been a segmentation
> fault.
> Following is a backtrace for the core:
> {code}
> #0 __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp.S:260
> #1 0x7f7d92dd6411 in x86ModelFind (cpu=0x7f7d68003440,
> map=0x7f7d680021e0, policy=1) at cpu/cpu_x86.c:831
> #2 x86ModelFromCPU (cpu=0x7f7d68003440, map=0x7f7d680021e0, policy=1) at
> cpu/cpu_x86.c:850
> #3 0x7f7d92dd87e8 in x86Compute (host=,
> cpu=0x7f7d68003440, guest=0x7f7d82f04df0, message=0x7f7d82f04de0) at
> cpu/cpu_x86.c:1243
> #4 0x004aac4e in qemuBuildCpuArgStr (conn=0x7f7d5920,
> driver=0x7f7d78013b20, def=0x7f7d68002830, monitor_chr=0x7f7d680026f0,
> monitor_json=true, caps=0x7f7d68002c50,
> migrateFrom=0x7f7d680136d0 "tcp:[::]:49152", migrateFd=-1, snapshot=0x0,
> vmop=VIR_NETDEV_VPORT_PROFILE_OP_MIGRATE_IN_START) at qemu/qemu_command.c:4516
> #5 qemuBuildCommandLine (conn=0x7f7d5920, driver=0x7f7d78013b20,
> def=0x7f7d68002830, monitor_chr=0x7f7d680026f0, monitor_json=true,
> caps=0x7f7d68002c50, migrateFrom=0x7f7d680136d0 "tcp:[::]:49152",
> migrateFd=-1, snapshot=0x0,
> vmop=VIR_NETDEV_VPORT_PROFILE_OP_MIGRATE_IN_START) at qemu/qemu_command.c:5320
> #6 0x0048a2cc in qemuProcessStart (conn=0x7f7d5920,
> driver=0x7f7d78013b20, vm=0x7f7d68006e10, migrateFrom=0x7f7d680136d0
> "tcp:[::]:49152", stdin_fd=-1, stdin_path=0x0, snapshot=0x0,
> vmop=VIR_NETDEV_VPORT_PROFILE_OP_MIGRATE_IN_START, flags=6) at
> qemu/qemu_process.c:4008
> #7 0x00491110 in qemuMigrationPrepareAny (driver=0x7f7d78013b20,
> dconn=0x7f7d5920, cookiein=, cookieinlen=255,
> cookieout=0x7f7d82f05ae0, cookieoutlen=0x7f7d82f05aec,
> dname=0x7f7d68002570 "i-2-10-VM",
> dom_xml=0x7f7d680013d0 "\n i-2-10-VM\n
> 95c5aa11-f7ad-4322-b377-d153774e330f\n CentOS 6.5
> (64-bit)\n 1048576\n
> qemu/qemu_migration.c:1502
> #8 0x00491ab7 in qemuMigrationPrepareDirect (driver=0x7f7d78013b20,
> dconn=0x7f7d5920,
> cookiein=0x7f7d680012c0 "\n i-2-10-VM\n
> 95c5aa11-f7ad-4322-b377-d153774e330f\n
> eqx-cs-cmp-05.ipscape.com.au\n
> 44454c4c-3000-104b-8043-b4c04f573232 cookieout=0x7f7d82f05ae0, cookieoutlen=0x7f7d82f05aec, uri_in= optimized out>, uri_out=0x7f7d68002680, dname=0x7f7d68002570 "i-2-10-VM",
> dom_xml=0x7f7d680013d0 "\n i-2-10-VM\n
> 95c5aa11-f7ad-4322-b377-d153774e330f\n CentOS 6.5
> (64-bit)\n 1048576\n
> #9 0x004550b4 in qemuDomainMigratePrepare3 (dconn=0x7f7d5920,
> cookiein=0x7f7d680012c0 "\n i-2-10-VM\n
> 95c5aa11-f7ad-4322-b377-d153774e330f\n
> eqx-cs-cmp-05.ipscape.com.au\n
> 44454c4c-3000-104b-8043-b4c04f573232 cookieout=0x7f7d82f05ae0,
[jira] [Commented] (CLOUDSTACK-7576) new nfs storage adapter for kvm hypervisor plugin to support managed storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244994#comment-14244994 ] Animesh Chaturvedi commented on CLOUDSTACK-7576: I cant find your FS. Can you point the link to me? > new nfs storage adapter for kvm hypervisor plugin to support managed storage. > - > > Key: CLOUDSTACK-7576 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7576 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: punith >Assignee: punith > Fix For: 4.5.0 > > > this adapter provides one to one mapping between the SAN volume to a VM's > disk, so that it can guarantee the QoS for the performance sensitive > applications. > this adapter is based on nfs protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7098) Improvised CloudByte Storage Plugin for 4.5 and above.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244999#comment-14244999 ] Animesh Chaturvedi commented on CLOUDSTACK-7098: Punith where is the FS link for this? > Improvised CloudByte Storage Plugin for 4.5 and above. > -- > > Key: CLOUDSTACK-7098 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7098 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: punith > Fix For: 4.5.0 > > > The new improvised cloudbyte plugin for cloudstack supports the following > features > * support for managed storage, where each vm disk has the guaranteed > QoS. > * account integration in cloudbyte with respect to domains in cloudstack. > * supports resize of the volume. > * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for > KVM and vmware ESX. > * supports storage level snapshot capabilites as well as hypervisor level > snapshot feature. > * also exposing the custom api's for ui integration. > * support for unlimited storage nodes across the sites. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
