[jira] [Created] (CLOUDSTACK-2757) Category not persisted when added config items
Kishan Kavala created CLOUDSTACK-2757: - Summary: Category not persisted when added config items Key: CLOUDSTACK-2757 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2757 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kishan Kavala Fix For: 4.2.0 Category is persisted when adding config items in ConfigurationDaoImpl.getValueAndInitIfNotExist. It is always set to Advanced. This can cause encryption failures. It'll be good to cleanup the SQL and use VO/DAO instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670109#comment-13670109 ] Abhinandan Prateek commented on CLOUDSTACK-2735: Kiran, can you list down the patches installed on 6.1 ? Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Blocker Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at
[jira] [Comment Edited] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670109#comment-13670109 ] Abhinandan Prateek edited comment on CLOUDSTACK-2735 at 5/30/13 6:45 AM: - Kiran, can you list down the patches installed on 6.1 ? Looks like the issue is with the patches. was (Author: aprateek): Kiran, can you list down the patches installed on 6.1 ? Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Blocker Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at
[jira] [Commented] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670112#comment-13670112 ] Kiran Koneti commented on CLOUDSTACK-2735: -- The issue is not seen if the below patches are not applied on the Xenserver, but if the patches are not applied the PV drivers are not getting installed for the VM's deployed on the Xenserver host. 1)XS61E001.zip 2)XS61E003.zip 3)XS61E004.zip 4)XS61E006.zip 5)XS61E009.zip 6)XS61E010.zip 7)XS61E012.zip 8)XS61E013.zip 9)XS61E014.zip 10)XS61E017.zip 11)XS61E018.zip 12)XS61E019.zip 13)XS61E020.zip 14)XS61E022.zip Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Blocker Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972
[jira] [Updated] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-2735: --- Priority: Critical (was: Blocker) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Critical Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143)
[jira] [Updated] (CLOUDSTACK-2732) [Multiple_IP_Ranges] Deleting guest IP range is not throwing any error message to user while the ip addresses are being used
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar updated CLOUDSTACK-2732:
-
Assignee: Bharat Kumar
[Multiple_IP_Ranges] Deleting guest IP range is not throwing any error
message to user while the ip addresses are being used
Key: CLOUDSTACK-2732
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2732
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: latest build from master
Zone: Advanced with SG
Hypervisor: KVM
Reporter: Sanjeev N
Assignee: Bharat Kumar
Fix For: 4.2.0
Deleting guest IP range is not throwing any error message to user while the
ip addresses are being used
Steps to Reproduce:
1.Bring up CS with SG enabled advanced zone with kvm hypervisor
2.Exhaust all the guest ip ranges from the primary ip range
3.Add another ip range in the existing CIDR
4.Deploy guest vm
5.Try to delete the ip range added at step3
Expected Result:
==
Deleting ip range when the ip addresses are being used, should throw a valid
error message to user
Actual Result:
===
No error message popped up for the user
Observations:
===
API fired:
http://10.147.59.126:8080/client/api?command=deleteVlanIpRangeid=de89f23e-8a17-4b4e-8b9c-8c89c11ec5a1response=jsonsessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D_=1369826364206
{ deletevlaniprangeresponse :
{uuidList:[],errorcode:530,cserrorcode:} }
Also observed NPE:
2013-05-29 12:48:27,646 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
===START=== 10.146.0.15 -- GET
command=deleteVlanIpRangeid=de89f23e-8a17-4b4e-8b9c-8c89c11ec5a1response=jsonsessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D_=1369826364206
2013-05-29 12:48:27,781 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) Ping from 3
2013-05-29 12:48:27,789 ERROR [cloud.api.ApiServer] (catalina-exec-19:null)
unhandled exception executing api command: deleteVlanIpRange
java.lang.NullPointerException
at
com.cloud.configuration.ConfigurationManagerImpl.deleteVlanAndPublicIpRange(ConfigurationManagerImpl.java:2951)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.configuration.ConfigurationManagerImpl.deleteVlanIpRange(ConfigurationManagerImpl.java:3476)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.admin.vlan.DeleteVlanIpRangeCmd.execute(DeleteVlanIpRangeCmd.java:69)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
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
[jira] [Updated] (CLOUDSTACK-2736) [Multiple_IP_Ranges] Failed to deploy vm with IP address from new CIDR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar updated CLOUDSTACK-2736:
-
Assignee: Bharat Kumar
[Multiple_IP_Ranges] Failed to deploy vm with IP address from new CIDR
---
Key: CLOUDSTACK-2736
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2736
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Latest build from master branch:
Zone: SG enabled advanced zone
Hypervisor:KVM
Reporter: Sanjeev N
Assignee: Bharat Kumar
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.rar
Failed to deploy vm with IP address from new CIDR
Steps to Reproduce:
=
1.Bring up CS with SG enabled advnaced zone with KVM cluster
2.Add guest ip range in new CIDR in the existing default shared network
3.Deploy guest vm with IP address from the new CIDR
Expected Result:
==
IP alias should be created on the VR and VM deployment should be successful
with IP address from the new CIDR
Actual Result:
VM deployment failed
Observations:
===
Configuring dhcp service failed with following exceptions:
2013-05-29 13:04:38,782 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-24:null) submit async job-18, details: AsyncJobVO {id:18,
userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
instanceId: 7, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
cmdOriginator: null, cmdInfo:
{sessionkey:ySm8CvuVNkVVRASycbmxD0Lfby4\u003d,ctxUserId:2,serviceOfferingId:b69fbcae-6cbb-4ac4-9669-a8cc8effe2f3,httpmethod:GET,securitygroupids:a181bf2c-c853-11e2-96ab-06045a66,zoneId:4f13e6b8-aa69-425e-954f-b1852f202266,response:json,templateId:6fb1b1b4-c853-11e2-96ab-06045a66,id:7,networkIds:a26a1c93-83c8-4f41-b6ba-7525e8aa0056,hypervisor:KVM,name:vm1-s2,_:1369827334315,ctxAccountId:2,ctxStartEventId:79,displayname:vm1-s2},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-29 13:04:38,786 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
===END=== 10.146.0.15 -- GET
command=deployVirtualMachinezoneId=4f13e6b8-aa69-425e-954f-b1852f202266templateId=6fb1b1b4-c853-11e2-96ab-06045a66hypervisor=KVMserviceOfferingId=b69fbcae-6cbb-4ac4-9669-a8cc8effe2f3securitygroupids=a181bf2c-c853-11e2-96ab-06045a66networkIds=a26a1c93-83c8-4f41-b6ba-7525e8aa0056displayname=vm1-s2name=vm1-s2response=jsonsessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D_=1369827334315
2013-05-29 13:04:38,789 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-2:job-18) Executing
org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-18
2013-05-29 13:04:40,365 DEBUG [db.Transaction.Transaction]
(Job-Executor-2:job-18) Rolling back the transaction: Time = 131 Name =
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679;
called by
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-NetworkManagerImpl.assignPublicIpAddressFromVlans:370-VirtualNetworkApplianceManagerImpl.configDhcpForSubnet:2798-VirtualRouterElement.configDhcpSupportForSubnet:870-NetworkManagerImpl.prepareElement:1962-NetworkManagerImpl.prepareNic:2077-NetworkManagerImpl.prepare:2018-VirtualMachineManagerImpl.advanceStart:842
2013-05-29 13:04:40,366 INFO
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-18)
Insufficient address capacity
2013-05-29 13:04:40,367 INFO
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-18)
unable to configure dhcp for this VM.
2013-05-29 13:04:40,367 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-18) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: unable to configure
the dhcp service, due to insufficiant address capacityScope=interface
com.cloud.network.Network; id=203
at
com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2078)
at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2018)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:842)
at
[jira] [Updated] (CLOUDSTACK-2756) Stratosphere SSP plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiroaki Kawai updated CLOUDSTACK-2756: -- Description: Stratosphere SDN Platform (SSP) is an SDN solution, which creates virtual L2 networking backed by vxlan, which is edge overlay technology. The purpose of this plugin is to integrate it with cloudstack as a connecitvity networking service. was: Stratosphere SDN Platform (SSP) is an SDN solution, which creates virtual L2 networking with edge overlay technologies. The purpose of this plugin is to integrate it with cloudstack as a connecitvity networking service. Stratosphere SSP plugin --- Key: CLOUDSTACK-2756 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2756 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Hiroaki Kawai Assignee: Hiroaki Kawai Stratosphere SDN Platform (SSP) is an SDN solution, which creates virtual L2 networking backed by vxlan, which is edge overlay technology. The purpose of this plugin is to integrate it with cloudstack as a connecitvity networking service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2756) Stratosphere SSP plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiroaki Kawai updated CLOUDSTACK-2756: -- Description: Stratosphere SDN Platform (SSP) is an SDN solution, which creates virtual L2 networking backed by vxlan, which is edge overlay technology. The purpose of this plugin is to integrate it with cloudstack as a connecitvity networking service. The design document is https://cwiki.apache.org/confluence/display/CLOUDSTACK/Stratosphere+SSP+Network+Plugin was: Stratosphere SDN Platform (SSP) is an SDN solution, which creates virtual L2 networking backed by vxlan, which is edge overlay technology. The purpose of this plugin is to integrate it with cloudstack as a connecitvity networking service. Stratosphere SSP plugin --- Key: CLOUDSTACK-2756 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2756 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Hiroaki Kawai Assignee: Hiroaki Kawai Stratosphere SDN Platform (SSP) is an SDN solution, which creates virtual L2 networking backed by vxlan, which is edge overlay technology. The purpose of this plugin is to integrate it with cloudstack as a connecitvity networking service. The design document is https://cwiki.apache.org/confluence/display/CLOUDSTACK/Stratosphere+SSP+Network+Plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2758) cloudstack-management does not start from RPM packages
Prasanna Santhanam created CLOUDSTACK-2758: -- Summary: cloudstack-management does not start from RPM packages Key: CLOUDSTACK-2758 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2758 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Packaging Affects Versions: 4.2.0 Reporter: Prasanna Santhanam Priority: Critical Fix For: 4.2.0 For the last two days the packages for CloudStack from jenkins.cs.o haven't been able to boot up the management server. The service start reports OK, but the service dies immediately. [root@cloudstack-centos63 ~]# bash -x /etc/init.d/cloudstack-management start + '[' -r /etc/rc.d/init.d/functions ']' + . /etc/rc.d/init.d/functions ++ TEXTDOMAIN=initscripts ++ umask 022 ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin ++ export PATH ++ '[' -z '' ']' ++ COLUMNS=80 ++ '[' -z '' ']' +++ /sbin/consoletype ++ CONSOLETYPE=pty ++ '[' -f /etc/sysconfig/i18n -a -z '' -a -z '' ']' ++ . /etc/profile.d/lang.sh ++ unset LANGSH_SOURCED ++ '[' -z '' ']' ++ '[' -f /etc/sysconfig/init ']' ++ . /etc/sysconfig/init +++ BOOTUP=color +++ RES_COL=60 +++ MOVE_TO_COL='echo -en \033[60G' +++ SETCOLOR_SUCCESS='echo -en \033[0;32m' +++ SETCOLOR_FAILURE='echo -en \033[0;31m' +++ SETCOLOR_WARNING='echo -en \033[0;33m' +++ SETCOLOR_NORMAL='echo -en \033[0;39m' +++ PROMPT=yes +++ AUTOSWAP=no +++ ACTIVE_CONSOLES='/dev/tty[1-6]' +++ SINGLE=/sbin/sushell ++ '[' pty = serial ']' ++ __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d' + '[' -r /lib/lsb/init-functions ']' + . /lib/lsb/init-functions ++ basename /etc/init.d/cloudstack-management + NAME=cloudstack-management + case $1 in + set_ulimit ++ ulimit -n + fd_limit=1024 + '[' 1024 '!=' 4096 ']' ++ whoami + user=root + '[' root == root ']' + ulimit -n 4096 + . /etc/rc.d/init.d/tomcat6 ++ '[' -r /lib/lsb/init-functions ']' ++ . /lib/lsb/init-functions +++ lsb_release -i -s ++ DISTRIB_ID=CentOS +++ basename /etc/init.d/cloudstack-management ++ NAME=cloudstack-management ++ unset ISBOOT ++ '[' c = S -o c = K ']' ++ '[' -x /sbin/runuser ']' ++ SU='/sbin/runuser -s /bin/sh' ++ TOMCAT_CFG=/etc/tomcat6/tomcat6.conf ++ '[' -r /etc/tomcat6/tomcat6.conf ']' ++ . /etc/tomcat6/tomcat6.conf +++ CATALINA_BASE=/usr/share/tomcat6 +++ CATALINA_HOME=/usr/share/tomcat6 +++ JASPER_HOME=/usr/share/tomcat6 +++ CATALINA_TMPDIR=/var/cache/tomcat6/temp +++ JAVA_OPTS=' -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory' +++ TOMCAT_USER=tomcat +++ SECURITY_MANAGER=false +++ SHUTDOWN_WAIT=30 +++ SHUTDOWN_VERBOSE=false +++ CATALINA_PID=/var/run/tomcat6.pid ++ '[' -r /etc/sysconfig/cloudstack-management ']' ++ . /etc/sysconfig/cloudstack-management +++ dummy=1 +++ export TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf +++ TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf +++ . /etc/cloudstack/management/tomcat6.conf CATALINA_BASE=/usr/share/cloudstack-management CATALINA_HOME=/usr/share/cloudstack-management JASPER_HOME=/usr/share/cloudstack-management CATALINA_TMPDIR=/usr/share/cloudstack-management/temp JAVA_OPTS='-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m' TOMCAT_USER=cloud TOMCAT6_USER=cloud TOMCAT_LOG=/var/log/cloudstack/management//catalina.out SECURITY_MANAGER=false SHUTDOWN_WAIT=30 SHUTDOWN_VERBOSE=false CATALINA_PID=/var/run/cloudstack-management.pid dummy=1 . /etc/cloudstack/management/classpath.conf + SYSTEMJARS= ++ build-classpath + SCP= + '[' 2 '!=' 0 ']' + export SCP= + SCP= + MCP= + DCP= + CLASSPATH=:::/etc/cloudstack/management:/usr/share/cloudstack-management/setup + for jarfile in '/usr/share/cloudstack-management/premium/*' + '[' '!' -e '/usr/share/cloudstack-management/premium/*' ']' + continue + for plugin in '/usr/share/cloudstack-management/plugin/*' + '[' '!' -e '/usr/share/cloudstack-management/plugin/*' ']' + continue + for vendorconf in '/etc/cloudstack/management/vendor/*' + '[' '!' -d '/etc/cloudstack/management/vendor/*' ']' + continue + export CLASSPATH + PATH=/sbin:/usr/sbin:/sbin:/usr/sbin:/bin:/usr/bin + export PATH ++ CONNECTOR_PORT=8080 ++ TOMCAT_SCRIPT=/usr/sbin/tomcat6 ++ TOMCAT_PROG=cloudstack-management ++ TOMCAT_USER=cloud ++ TOMCAT_LOG=/var/log/cloudstack/management//catalina.out ++ export CATALINA_PID=/var/run/cloudstack-management.pid ++ CATALINA_PID=/var/run/cloudstack-management.pid ++ RETVAL=0 ++ RETVAL=0 ++ case $1 in ++ start ++ echo -n
[jira] [Commented] (CLOUDSTACK-2130) UpdateDefaultNicForVirtualMachine api should also create usage events for updating new default network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670128#comment-13670128 ] ASF subversion and git services commented on CLOUDSTACK-2130: - Commit 62413eec1067ab5d92977fab93a2fc88d4247bb0 in branch refs/heads/master from [~saksham] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=62413ee ] CLOUDSTACK-2130: Fix resource_name for old NIC ID Signed-off-by: Mice Xia mice_...@tcloudcomputing.com UpdateDefaultNicForVirtualMachine api should also create usage events for updating new default network -- Key: CLOUDSTACK-2130 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2130 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Usage Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-232-rhel6.3 Reporter: shweta agarwal Assignee: Saksham Srivastava Priority: Critical Fix For: 4.2.0 When we call UpdateDefaultNicForVirtualMachine we should call appropriate usage events as well for updating information related to default nic for proper usage calculation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2128) usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670127#comment-13670127 ] ASF subversion and git services commented on CLOUDSTACK-2128: - Commit 4989f73fdaab23cb8d78131163eeb9a0e1ad2856 in branch refs/heads/master from [~mice] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4989f73 ] fix CLOUDSTACK-2128, should save network offering id into usage event usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called -- Key: CLOUDSTACK-2128 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2128 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Usage Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-232-rhel6.3.tar.gz Reporter: shweta agarwal Assignee: Mice Xia Priority: Critical Fix For: 4.2.0 When we call addNicToVirtualMachine api it adds a new network /nic to a VM . Presently we just register this in events . however we need to add this event in usage event for correct tracking of network we need to create a corresponding network.offerings.assign event in usage events table as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2128) usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mice Xia resolved CLOUDSTACK-2128. -- Resolution: Fixed fixed usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called -- Key: CLOUDSTACK-2128 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2128 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Usage Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-232-rhel6.3.tar.gz Reporter: shweta agarwal Assignee: Mice Xia Priority: Critical Fix For: 4.2.0 When we call addNicToVirtualMachine api it adds a new network /nic to a VM . Presently we just register this in events . however we need to add this event in usage event for correct tracking of network we need to create a corresponding network.offerings.assign event in usage events table as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2130) UpdateDefaultNicForVirtualMachine api should also create usage events for updating new default network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava resolved CLOUDSTACK-2130. Resolution: Fixed UpdateDefaultNicForVirtualMachine api should also create usage events for updating new default network -- Key: CLOUDSTACK-2130 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2130 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Usage Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-232-rhel6.3 Reporter: shweta agarwal Assignee: Saksham Srivastava Priority: Critical Fix For: 4.2.0 When we call UpdateDefaultNicForVirtualMachine we should call appropriate usage events as well for updating information related to default nic for proper usage calculation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1532) Ability to plug a VPC private gateway interface onto a specified Nicira NVP logical switch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers updated CLOUDSTACK-1532: --- Status: Ready To Review (was: In Progress) Ability to plug a VPC private gateway interface onto a specified Nicira NVP logical switch -- Key: CLOUDSTACK-1532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1532 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Reporter: Roeland Kuipers Assignee: Hugo Trippaers Currently a VPC private gateway interface can be plugged on a specific VLAN. We like to see the possibility to specify a Nicira NVP logical switch instead of a VLAN. One of the use cases we have for this is VPC - VPC connectivity (routing) within the logical space of NVP -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-681) Dedicate Pod, Cluster or Host to a domain
[ https://issues.apache.org/jira/browse/CLOUDSTACK-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670151#comment-13670151 ] ASF subversion and git services commented on CLOUDSTACK-681: Commit 965c7b9c35fc5680b2f35a8c8fed35c1232a643b in branch refs/heads/master from [~saksham] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=965c7b9 ] Patch 2: CLOUDSTACK-681: Dedicated Resources - Explicit Dedication, Private zone, pod, cluster or host Patch 2 for https://reviews.apache.org/r/11379/ Created for files server/src/com/cloud/deploy/DeploymentPlanningManagerImpl.java, server/test/com/cloud/vm/DeploymentPlanningManagerImplTest.java, server/test/org/apache/cloudstack/affinity/AffinityApiUnitTest.java Dedicate Pod, Cluster or Host to a domain - Key: CLOUDSTACK-681 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-681 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Reporter: deepti dohare Assignee: Devdeep Singh Fix For: 4.2.0 Currently in CloudStack architecture, domains can have dedicated zones but not pods, clusters or hosts. Dedicating a zone might be very expensive offering for an end users, whereas dedicating a pod, cluster or a host may be more economical. This feature will allow Root-Admin to dedicate resources to a specific domain that needs private infrastructure for additional security or performance guarantees. Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Private+Host%2C+Cluster%2C+Pod Release Planning: Dev List Discussion: http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201212.mbox/browser Functional Spec: https://cwiki.apache.org/CLOUDSTACK/dedicated-resources-private-zone-pod-cluster-host-functional-spec.html Feature Branch: Will come in as reviews -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2735: -- Assignee: (was: Abhinandan Prateek) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at
[jira] [Commented] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670174#comment-13670174 ] Abhinandan Prateek commented on CLOUDSTACK-2735: I will keep this open till we figure out what patch is misbehaving. Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Critical Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658)
[jira] [Created] (CLOUDSTACK-2759) listNetworks should show ACL applied state
Kishan Kavala created CLOUDSTACK-2759: - Summary: listNetworks should show ACL applied state Key: CLOUDSTACK-2759 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2759 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kishan Kavala Fix For: 4.2.0 When NetworkACL is applied to a network, it could fail when the router is not up, or due to connectivity issues. listNetworks API should return the network ACL applied state (Add/Active), so that user can see the ACL state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CLOUDSTACK-2651) [Shared n/w]Add IP range should ask for gateway and netmask
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669166#comment-13669166
]
Bharat Kumar edited comment on CLOUDSTACK-2651 at 5/30/13 9:39 AM:
---
the public ips belong to the pod, they do not belong to the network.
was (Author: bharat.kumar):
Also reading from the network part is already being done to check if it a
range is being added to same subnet or a different one.
[Shared n/w]Add IP range should ask for gateway and netmask
---
Key: CLOUDSTACK-2651
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2651
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Affects Versions: 4.2.0
Reporter: manasaveloori
Assignee: Bharat Kumar
Priority: Critical
Fix For: 4.2.0
Attachments: guestnetwork.jpg
Steps:
1. Have an CS setup with advanced zone/ Advanced zone with SG.
2. Create a shared network(zone-physical network-Guest-Add guest network).
3. Try to entend the ip range for the created guest network.(zone-physical
network-Guest- created guest network -view ip ranges-add ip range)
Observation:The API passed for extending the ip range is
API
passed:http://10.147.38.154:8080/client/api?command=createVlanIpRangeforVirtualNetwork=falsenetworkid=2bc91f46-8f4a-4a31-b95d-ecea71663e67startip=10.147.54.238endip=10.147.54.239response=jsonsessionkey=ax2q1vd%2Bp4BsOPgw%2BKQ78JKMVx0%3D_=1369311736447;
Response is
{ createvlaniprangeresponse :
{errorcode:431,cserrorcode:4350,errortext:Gateway, netmask and zoneId
have to be passed in for virtual and direct untagged networks} }
Expected behaviour:
Extending ip range for the already existing network should ask for
parameters like gateway and netmask otherwise user can't add guest ip range
in different subnet.
Attached the screen shot for reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2760) UI - Agent Status not shown for SSVM and CPVM.
Nitin Mehta created CLOUDSTACK-2760: --- Summary: UI - Agent Status not shown for SSVM and CPVM. Key: CLOUDSTACK-2760 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2760 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Nitin Mehta Priority: Critical Fix For: 4.2.0 UI - Agent Status not shown for SSVM and CPVM. We can query agent status through listHosts command. This would greatly help understand the admin the status of the agents which do the real handshake with MS and also the work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2760) UI - Agent Status not shown for SSVM and CPVM.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670213#comment-13670213 ] Nitin Mehta commented on CLOUDSTACK-2760: - This should be shown along with the SSVM status as agent status UI - Agent Status not shown for SSVM and CPVM. -- Key: CLOUDSTACK-2760 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2760 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0, 4.2.0 Reporter: Nitin Mehta Priority: Critical Fix For: 4.2.0 UI - Agent Status not shown for SSVM and CPVM. We can query agent status through listHosts command. This would greatly help understand the admin the status of the agents which do the real handshake with MS and also the work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2728) 41-42 DB upgrade: add step to upgrade system templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2728: -- Assignee: Harikrishna Patnala 41-42 DB upgrade: add step to upgrade system templates -- Key: CLOUDSTACK-2728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Alena Prokharchyk Assignee: Harikrishna Patnala Priority: Blocker This bug is a blocker for the DB upgrade testing. As the system vm got changed in CS 4.2, we have to add upgrade steps for 4.1 users. Usually the steps are: 1) While being on 4.1, upload the system template (it should be named properly) 2) During the 4.1 -4.2 db upgrade, the script should change the vm_template_id for all the system vms, to the id of the new template 3) All the system vms have to be restarted afterwards. Right now step #2 is not a part of the DB upgrade script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670222#comment-13670222 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit a96c9c5ae4138a4e22d0ee73b985ea4efbe77c9a in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a96c9c5 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Injecting component VolumeManager into VmwareResource. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-769) Documentation for nTier Apps 2.0 : Internal LB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-769: Description: documentation for nTier Apps 2.0 : Internal LB https://cwiki.apache.org/confluence/display/CLOUDSTACK/Internal+Load+Balancing+between+VPC+tiers was:documentation for nTier Apps 2.0 : Use same public IP for static NAT, PF and LB in VPC Summary: Documentation for nTier Apps 2.0 : Internal LB (was: Documentation for nTier Apps 2.0 : Use same public IP for static NAT, PF and LB in VPC) Documentation for nTier Apps 2.0 : Internal LB --- Key: CLOUDSTACK-769 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-769 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 documentation for nTier Apps 2.0 : Internal LB https://cwiki.apache.org/confluence/display/CLOUDSTACK/Internal+Load+Balancing+between+VPC+tiers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-769) Documentation for nTier Apps 2.0 : Internal LB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670224#comment-13670224 ] ASF subversion and git services commented on CLOUDSTACK-769: Commit 08e5a45def1ff7685f9067114c769037e54fb411 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=08e5a45 ] CLOUDSTACK-769 Documentation for nTier Apps 2.0 : Internal LB --- Key: CLOUDSTACK-769 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-769 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 documentation for nTier Apps 2.0 : Internal LB https://cwiki.apache.org/confluence/display/CLOUDSTACK/Internal+Load+Balancing+between+VPC+tiers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2761) [VMware] [VPC] Failed to create PF/StaticNAT rules on VPC
venkata swamybabu budumuru created CLOUDSTACK-2761:
--
Summary: [VMware] [VPC] Failed to create PF/StaticNAT rules on VPC
Key: CLOUDSTACK-2761
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2761
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller
Affects Versions: 4.2.0
Environment: commit # 8d1189c2ae87216bc1c4a1443f75e9a8629abdc2
Reporter: venkata swamybabu budumuru
Priority: Blocker
Fix For: 4.2.0
Steps to reproduce:
1. Have latest CloudStack build with at least 1 advanced zone
2. Have at least 1 VMware cluster with 1 host.
3. Create a VPC with at least 1 Tier
4. deploy a VM
5. apply an ACL to allow all
6. acquire at least 1 IP
7. create PF/staticNAT on the above created IP to the VM created in step (4)
Observations:
(i) It failed to create staticNAT with the following error
2013-05-30 08:05:20,203 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-38:null) Seq 1-1416495168: Response Received:
2013-05-30 08:05:20,206 DEBUG [agent.transport.Request] (DirectAgent-38:null)
Seq 1-1416495168: Processing: { Ans: , MgmtId: 7280707764394, via: 1, Ver: v1,
Flags: 0, [{routing.IpAssocAnswer:{results:[10.147.44.63 -
success],result:true,wait:0}}] }
2013-05-30 08:05:20,207 DEBUG [agent.transport.Request] (catalina-exec-19:null)
Seq 1-1416495168: Received: { Ans: , MgmtId: 7280707764394, via: 1, Ver: v1,
Flags: 0, { IpAssocAnswer } }
2013-05-30 08:05:20,211 INFO [cloud.network.NetworkManagerImpl]
(catalina-exec-19:null) Let VpcVirtualRouter handle StaticNat in network 204
2013-05-30 08:05:20,223 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl] (catalina-exec-19:null)
Applying static nat rules in network Ntwk[204|Guest|11]
2013-05-30 08:05:20,288 DEBUG [agent.transport.Request] (catalina-exec-19:null)
Seq 1-1416495169: Sending { Cmd , MgmtId: 7280707764394, via: 1, Ver: v1,
Flags: 11,
[{routing.SetStaticNatRulesCommand:{rules:[{dstIp:10.0.1.188,id:0,srcIp:10.147.44.63,revoked:false,alreadyAdded:false,purpose:StaticNat,icmpType:0,icmpCode:0}],vpcId:1,accessDetails:{router.guest.ip:10.0.1.1,zone.network.type:Advanced,router.ip:10.147.40.62,router.name:r-3-VM},wait:0}}]
}
2013-05-30 08:05:20,288 DEBUG [agent.transport.Request] (catalina-exec-19:null)
Seq 1-1416495169: Executing: { Cmd , MgmtId: 7280707764394, via: 1, Ver: v1,
Flags: 11,
[{routing.SetStaticNatRulesCommand:{rules:[{dstIp:10.0.1.188,id:0,srcIp:10.147.44.63,revoked:false,alreadyAdded:false,purpose:StaticNat,icmpType:0,icmpCode:0}],vpcId:1,accessDetails:{router.guest.ip:10.0.1.1,zone.network.type:Advanced,router.ip:10.147.40.62,router.name:r-3-VM},wait:0}}]
}
2013-05-30 08:05:20,289 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-16:null) Seq 1-1416495169: Executing request
2013-05-30 08:05:20,290 INFO [vmware.resource.VmwareResource]
(DirectAgent-16:10.147.40.12) Executing resource SetFirewallRuleCommand:
{rules:[{dstIp:10.0.1.188,id:0,srcIp:10.147.44.63,revoked:false,alreadyAdded:false,purpose:StaticNat,icmpType:0,icmpCode:0}],vpcId:1,accessDetails:{router.guest.ip:10.0.1.1,zone.network.type:Advanced,router.ip:10.147.40.62,router.name:r-3-VM},wait:0}
2013-05-30 08:05:20,290 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-16:10.147.40.12) Use router's private IP for SSH control. IP :
10.147.40.62
2013-05-30 08:05:21,746 ERROR [utils.ssh.SshHelper]
(DirectAgent-16:10.147.40.12) SSH execution of command /root/firewall.sh -A
-l 10.147.44.63 -r 10.0.1.188 -d 0:0 -G has an error status code in return.
result output: Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.14: option --set-mark requires an argument
Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `eth0'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
2013-05-30 08:05:21,790 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-16:10.147.40.12) Executing script on domain router 10.147.40.62:
/root/firewall.sh -A -l 10.147.44.63 -r 10.0.1.188 -d 0:0 -G
(ii) After changing the firewall.sh as mentioned below, it went fine.
get_dev_list() {
ip link show | grep -e eth[2-9] | awk -F : '{print $2}'
ip link show | grep -e eth1[0-9] | awk -F : '{print $2}'
}
Changed the above
[jira] [Commented] (CLOUDSTACK-2728) 41-42 DB upgrade: add step to upgrade system templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670246#comment-13670246 ] Harikrishna Patnala commented on CLOUDSTACK-2728: - can you provide me the list of Hypervisors we need to upgrade and correspoding URLs to update on the upgrade. Thank you 41-42 DB upgrade: add step to upgrade system templates -- Key: CLOUDSTACK-2728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Alena Prokharchyk Assignee: Harikrishna Patnala Priority: Blocker This bug is a blocker for the DB upgrade testing. As the system vm got changed in CS 4.2, we have to add upgrade steps for 4.1 users. Usually the steps are: 1) While being on 4.1, upload the system template (it should be named properly) 2) During the 4.1 -4.2 db upgrade, the script should change the vm_template_id for all the system vms, to the id of the new template 3) All the system vms have to be restarted afterwards. Right now step #2 is not a part of the DB upgrade script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2761) [VMware] [VPC] Failed to create PF/StaticNAT rules on VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru updated CLOUDSTACK-2761:
---
Attachment: logs.tgz
[VMware] [VPC] Failed to create PF/StaticNAT rules on VPC
-
Key: CLOUDSTACK-2761
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2761
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.2.0
Environment: commit # 8d1189c2ae87216bc1c4a1443f75e9a8629abdc2
Reporter: venkata swamybabu budumuru
Priority: Blocker
Fix For: 4.2.0
Attachments: logs.tgz
Steps to reproduce:
1. Have latest CloudStack build with at least 1 advanced zone
2. Have at least 1 VMware cluster with 1 host.
3. Create a VPC with at least 1 Tier
4. deploy a VM
5. apply an ACL to allow all
6. acquire at least 1 IP
7. create PF/staticNAT on the above created IP to the VM created in step (4)
Observations:
(i) It failed to create staticNAT with the following error
2013-05-30 08:05:20,203 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-38:null) Seq 1-1416495168: Response Received:
2013-05-30 08:05:20,206 DEBUG [agent.transport.Request] (DirectAgent-38:null)
Seq 1-1416495168: Processing: { Ans: , MgmtId: 7280707764394, via: 1, Ver:
v1, Flags: 0, [{routing.IpAssocAnswer:{results:[10.147.44.63 -
success],result:true,wait:0}}] }
2013-05-30 08:05:20,207 DEBUG [agent.transport.Request]
(catalina-exec-19:null) Seq 1-1416495168: Received: { Ans: , MgmtId:
7280707764394, via: 1, Ver: v1, Flags: 0, { IpAssocAnswer } }
2013-05-30 08:05:20,211 INFO [cloud.network.NetworkManagerImpl]
(catalina-exec-19:null) Let VpcVirtualRouter handle StaticNat in network 204
2013-05-30 08:05:20,223 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl] (catalina-exec-19:null)
Applying static nat rules in network Ntwk[204|Guest|11]
2013-05-30 08:05:20,288 DEBUG [agent.transport.Request]
(catalina-exec-19:null) Seq 1-1416495169: Sending { Cmd , MgmtId:
7280707764394, via: 1, Ver: v1, Flags: 11,
[{routing.SetStaticNatRulesCommand:{rules:[{dstIp:10.0.1.188,id:0,srcIp:10.147.44.63,revoked:false,alreadyAdded:false,purpose:StaticNat,icmpType:0,icmpCode:0}],vpcId:1,accessDetails:{router.guest.ip:10.0.1.1,zone.network.type:Advanced,router.ip:10.147.40.62,router.name:r-3-VM},wait:0}}]
}
2013-05-30 08:05:20,288 DEBUG [agent.transport.Request]
(catalina-exec-19:null) Seq 1-1416495169: Executing: { Cmd , MgmtId:
7280707764394, via: 1, Ver: v1, Flags: 11,
[{routing.SetStaticNatRulesCommand:{rules:[{dstIp:10.0.1.188,id:0,srcIp:10.147.44.63,revoked:false,alreadyAdded:false,purpose:StaticNat,icmpType:0,icmpCode:0}],vpcId:1,accessDetails:{router.guest.ip:10.0.1.1,zone.network.type:Advanced,router.ip:10.147.40.62,router.name:r-3-VM},wait:0}}]
}
2013-05-30 08:05:20,289 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-16:null) Seq 1-1416495169: Executing request
2013-05-30 08:05:20,290 INFO [vmware.resource.VmwareResource]
(DirectAgent-16:10.147.40.12) Executing resource SetFirewallRuleCommand:
{rules:[{dstIp:10.0.1.188,id:0,srcIp:10.147.44.63,revoked:false,alreadyAdded:false,purpose:StaticNat,icmpType:0,icmpCode:0}],vpcId:1,accessDetails:{router.guest.ip:10.0.1.1,zone.network.type:Advanced,router.ip:10.147.40.62,router.name:r-3-VM},wait:0}
2013-05-30 08:05:20,290 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-16:10.147.40.12) Use router's private IP for SSH control. IP :
10.147.40.62
2013-05-30 08:05:21,746 ERROR [utils.ssh.SshHelper]
(DirectAgent-16:10.147.40.12) SSH execution of command /root/firewall.sh -A
-l 10.147.44.63 -r 10.0.1.188 -d 0:0 -G has an error status code in return.
result output: Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.14: option --set-mark requires an argument
Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `eth0'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Bad argument `10.147.44.63'
Try `iptables -h' or 'iptables --help' for more information.
2013-05-30 08:05:21,790 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-16:10.147.40.12) Executing script on domain router 10.147.40.62:
[jira] [Commented] (CLOUDSTACK-2736) [Multiple_IP_Ranges] Failed to deploy vm with IP address from new CIDR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670251#comment-13670251
]
Sanjeev N commented on CLOUDSTACK-2736:
---
Observed this issue while deploying vm from new CIDR in Advanced zone shared
network as well.
[Multiple_IP_Ranges] Failed to deploy vm with IP address from new CIDR
---
Key: CLOUDSTACK-2736
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2736
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Latest build from master branch:
Zone: SG enabled advanced zone
Hypervisor:KVM
Reporter: Sanjeev N
Assignee: Bharat Kumar
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.rar
Failed to deploy vm with IP address from new CIDR
Steps to Reproduce:
=
1.Bring up CS with SG enabled advnaced zone with KVM cluster
2.Add guest ip range in new CIDR in the existing default shared network
3.Deploy guest vm with IP address from the new CIDR
Expected Result:
==
IP alias should be created on the VR and VM deployment should be successful
with IP address from the new CIDR
Actual Result:
VM deployment failed
Observations:
===
Configuring dhcp service failed with following exceptions:
2013-05-29 13:04:38,782 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-24:null) submit async job-18, details: AsyncJobVO {id:18,
userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
instanceId: 7, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
cmdOriginator: null, cmdInfo:
{sessionkey:ySm8CvuVNkVVRASycbmxD0Lfby4\u003d,ctxUserId:2,serviceOfferingId:b69fbcae-6cbb-4ac4-9669-a8cc8effe2f3,httpmethod:GET,securitygroupids:a181bf2c-c853-11e2-96ab-06045a66,zoneId:4f13e6b8-aa69-425e-954f-b1852f202266,response:json,templateId:6fb1b1b4-c853-11e2-96ab-06045a66,id:7,networkIds:a26a1c93-83c8-4f41-b6ba-7525e8aa0056,hypervisor:KVM,name:vm1-s2,_:1369827334315,ctxAccountId:2,ctxStartEventId:79,displayname:vm1-s2},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-29 13:04:38,786 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
===END=== 10.146.0.15 -- GET
command=deployVirtualMachinezoneId=4f13e6b8-aa69-425e-954f-b1852f202266templateId=6fb1b1b4-c853-11e2-96ab-06045a66hypervisor=KVMserviceOfferingId=b69fbcae-6cbb-4ac4-9669-a8cc8effe2f3securitygroupids=a181bf2c-c853-11e2-96ab-06045a66networkIds=a26a1c93-83c8-4f41-b6ba-7525e8aa0056displayname=vm1-s2name=vm1-s2response=jsonsessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D_=1369827334315
2013-05-29 13:04:38,789 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-2:job-18) Executing
org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-18
2013-05-29 13:04:40,365 DEBUG [db.Transaction.Transaction]
(Job-Executor-2:job-18) Rolling back the transaction: Time = 131 Name =
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679;
called by
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-NetworkManagerImpl.assignPublicIpAddressFromVlans:370-VirtualNetworkApplianceManagerImpl.configDhcpForSubnet:2798-VirtualRouterElement.configDhcpSupportForSubnet:870-NetworkManagerImpl.prepareElement:1962-NetworkManagerImpl.prepareNic:2077-NetworkManagerImpl.prepare:2018-VirtualMachineManagerImpl.advanceStart:842
2013-05-29 13:04:40,366 INFO
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-18)
Insufficient address capacity
2013-05-29 13:04:40,367 INFO
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-18)
unable to configure dhcp for this VM.
2013-05-29 13:04:40,367 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-18) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: unable to configure
the dhcp service, due to insufficiant address capacityScope=interface
com.cloud.network.Network; id=203
at
com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2078)
at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2018)
at
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670253#comment-13670253 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 406785b4aec457ea24dde13b23529fd8df9c1645 in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=406785b ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Whitespace cleanup Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-659) Enable storage xenmotion support in XenServer 6.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670254#comment-13670254 ] ASF subversion and git services commented on CLOUDSTACK-659: Commit 05b75e9d57c216c19c881ce5ceaed23c4a7e9301 in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=05b75e9 ] CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added VmwareStorageMotionStrategy to deal with storage motion tasks. Added target host parameter to MigrateWithStorageCommand. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a zone. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added VmwareStorageMotionStrategy to application context. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Support for volume live migration across datastores Unit tests for vmware storage motion. These test the VmwareStorageMotionStrategy. CLOUDSTACK-659 Fixing migrate volume. CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a zone. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Support for volume live migration across datastores CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a zone. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Support for volume live migration across datastores CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a zone. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Support for volume live migration across datastores Added vm type to prepareNetworkFromNicInfo in MigrateWithStorageCommand implementation. CLOUDSTACK-2701 - Enable storage migration for VMware resources Fixing attach volume and delete volume cases for volumes that are moved off original path in datastore when created. If volume is not found in root directory or datastore, do search in sub folders. CLOUDSTACK-2701 - Enable storage migration for VMware resources Sending command MigrateWithStorageCommand to source host instead of target host for the case of migration of VM within cluster. CLOUDSTACK-2701 - Enable storage migration for VMware resources Searching for virtual disk during device tear down. Adding dependency of 'cloud-engine-storage' to vmware hypervisor plugin. Add hypervisor capability storage_motion_supported for VMware 5.0 and 5.1 CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added VmwareStorageMotionStrategy to deal with storage motion tasks. Added target host parameter to MigrateWithStorageCommand. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a zone. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added VmwareStorageMotionStrategy to application context. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Support for volume live migration across datastores Unit tests for vmware storage motion. These test the VmwareStorageMotionStrategy. CLOUDSTACK-659 Fixing migrate volume. CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a zone. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Support for volume live migration across datastores Added vm type to prepareNetworkFromNicInfo in MigrateWithStorageCommand implementation. Adding dependency of 'cloud-engine-storage' to vmware hypervisor plugin. Add hypervisor capability storage_motion_supported for VMware 5.0 and 5.1 CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added VmwareStorageMotionStrategy to deal with storage motion tasks. Added target host parameter to MigrateWithStorageCommand. Signed-off-by: Sateesh Chodapuneedi sate...@apache.org CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over VMware Added Resource changes to perform VM live migration along with virtual disks across the clusters in a
[jira] [Resolved] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek resolved CLOUDSTACK-2735. Resolution: Fixed Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Critical Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at
[jira] [Commented] (CLOUDSTACK-2662) Preferred implicit dedication fails with insufficient capacity even if shared hosts are available.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670263#comment-13670263 ] Rajesh Battala commented on CLOUDSTACK-2662: Incorporated the review comments and sent for review. Preferred implicit dedication fails with insufficient capacity even if shared hosts are available. -- Key: CLOUDSTACK-2662 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2662 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Rajesh Battala Priority: Blocker Fix For: 4.2.0 Below are the steps followed : 1)Created a Xen Advanced Zone setup with one cluster and hosts. 2)The host1 has the system VM's deployed and a VM with the root domain. 3)Then created two accounts kiran and kiran2 respectively. 4)Was able to deploy VM's using the preferred and strict implicit dedication for the Account kiran. 5)Then tried to deploy a VM fro the account kiran2 using the preferred implicit service offering. 6)The VM deployment fails saying insufficient resources even we have the host 1 in the shared state. the below error message is observed 2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[U ser|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1 2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) Unable to create a deployment for VM[User|win832pref2] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3206) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2745) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2731) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) The op_host_planner_reservation shows the host dedication details as below: mysql select * from op_host_planner_reservation; +++++-++ | id | data_center_id | pod_id | cluster_id | host_id | resource_usage | +++++-++ | 1 | 1 | 1 | 1 | 1 | Shared | | 2 | 1 | 1 | 1 | 5 | Dedicated | +++++-++ 2 rows in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2662) Preferred implicit dedication fails with insufficient capacity even if shared hosts are available.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670261#comment-13670261 ] Rajesh Battala commented on CLOUDSTACK-2662: Additonal Test cases Executed: = 1. Deploy setup with only one host. Enabling zone will create sys vms on the host and it will be marked as Shared. Deploy VM from the account with Implict preferred. It will try in strict and then tried Shared and created instance in the available single host. Preferred implicit dedication fails with insufficient capacity even if shared hosts are available. -- Key: CLOUDSTACK-2662 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2662 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Rajesh Battala Priority: Blocker Fix For: 4.2.0 Below are the steps followed : 1)Created a Xen Advanced Zone setup with one cluster and hosts. 2)The host1 has the system VM's deployed and a VM with the root domain. 3)Then created two accounts kiran and kiran2 respectively. 4)Was able to deploy VM's using the preferred and strict implicit dedication for the Account kiran. 5)Then tried to deploy a VM fro the account kiran2 using the preferred implicit service offering. 6)The VM deployment fails saying insufficient resources even we have the host 1 in the shared state. the below error message is observed 2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[U ser|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1 2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) Unable to create a deployment for VM[User|win832pref2] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3206) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2745) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2731) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) The op_host_planner_reservation shows the host dedication details as below: mysql select * from op_host_planner_reservation; +++++-++ | id | data_center_id | pod_id | cluster_id | host_id | resource_usage | +++++-++ | 1 | 1 | 1 | 1 | 1 | Shared | | 2 | 1 | 1 | 1 | 5 | Dedicated | +++++-++ 2 rows in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2764) Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760)
Radhika Nair created CLOUDSTACK-2764: Summary: Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760) Key: CLOUDSTACK-2764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2764 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2764) Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670265#comment-13670265 ] Radhika Nair commented on CLOUDSTACK-2764: -- edit configure-acl.xml. -Change the navigation to create ACL rule -Add the new protocol details: All, Protocol (0 to 255) -API changes Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760) --- Key: CLOUDSTACK-2764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2764 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CLOUDSTACK-2764) Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670265#comment-13670265 ] Radhika Nair edited comment on CLOUDSTACK-2764 at 5/30/13 11:36 AM: edit configure-acl.xml. -Change the navigation to create ACL rules -Add the new protocol details: All, Protocol (0 to 255) -API changes was (Author: radhikap): edit configure-acl.xml. -Change the navigation to create ACL rule -Add the new protocol details: All, Protocol (0 to 255) -API changes Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760) --- Key: CLOUDSTACK-2764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2764 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2666) Host is getting dedicated to a Account even when preferred implicit dedication is used.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-2666. Verified this with the latest Build and this is working fine. Host is getting dedicated to a Account even when preferred implicit dedication is used. --- Key: CLOUDSTACK-2666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2666 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kiran Koneti Assignee: Devdeep Singh Priority: Blocker https://issues.apache.org/jira/browse/CLOUDSTACK-26661)Created a Xen Advanced Zone setup with one cluster and hosts. 2)The host1 has the system VM's deployed and a VM with the root domain. 3)Then created two accounts kiran and kiran2 respectively. 4)Deployed VM using the preferred implicit dedication for the Account kiran. 5)Then tried to deploy a VM fro the account kiran2 using the preferred implicit service offering. 6)The VM deployment fails saying insufficient resources The error message is as below 2013-05-24 17:49:33,285 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-26) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|prefacc2]Scope=interface com.cloud.dc.DataCenter; id=1 2013-05-24 17:49:33,287 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-26) Unable to create a deployment for VM[User|prefacc2] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|prefacc2]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3206) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2745) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2731) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Ideally saying the host should not be dedicated to the account kiran but this is getting dedicated which is causing the vm creation failure for the account kiran2. The db shows the host in dedicated state. mysql select * from op_host_planner_reservation; +++++-++ | id | data_center_id | pod_id | cluster_id | host_id | resource_usage | +++++-++ | 1 | 1 | 1 | 1 | 1 | Shared | | 2 | 1 | 1 | 1 | 5 | Dedicated | +++++-++ 2 rows in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2276) NPE while attaching the volume to the instance which is created from ROOT Disk Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670269#comment-13670269
]
ASF subversion and git services commented on CLOUDSTACK-2276:
-
Commit fd79f6b6020ae653c4f2d1f6222685becb792b77 in branch refs/heads/master
from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fd79f6b ]
CLOUDSTACK-2276: NPE while attaching the volume to the instance which is
created from ROOT Disk Snapshot
The NPE comes as the storage pool id is set to null in the in-memory volume
object which is not in sync with the db. entry. Reloading the volume from db.
fixes the issue
NPE while attaching the volume to the instance which is created from ROOT
Disk Snapshot
---
Key: CLOUDSTACK-2276
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2276
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Koushik Das
Priority: Critical
Fix For: 4.2.0
Setup: Advanced Networking Zone with Xen 6.1 , MS -RHEL 6.3
Steps:
1. Deploy instance as ROOT admin
2. Create the snapshot from this instance ROOT disk
3. Create Volume from this snapshot
4. Try to attach this volume to the instance .
Observation:
NPE while attaching the volume to the instance which is created from ROOT
Disk Snapshot
2013-04-29 16:51:02,412 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.144.6.19 -- GET
command=attachVolumeid=3c8487fd-a30f-42d6-bc14-e19ec6c4090cvirtualMachineId=cc2a94bb-bdf0-4d36-9f2c-a501c75f53ddresponse=jsonsessionkey=50KnW0aaOd0wvF2hspe71pXsfqI%3D_=1367234593280
2013-04-29 16:51:02,450 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-41:job-57) Executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-57
2013-04-29 16:51:02,528 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-41:job-57) Checking pool: 1 for volume allocation
[Vol[26|vm=null|DATADISK]], maxSize : 1759218630656, totalAllocatedSize :
108885410816, askingSize : 21474836480, allocated disable threshold: 0.85
2013-04-29 16:51:02,530 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-41:job-57) Trying to create
org.apache.cloudstack.storage.volume.VolumeObject@28b8ef9e on
org.apache.cloudstack.storage.datastore.DefaultPrimaryDataStore@57b82f5
2013-04-29 16:51:02,566 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:26,pool:{id:1,uuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,host:10.102.192.100,path:/cpg_vol/sailaja/masterxenps,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:21474836480,tags:[],type:DATADISK,name:VolumefromsnapshotofROOT15,useLocalStorage:false,recreatable:true,diskOfferingId:1,volumeId:26},templateUrl:c2f7de45-83c8-40a8-9937-a450b0d8660a,wait:0}}]
}
2013-04-29 16:51:02,577 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539: Executing: { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:26,pool:{id:1,uuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,host:10.102.192.100,path:/cpg_vol/sailaja/masterxenps,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:21474836480,tags:[],type:DATADISK,name:VolumefromsnapshotofROOT15,useLocalStorage:false,recreatable:true,diskOfferingId:1,volumeId:26},templateUrl:c2f7de45-83c8-40a8-9937-a450b0d8660a,wait:0}}]
}
2013-04-29 16:51:02,592 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-343:null) Seq 1-1019093539: Executing request
2013-04-29 16:51:02,710 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) SR retrieved for ba45e9e1-5b6f-3005-a920-00c02a73d9e1
2013-04-29 16:51:02,726 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) Checking ba45e9e1-5b6f-3005-a920-00c02a73d9e1 or SR
527d8f70-7760-6381-04bf-2d7f86c7f037 on
XS[40d72111-4e51-4bda-9d2a-65de0f1bebb5-10.102.192.13]
2013-04-29 16:51:02,809 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-04-29 16:51:03,772 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) Succesfully created VDI for
com.cloud.agent.api.storage.CreateCommand. Uuid =
2f8bfe2f-3cf4-4924-899d-0409c776430b
2013-04-29 16:51:03,773 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-343:null) Seq 1-1019093539: Response Received:
2013-04-29 16:51:03,773 DEBUG [agent.transport.Request]
(DirectAgent-343:null) Seq
[jira] [Resolved] (CLOUDSTACK-2276) NPE while attaching the volume to the instance which is created from ROOT Disk Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das resolved CLOUDSTACK-2276.
-
Resolution: Fixed
NPE while attaching the volume to the instance which is created from ROOT
Disk Snapshot
---
Key: CLOUDSTACK-2276
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2276
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Koushik Das
Priority: Critical
Fix For: 4.2.0
Setup: Advanced Networking Zone with Xen 6.1 , MS -RHEL 6.3
Steps:
1. Deploy instance as ROOT admin
2. Create the snapshot from this instance ROOT disk
3. Create Volume from this snapshot
4. Try to attach this volume to the instance .
Observation:
NPE while attaching the volume to the instance which is created from ROOT
Disk Snapshot
2013-04-29 16:51:02,412 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.144.6.19 -- GET
command=attachVolumeid=3c8487fd-a30f-42d6-bc14-e19ec6c4090cvirtualMachineId=cc2a94bb-bdf0-4d36-9f2c-a501c75f53ddresponse=jsonsessionkey=50KnW0aaOd0wvF2hspe71pXsfqI%3D_=1367234593280
2013-04-29 16:51:02,450 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-41:job-57) Executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-57
2013-04-29 16:51:02,528 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-41:job-57) Checking pool: 1 for volume allocation
[Vol[26|vm=null|DATADISK]], maxSize : 1759218630656, totalAllocatedSize :
108885410816, askingSize : 21474836480, allocated disable threshold: 0.85
2013-04-29 16:51:02,530 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-41:job-57) Trying to create
org.apache.cloudstack.storage.volume.VolumeObject@28b8ef9e on
org.apache.cloudstack.storage.datastore.DefaultPrimaryDataStore@57b82f5
2013-04-29 16:51:02,566 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:26,pool:{id:1,uuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,host:10.102.192.100,path:/cpg_vol/sailaja/masterxenps,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:21474836480,tags:[],type:DATADISK,name:VolumefromsnapshotofROOT15,useLocalStorage:false,recreatable:true,diskOfferingId:1,volumeId:26},templateUrl:c2f7de45-83c8-40a8-9937-a450b0d8660a,wait:0}}]
}
2013-04-29 16:51:02,577 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539: Executing: { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:26,pool:{id:1,uuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,host:10.102.192.100,path:/cpg_vol/sailaja/masterxenps,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:21474836480,tags:[],type:DATADISK,name:VolumefromsnapshotofROOT15,useLocalStorage:false,recreatable:true,diskOfferingId:1,volumeId:26},templateUrl:c2f7de45-83c8-40a8-9937-a450b0d8660a,wait:0}}]
}
2013-04-29 16:51:02,592 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-343:null) Seq 1-1019093539: Executing request
2013-04-29 16:51:02,710 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) SR retrieved for ba45e9e1-5b6f-3005-a920-00c02a73d9e1
2013-04-29 16:51:02,726 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) Checking ba45e9e1-5b6f-3005-a920-00c02a73d9e1 or SR
527d8f70-7760-6381-04bf-2d7f86c7f037 on
XS[40d72111-4e51-4bda-9d2a-65de0f1bebb5-10.102.192.13]
2013-04-29 16:51:02,809 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-04-29 16:51:03,772 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) Succesfully created VDI for
com.cloud.agent.api.storage.CreateCommand. Uuid =
2f8bfe2f-3cf4-4924-899d-0409c776430b
2013-04-29 16:51:03,773 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-343:null) Seq 1-1019093539: Response Received:
2013-04-29 16:51:03,773 DEBUG [agent.transport.Request]
(DirectAgent-343:null) Seq 1-1019093539: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 110,
[{storage.CreateAnswer:{volume:{id:26,name:VolumefromsnapshotofROOT15,mountPoint:/cpg_vol/sailaja/masterxenps,path:2f8bfe2f-3cf4-4924-899d-0409c776430b,size:21474836480,type:DATADISK,storagePoolType:NetworkFilesystem,storagePoolUuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,deviceId:0},requestTemplateReload:false,result:true,wait:0}}]
}
2013-04-29 16:51:03,773 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539:
[jira] [Updated] (CLOUDSTACK-2765) Dashboard is showing invalid value for storage Allocated 0.00KB/0.00KB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2765: -- Description: please check screenshot for more detail Database -- mysql select *from op_host_capacity ; ++-++++---+---++---++-+-+ | id | host_id | data_center_id | pod_id | cluster_id | used_capacity | reserved_capacity | total_capacity | capacity_type | capacity_state | update_time | created | ++-++++---+---++---++-+-+ | 1 | 1 | 1 | 1 | 1 |2550136832 | 0 |16190157312 | 0 | Enabled| 2013-05-30 12:34:38 | 2013-05-30 12:19:55 | | 2 | 1 | 1 | 1 | 1 | 2500 | 0 | 9576 | 1 | Enabled| 2013-05-30 12:34:38 | 2013-05-30 12:19:55 | | 3 |NULL | 1 | NULL | NULL | 3 | 0 | 28 | 4 | Enabled| 2013-05-30 12:34:55 | 2013-05-30 12:19:55 | | 4 |NULL | 1 | NULL | NULL | 0 | 0 | 0 | 8 | Enabled| 2013-05-30 12:19:55 | 2013-05-30 12:19:55 | | 5 |NULL | 1 | NULL | NULL | 1 | 0 | 10 | 7 | Enabled| 2013-05-30 12:34:55 | 2013-05-30 12:19:55 | | 6 |NULL | 1 | 1 | NULL | 3 | 0 | 10 | 5 | Enabled| 2013-05-30 12:24:55 | 2013-05-30 12:19:55 | | 7 | 3 | 1 | 1 | 1 | 36995040256 | 0 |58210910208 | 3 | Enabled| 2013-05-30 17:26:41 | 2013-05-30 12:22:39 | ++-++++---+---++---++-+-+ Storage detail - [root@RHEL62 ~]# df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg_rhel62-lv_root 28G 9.9G 16G 39% / tmpfs 499M 0 499M 0% /dev/shm /dev/sda1 485M 32M 428M 7% /boot /tmp/iso/rhel-server-6.2-x86_64-dvd.iso 3.4G 3.4G 0 100% /media was: please check screen shot for more detail Database -- mysql select *from op_host_capacity ; ++-++++---+---++---++-+-+ | id | host_id | data_center_id | pod_id | cluster_id | used_capacity | reserved_capacity | total_capacity | capacity_type | capacity_state | update_time | created | ++-++++---+---++---++-+-+ | 1 | 1 | 1 | 1 | 1 |2550136832 | 0 |16190157312 | 0 | Enabled| 2013-05-30 12:34:38 | 2013-05-30 12:19:55 | | 2 | 1 | 1 | 1 | 1 | 2500 | 0 | 9576 | 1 | Enabled| 2013-05-30 12:34:38 | 2013-05-30 12:19:55 | | 3 |NULL | 1 | NULL | NULL | 3 | 0 | 28 | 4 | Enabled| 2013-05-30 12:34:55 | 2013-05-30 12:19:55 | | 4 |NULL | 1 | NULL | NULL | 0 | 0 | 0 | 8 | Enabled| 2013-05-30 12:19:55 | 2013-05-30 12:19:55 | | 5 |NULL | 1 | NULL | NULL | 1 | 0 | 10 | 7 | Enabled| 2013-05-30 12:34:55 | 2013-05-30 12:19:55 | | 6 |NULL | 1 | 1 | NULL | 3 | 0 | 10 | 5 | Enabled| 2013-05-30 12:24:55 | 2013-05-30 12:19:55 | | 7 | 3 | 1 | 1 | 1 | 36995040256 | 0 |58210910208 | 3 | Enabled| 2013-05-30 17:26:41 | 2013-05-30 12:22:39 | ++-++++---+---++---++-+-+ Storage detail
[jira] [Updated] (CLOUDSTACK-2765) Dashboard is showing invalid value for storage Allocated 0.00KB/0.00KB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2765: -- Attachment: Dashboard.png MSlogs.rar Dashboard is showing invalid value for storage Allocated 0.00KB/0.00KB -- Key: CLOUDSTACK-2765 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2765 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Storage Controller Affects Versions: 4.2.0 Reporter: prashant kumar mishra Priority: Critical Fix For: 4.2.0 Attachments: Dashboard.png, MSlogs.rar please check screenshot for more detail Database -- mysql select *from op_host_capacity ; ++-++++---+---++---++-+-+ | id | host_id | data_center_id | pod_id | cluster_id | used_capacity | reserved_capacity | total_capacity | capacity_type | capacity_state | update_time | created | ++-++++---+---++---++-+-+ | 1 | 1 | 1 | 1 | 1 |2550136832 | 0 |16190157312 | 0 | Enabled| 2013-05-30 12:34:38 | 2013-05-30 12:19:55 | | 2 | 1 | 1 | 1 | 1 | 2500 | 0 | 9576 | 1 | Enabled| 2013-05-30 12:34:38 | 2013-05-30 12:19:55 | | 3 |NULL | 1 | NULL | NULL | 3 | 0 | 28 | 4 | Enabled| 2013-05-30 12:34:55 | 2013-05-30 12:19:55 | | 4 |NULL | 1 | NULL | NULL | 0 | 0 | 0 | 8 | Enabled| 2013-05-30 12:19:55 | 2013-05-30 12:19:55 | | 5 |NULL | 1 | NULL | NULL | 1 | 0 | 10 | 7 | Enabled| 2013-05-30 12:34:55 | 2013-05-30 12:19:55 | | 6 |NULL | 1 | 1 | NULL | 3 | 0 | 10 | 5 | Enabled| 2013-05-30 12:24:55 | 2013-05-30 12:19:55 | | 7 | 3 | 1 | 1 | 1 | 36995040256 | 0 |58210910208 | 3 | Enabled| 2013-05-30 17:26:41 | 2013-05-30 12:22:39 | ++-++++---+---++---++-+-+ Storage detail - [root@RHEL62 ~]# df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg_rhel62-lv_root 28G 9.9G 16G 39% / tmpfs 499M 0 499M 0% /dev/shm /dev/sda1 485M 32M 428M 7% /boot /tmp/iso/rhel-server-6.2-x86_64-dvd.iso 3.4G 3.4G 0 100% /media -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670281#comment-13670281 ] Abhinandan Prateek commented on CLOUDSTACK-2735: When patches 9 and 10, which are responsible for the PV driver installation, are installed .Then the hosts are adding without issues and PV drivers can also be installed successfully. Unable to Add two Xen hosts(6.1 with all updates/patches) in a cluster. --- Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Abhinandan Prateek Priority: Critical Fix For: 4.2.0 Attachments: management-server.zip Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message 2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 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:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at
[jira] [Commented] (CLOUDSTACK-2501) Scalevm - Need to take care of upgraded vms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670282#comment-13670282 ] Nitin Mehta commented on CLOUDSTACK-2501: - Done for XS by commit 0a5e3fa60778ccd4ac22a99809498372399405f6 Scalevm - Need to take care of upgraded vms --- Key: CLOUDSTACK-2501 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2501 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 In case the vms were created prior to 4.2 they wont be scalable unless they are restarted because there are attributes that are set during the start command. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2766) [VPC]Firewall service should not be enabled for acquired public IPs in VPC as the VPC VR provides option to configure Network ACLs.
manasaveloori created CLOUDSTACK-2766: - Summary: [VPC]Firewall service should not be enabled for acquired public IPs in VPC as the VPC VR provides option to configure Network ACLs. Key: CLOUDSTACK-2766 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2766 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: manasaveloori Priority: Minor Fix For: 4.2.0 Steps: 1. Have a CS with Advanced zone. 2. Create a VPC. 3. For the VPC created in step2 go to public ip addresses and acquire an ip. Observation: For the acquired IP,under configuration tab-Firewall service option should be disabled as VPC VR provides option to configure Network ACLs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2767) There is no API/UI cehck on input parameters for Global settings,zone settings and account settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2767: -- Affects Version/s: 4.2.0 There is no API/UI cehck on input parameters for Global settings,zone settings and account settings -- Key: CLOUDSTACK-2767 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2767 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server, UI Affects Versions: 4.2.0 Reporter: prashant kumar mishra -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2767) There is no API/UI cehck on input parameters for Global settings,zone settings and account settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2767: -- Fix Version/s: 4.2.0 There is no API/UI cehck on input parameters for Global settings,zone settings and account settings -- Key: CLOUDSTACK-2767 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2767 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server, UI Affects Versions: 4.2.0 Reporter: prashant kumar mishra Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2767) There is no API/UI cehck on input parameters for Global settings,zone settings and account settings
prashant kumar mishra created CLOUDSTACK-2767: - Summary: There is no API/UI cehck on input parameters for Global settings,zone settings and account settings Key: CLOUDSTACK-2767 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2767 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, Management Server, UI Reporter: prashant kumar mishra -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2768) [SXM] snapshot on a migrated volume is getting NULL path
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-2768: - Attachment: management-server.log.zip [SXM] snapshot on a migrated volume is getting NULL path - Key: CLOUDSTACK-2768 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2768 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Snapshot Affects Versions: 4.2.0 Reporter: Srikanteswararao Talluri Priority: Critical Fix For: 4.2.0 Attachments: management-server.log.zip Steps to reproduce: 1. create two clusters [C1,C2]with two primary storages[P1,P2] respectively. 2. deploy a VM VM1 and attach 2 data volumes V1,V2. 3. migrate volume V1. 4. While volume V1 is being migrated, Migrate VM1 with volumes to Cluster C2. Step 4 will result in failure and all the volumes and VM should be as it was before migrate operation. 5. Now, take a snapshot of volume V1 OR V2. This is updating the path in the snapshot table as NULL, which in turn results in Null pointer exception on snapshot operations(template/volume creation from snapshot) id: 3 data_center_id: 1 account_id: 2 domain_id: 1 volume_id: 25 disk_offering_id: 5 status: BackedUp path: NULL name: sharedshared_tt_20130530164422 uuid: 3ba59708-cb37-4019-a54c-5f6db4eaa36d snapshot_type: 0 type_description: MANUAL size: 107374182400 created: 2013-05-30 16:44:22 removed: NULL backup_snap_id: NULL swift_id: NULL sechost_id: NULL prev_snap_id: 0 hypervisor_type: XenServer version: 2.2 s3_id: NULL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2764) Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670302#comment-13670302 ] ASF subversion and git services commented on CLOUDSTACK-2764: - Commit dd9b75020cf0bb0dcbabcb95775160c0c2c83f94 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dd9b750 ] CLOUDSTACK-2764 Documentation - Allow ACL on all layer 4 protocols (CLOUDSTACK-760) --- Key: CLOUDSTACK-2764 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2764 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2619) Volume created from Snapshot does not attach to the VM.fails with NPE.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das reassigned CLOUDSTACK-2619:
---
Assignee: Koushik Das
Volume created from Snapshot does not attach to the VM.fails with NPE.
--
Key: CLOUDSTACK-2619
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2619
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Assignee: Koushik Das
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.zip
1)Create a VMware Advanced Zone setup.
2)Once the Builtin template is downloaded then created a Vm and took snapshot
for the same.
3)Created a volume from the snapshot created in the step 2.
4) I see the volume creation was successful in the UI.
5)Tried to check the volume details but couldn't find it either in primary
nor in secondary storage.
6)Observed the Volumes details in the DB and it shows state as allocated and
the Location as Null.
*** 6. row ***
id: 6
account_id: 2
domain_id: 1
pool_id: NULL
last_pool_id: NULL
instance_id: NULL
device_id: NULL
name: CreatedVolume
uuid: 858d9047-899b-4d2a-95fe-d1ac33154aa8
size: 2147483648
folder: NULL
path: c394b91e99774acd8e9c30f890d3
pod_id: NULL
data_center_id: 1
iscsi_name: NULL
host_ip: NULL
volume_type: DATADISK
pool_type: NULL
disk_offering_id: 2
template_id: 7
first_snapshot_backup_uuid: NULL
recreatable: 0
created: 2013-05-22 14:18:28
attached: NULL
updated: 2013-05-22 14:18:28
removed: NULL
state: Allocated
chain_info: NULL
update_count: 0
disk_type: NULL
display_volume: 1
6 rows in set (0.00 sec)
Then I tried to attach this volume to a VM and it fails with an NPE as
mentioned below
2013-05-22 20:16:02,983 DEBUG [agent.transport.Request]
(DirectAgent-202:null) Seq 1-1002242356: Processing: { Ans: , MgmtId:
6703101771911, via: 1, Ver: v1, Flags: 110,
[{storage.CreateAnswer:{volume:{id:6,name:CreatedVolume,mountPoint:/export/home/kiran/p1,path:a300f5598c63435c948deb4cc313a4b7,size:2147483648,type:DATADISK,storagePoolType:NetworkFilesystem,storagePoolUuid:b4825bd6-2b6d-33ef-b324-bfbbec982716,deviceId:0},requestTemplateReload:false,result:true,wait:0}}]
}
2013-05-22 20:16:02,985 DEBUG [agent.transport.Request]
(Job-Executor-17:job-17) Seq 1-1002242356: Received: { Ans: , MgmtId:
6703101771911, via: 1, Ver: v1, Flags: 110, { CreateAnswer } }
2013-05-22 20:16:02,990 DEBUG [agent.manager.AgentAttache]
(DirectAgent-202:null) Seq 1-1002242356: No more commands found
2013-05-22 20:16:03,062 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1500)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1730)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-22 20:16:03,065 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17) Complete async job-17, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: null
Attaching the management server
[jira] [Resolved] (CLOUDSTACK-2619) Volume created from Snapshot does not attach to the VM.fails with NPE.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das resolved CLOUDSTACK-2619.
-
Resolution: Duplicate
Volume created from Snapshot does not attach to the VM.fails with NPE.
--
Key: CLOUDSTACK-2619
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2619
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Assignee: Koushik Das
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.zip
1)Create a VMware Advanced Zone setup.
2)Once the Builtin template is downloaded then created a Vm and took snapshot
for the same.
3)Created a volume from the snapshot created in the step 2.
4) I see the volume creation was successful in the UI.
5)Tried to check the volume details but couldn't find it either in primary
nor in secondary storage.
6)Observed the Volumes details in the DB and it shows state as allocated and
the Location as Null.
*** 6. row ***
id: 6
account_id: 2
domain_id: 1
pool_id: NULL
last_pool_id: NULL
instance_id: NULL
device_id: NULL
name: CreatedVolume
uuid: 858d9047-899b-4d2a-95fe-d1ac33154aa8
size: 2147483648
folder: NULL
path: c394b91e99774acd8e9c30f890d3
pod_id: NULL
data_center_id: 1
iscsi_name: NULL
host_ip: NULL
volume_type: DATADISK
pool_type: NULL
disk_offering_id: 2
template_id: 7
first_snapshot_backup_uuid: NULL
recreatable: 0
created: 2013-05-22 14:18:28
attached: NULL
updated: 2013-05-22 14:18:28
removed: NULL
state: Allocated
chain_info: NULL
update_count: 0
disk_type: NULL
display_volume: 1
6 rows in set (0.00 sec)
Then I tried to attach this volume to a VM and it fails with an NPE as
mentioned below
2013-05-22 20:16:02,983 DEBUG [agent.transport.Request]
(DirectAgent-202:null) Seq 1-1002242356: Processing: { Ans: , MgmtId:
6703101771911, via: 1, Ver: v1, Flags: 110,
[{storage.CreateAnswer:{volume:{id:6,name:CreatedVolume,mountPoint:/export/home/kiran/p1,path:a300f5598c63435c948deb4cc313a4b7,size:2147483648,type:DATADISK,storagePoolType:NetworkFilesystem,storagePoolUuid:b4825bd6-2b6d-33ef-b324-bfbbec982716,deviceId:0},requestTemplateReload:false,result:true,wait:0}}]
}
2013-05-22 20:16:02,985 DEBUG [agent.transport.Request]
(Job-Executor-17:job-17) Seq 1-1002242356: Received: { Ans: , MgmtId:
6703101771911, via: 1, Ver: v1, Flags: 110, { CreateAnswer } }
2013-05-22 20:16:02,990 DEBUG [agent.manager.AgentAttache]
(DirectAgent-202:null) Seq 1-1002242356: No more commands found
2013-05-22 20:16:03,062 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1500)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1730)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-22 20:16:03,065 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17) Complete async job-17, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: null
Attaching the management server
[jira] [Assigned] (CLOUDSTACK-2740) Talk with Hugo
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna reassigned CLOUDSTACK-2740: Assignee: tuna Talk with Hugo -- Key: CLOUDSTACK-2740 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2740 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna Talking with Hugo for the beginning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1784) GSoC: Integration project to deploy and use Mesos on a CloudStack based cloud
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dharmesh Kakadia updated CLOUDSTACK-1784: - Assignee: Dharmesh Kakadia GSoC: Integration project to deploy and use Mesos on a CloudStack based cloud - Key: CLOUDSTACK-1784 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1784 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: Future Reporter: sebastien goasguen Assignee: Dharmesh Kakadia Labels: gsoc2013 In this project student(s), will deploy a CloudStack based cloud and use mesos to schedule tasks on the resulting virtual clusters. They will show how to run traditional parallel application with MPI and big data application with Hadoop/Map Reduce. This is primarily an integration project that will result in a proof of concept. Bootstrap code will most likely be created to dynamically provision the virtual clusters and configure mesos on the resulting nodes. We envision a set of puppet or chef recipes and some Python boostrapping code. Potentially this could be an extension of the apache incubating Provisionr project Language: Java, bash, python Knowledge: system administration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-1779) GSoC: Add Xen/XCP support for GRE SDN controller
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna reassigned CLOUDSTACK-1779: Assignee: tuna GSoC: Add Xen/XCP support for GRE SDN controller Key: CLOUDSTACK-1779 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1779 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: Future Reporter: sebastien goasguen Assignee: tuna Labels: gsoc2013 Apache CloudStack has a native Software Define Networking (SDN) controller that manages GRE tunnels between hypervisors. This allows isolation of tenants in the cloud. Currently the controller only supports Xen Server. This project would extend support to open source Xen and XCP hypervisors. Language: Java, bash, python Knowledge: networking, open switch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-2725:
Summary: [Automation] Re-attaching volume on VM failing in KVM (was:
[Automation] [Object_Store_Refactor]Re-attaching volume on VM failing in KVM)
[Automation] Re-attaching volume on VM failing in KVM
-
Key: CLOUDSTACK-2725
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: Object Store branch
(1647f0a287f7ac027c7b1fa18a17523ad8e3c042)
Automation environment KVM
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
Fix For: 4.2.0
Attachments: CLOUDSTACK-2725.rar
Below two test case failing from BVT
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume
Steps to reproduce
Step 1 : Create an account, service offering, create volume, create VM
Step 2 : Attach volume to VM ,
Step 3 : Detach volume
Step 4 : Attach volume to VM again
Actual result
Attachment failed with below error
2013-05-28 13:45:39,101 DEBUG [agent.transport.Request]
(Job-Executor-98:job-1246) Seq 5-258539658: Rec
eived: { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, {
AttachAnswer } }
2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-98:job-1246) Unexpected e
xception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
TestDiskServ to VM: ce79edb6-
a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error
unable to execute QEMU comman
d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
at
com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
t(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
22)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-98:job-1246) Complete asy
nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
text: Failed to attach volume
: TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e;
org.libvirt.LibvirtException: internal erro
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-2725:
Environment:
Automation environment KVM
Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
was:
Object Store branch (1647f0a287f7ac027c7b1fa18a17523ad8e3c042)
Automation environment KVM
[Automation] Re-attaching volume on VM failing in KVM
-
Key: CLOUDSTACK-2725
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: Automation environment KVM
Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
Fix For: 4.2.0
Attachments: CLOUDSTACK-2725.rar
Below two test case failing from BVT
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume
Steps to reproduce
Step 1 : Create an account, service offering, create volume, create VM
Step 2 : Attach volume to VM ,
Step 3 : Detach volume
Step 4 : Attach volume to VM again
Actual result
Attachment failed with below error
2013-05-28 13:45:39,101 DEBUG [agent.transport.Request]
(Job-Executor-98:job-1246) Seq 5-258539658: Rec
eived: { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, {
AttachAnswer } }
2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-98:job-1246) Unexpected e
xception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
TestDiskServ to VM: ce79edb6-
a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error
unable to execute QEMU comman
d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
at
com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
t(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
22)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-98:job-1246) Complete asy
nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
text: Failed to attach volume
: TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e;
org.libvirt.LibvirtException: internal erro
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-2285) [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy reopened CLOUDSTACK-2285: -- ee317287b3981200ec1a54ee096600fd24a16475 does not cleanly fix the issue. So reopening the bug. [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone -- Key: CLOUDSTACK-2285 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2285 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: commit 0e2ffe72aa641f4551cae63fbc36454c5934342f Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Attachments: api.log.tgz Steps to reproduce : 1. Have a basic zone setup with at least one XEN cluster using the offering DefaultSharedNetworkOfferingWithSGService 2. Try addNetscalerLoadBalancer with GSLB enabled Observations: (i) It gets added successfully. command=addNetscalerLoadBalancerphysicalnetworkid=4dbe1d3c-1cee-4f88-aeca-45c4a8a76b4dusername=nsrootpassword=nsrootnetworkdevicetype=NetscalerVPXLoadBalancergslbprovider=truegslbproviderpublicip=1.1.1.1gslbproviderprivateip=1.1.1.1url=https://10.147.54.5?publicinterface=1/1privateinterface=1/2numretries=2lbdevicededicated=false; mysql select id,name,networktype from data_center where id=1; ++---+-+ | id | name | networktype | ++---+-+ | 1 | zone1 | Basic | ++---+-+ mysql select * from external_load_balancer_devices where id=2\G *** 1. row *** id: 2 uuid: 8c467bfc-7ac3-410a-92d7-11e5853a5d79 physical_network_id: 200 provider_name: Netscaler device_name: NetscalerVPXLoadBalancer capacity: 50 device_state: Enabled allocation_state: Free is_dedicated: 0 is_managed: 0 host_id: 15 parent_host_id: 0 is_gslb_provider: 1 gslb_site_publicip: NULL gslb_site_privateip: 1.1.1.1 (ii) There is no need for enabling GSLB functionality in basic zones created with above network offerings because there is no LB feature enabled in this case. May be having a check at the API level and allowing it only based on type of zone will help in this case but, if we are supporting GSLB for ELB enabled zones then we need to handle that situation as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2059) Support remove network over VMware deployments with dvSwitch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-2059: - Issue Type: Bug (was: Improvement) Support remove network over VMware deployments with dvSwitch Key: CLOUDSTACK-2059 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2059 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 Remove network from user VM is supported in VMware only for standard vSwitches. This need to be supported for dvSwitches as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2432) AES NI module in the VR is installled but it does not seem to work with openssl
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-2432: --- Summary: AES NI module in the VR is installled but it does not seem to work with openssl (was: AES NI module in the VR is installled but it dose not seem to work with openssl) AES NI module in the VR is installled but it does not seem to work with openssl --- Key: CLOUDSTACK-2432 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2432 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0 Reporter: Bharat Kumar Assignee: Abhinandan Prateek Priority: Blocker Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2746) [VPC UI]: when tier with Internal LB is created, UI doesn't let you create the tier with public LB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-2746: -- Summary: [VPC UI]: when tier with Internal LB is created, UI doesn't let you create the tier with public LB (was: VPC: when tier with Internal LB is created, UI doesn't let you create the tier with public LB) [VPC UI]: when tier with Internal LB is created, UI doesn't let you create the tier with public LB -- Key: CLOUDSTACK-2746 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2746 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Fix For: 4.2.0 Steps to reproduce: = 1) Create network offering with Internal LB support. 2) Create VPC 3) Add first network to the VPC using the network offering with Internal LB. Bug: when try to add the second network, the network offering with the public LB support is not shown in the UI (the offering is present in the api response of the call the UI makes) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2744) [VPC UI] Create Network offering (VPC): when Public type of the LB selected, don't show internalLBVm in the list of providers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-2744: -- Summary: [VPC UI] Create Network offering (VPC): when Public type of the LB selected, don't show internalLBVm in the list of providers (was: Create Network offering (VPC): when Public type of the LB selected, don't show internalLBVm in the list of providers) [VPC UI] Create Network offering (VPC): when Public type of the LB selected, don't show internalLBVm in the list of providers - Key: CLOUDSTACK-2744 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2744 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Fix For: 4.2.0 Steps to reproduce: 1) Open Create Network offering dialog 2) Select LB service. 3) Select Public LB from the drop down list. bug: Internal LB VM shouldn't be shown in the providers list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2743) [VPC UI] Create Internal LB rule: sourcePort/instancePort edit boxes titles should begin with uppercase letter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-2743: -- Summary: [VPC UI] Create Internal LB rule: sourcePort/instancePort edit boxes titles should begin with uppercase letter (was: Create Internal LB rule: sourcePort/instancePort edit boxes titles should begin with uppercase letter) [VPC UI] Create Internal LB rule: sourcePort/instancePort edit boxes titles should begin with uppercase letter -- Key: CLOUDSTACK-2743 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2743 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Priority: Minor Fix For: 4.2.0 The subject says it all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2745) [VPC UI] Internal LB rules view: display source and instance port info on the general view
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-2745: -- Summary: [VPC UI] Internal LB rules view: display source and instance port info on the general view (was: Internal LB rules view: display source and instance port info on the general view) [VPC UI] Internal LB rules view: display source and instance port info on the general view -- Key: CLOUDSTACK-2745 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2745 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Fix For: 4.2.0 1) Get rid of Rules tab as there is just one rule per load balancer is supported 2) Display information about source and instance port on the general view for the internal load balancers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2711) UpdateDefaultNicForVirtualMachine api is not updating default nic on VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670572#comment-13670572 ] Animesh Chaturvedi commented on CLOUDSTACK-2711: Marcus can you check on this issue? UpdateDefaultNicForVirtualMachine api is not updating default nic on VM --- Key: CLOUDSTACK-2711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2711 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-410-rhel6.3 Reporter: shweta agarwal Priority: Blocker Fix For: 4.2.0 Repro steps: 1.Create a VM 2. Create a Network 3.Add this Network to VM 4. Reboot the VM inorder to reflect the changes of new nic 5.Make the newly added nic as Default nic 6. Reboot the VM Bug: Even after rebooting the VM ;it shows old Default Nic as default one Expected Result: After VM reboots , Default nic should be updated My sql shows Default nic for a vm as id uuid instance_id mac_address ip4_address netmask gateway ip_type broadcast_uri network_idmode state reserver_name reservation_iddevice_id update_time isolation_uri ip6_address default_nic vm_type created removed ip6_gateway ip6_cidr secondary_ip display_nic 40 cd8deae5-ebc4-45ba-998b-5e14afe39d01 3 02:00:6b:dc:00:01 10.1.4.98 255.255.255.0 10.1.4.1 Ip4 vlan://1041 208 Dhcp Reserved ExternalGuestNetworkGuru0 2013-05-28 10:02:57 vlan://1041 1 User 2013-05-28 11:30:54 0 1 VM entries for ip route show 10.1.4.0/24 dev eth1 proto kernel scope link src 10.1.4.98 10.1.5.0/24 dev eth2 proto kernel scope link src 10.1.5.49 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.47 169.254.0.0/16 dev eth2 scope link default via 10.1.1.1 dev eth0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2769) UI:API: UI lists deleted project and upon selecting the project an error is received
Parth Jagirdar created CLOUDSTACK-2769: -- Summary: UI:API: UI lists deleted project and upon selecting the project an error is received Key: CLOUDSTACK-2769 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2769 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Attachments: project_deleted2.jpg, project_deleted.jpg UI lists project that has been deleted. Steps:: Create a project. Create an instance within it. Destroy instance. Delete the project. Observe project is still listed on UI. and Upon selecting it, an error message is received. Refer to attached screens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2769) UI:API: UI lists deleted project and upon selecting the project an error is received
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-2769: --- Attachment: project_deleted2.jpg project_deleted.jpg UI:API: UI lists deleted project and upon selecting the project an error is received Key: CLOUDSTACK-2769 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2769 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Attachments: project_deleted2.jpg, project_deleted.jpg UI lists project that has been deleted. Steps:: Create a project. Create an instance within it. Destroy instance. Delete the project. Observe project is still listed on UI. and Upon selecting it, an error message is received. Refer to attached screens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-2730:
---
Assignee: Venkata Siva Vijayendra Bhamidipati
vmware:addcluster failed in basiczone
-
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Blocker
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
restart_required: 0
created: 2013-05-29 12:21:04
removed: NULL
specify_ip_ranges: 1
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
{ createzoneresponse : { zone :
{id:c642382d-8587-4cd7-a1e9-5a488bb47da7,name:zone1,dns1:10.103.128.16,internaldns1:10.103.128.16,networktype:Basic,securitygroupsenabled:true,allocationstate:Disabled,zonetoken:68de3ddf-3a08-3371-9506-a57a4a0a8af5,dhcpprovider:VirtualRouter,localstorageenabled:false}
} }
[jira] [Assigned] (CLOUDSTACK-2770) UI to add Baremetal DHCP server, Baremetal PXE server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-2770: Assignee: Jessica Wang UI to add Baremetal DHCP server, Baremetal PXE server - Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2770) UI to add Baremetal DHCP server, Baremetal PXE server
Jessica Wang created CLOUDSTACK-2770: Summary: UI to add Baremetal DHCP server, Baremetal PXE server Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jessica Wang -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2687) NPE with deploy VM when there are no resources available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670656#comment-13670656 ] Alena Prokharchyk commented on CLOUDSTACK-2687: --- Sailaja, what is the last commit id of the CS version you found this bug in? NPE with deploy VM when there are no resources available - Key: CLOUDSTACK-2687 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2687 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Sailaja Mada Fix For: 4.2.0 Setup : Advanced Zone Steps : 1. Try to deploy VM when there are resources unavailable ( Host does not enough resources Or host is in alert state ) Observation : 2013-05-27 11:24:18,951 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-57:job-101) Destroying vm VM[User|c8a3fb3f-e264-4b09-b6b6-1e2b07a20df1] as it failed to create on Host with Id:null 2013-05-27 11:24:18,966 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-101) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null 2013-05-27 11:24:18,974 WARN [apache.cloudstack.alerts] (Job-Executor-57:job-101) alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: Failed to deploy Vm with Id: 11, on Host with Id: null 2013-05-27 11:24:19,322 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-57:job-101) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd java.lang.NullPointerException at com.cloud.vm.UserVmManagerImpl.finalizeStop(UserVmManagerImpl.java:3041) at com.cloud.vm.VirtualMachineManagerImpl.sendStop(VirtualMachineManagerImpl.java:978) at com.cloud.vm.VirtualMachineManagerImpl.cleanup(VirtualMachineManagerImpl.java:1005) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:932) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3185) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2726) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2712) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:419) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-05-27 11:24:19,323 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-57:job-101) Complete async job-101, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null 2013-05-27 11:24:20,498 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) ===START=== 10.144.6.19 -- GET command=queryAsyncJobResultjobId=74563444-5481-4145-a0ab-f80e1db4response=jsonsessionkey=6Y8QsASlVJM2%2F%2BzSeYZnDac1lD8%3D_=1369634220149 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2506) create network dialog is not displaying network offerings with specifyvlan=true to admin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670669#comment-13670669 ] Alena Prokharchyk commented on CLOUDSTACK-2506: --- The bug should be fixed to bring this feature to the UI: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Vlan+assignment+to+Isolated+network 1) Don't change anything in User/domainAdmin UI. 2) In root admin UI, change listNetworks call that Shweta mentioned in the bug description - remove specifyVlan=false from the call. 3) When admin picks up the offering with specifyVlan=true from the drop down, display one more edit box Vlan (required field for this type of offering). Pass the value of the edit box to the createNetwork call (parameter name is vlan). create network dialog is not displaying network offerings with specifyvlan=true to admin Key: CLOUDSTACK-2506 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2506 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-329-rhel6.3 Reporter: shweta agarwal Priority: Critical Fix For: 4.2.0 Repro steps: 1. Create a network offerings with specify vlan=true 2. As a root admin Goto network tab and open create network dialog Bug: Notice its not showing network offerings created in step 1 Expected result: It should show the network offerings created in step1 Actually When we open create network dialog presently its only firing following api http://10.147.59.212:8080/client/api?command=listNetworkOfferingszoneid=dd1f4b0f-bc77-4b3b-8f47-45130d4b816aforVpc=falseresponse=jsonsessionkey=dNddt90WhymsHK2%2FNj9eD5fZbWk%3Dguestiptype=IsolatedsupportedServices=SourceNatspecifyvlan=falsestate=Enabled_=1368600062363 it need to fire one more api with specifyvlan=true param value for isolated network -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2770) UI to add Baremetal DHCP server, Baremetal PXE server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-2770: - Description: http://support.citrix.com/article/CTX135163 Cannot Add PXE/DHCP Server to Setup BareMetal Provisioning UI to add Baremetal DHCP server, Baremetal PXE server - Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang http://support.citrix.com/article/CTX135163 Cannot Add PXE/DHCP Server to Setup BareMetal Provisioning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670682#comment-13670682 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2730: - Sadhu, I was able to create a basic zone with network offering as DefaultSharedNetworkOffering. I didn't face the issue mentioned above. We cannot use the DefaultSharedNetworkOfferingWithSGService for VMWare - ESX doesn't have iptables support and so we cannot program a VR to support security groups at L3 on ESX. Instead, PVLAN support was put in for VMware deployments in order to provide functionally similar isolation between VMs. What network offering did you use during the basic zone creation? If the latter, can you please check the result of using the former? In my setup, though the zone creation went through fine, I ran into an exception when attempting to create a guest VM. This is the exception I hit: WARN [apache.cloudstack.alerts] (Job-Executor-9:job-9) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated. at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) That is however a completely different bug, so I'll log one for it to track it separately. Since I'm not running into issues with basic zone creation on master, I'll downgrade this bug from blocker to major. Regards, Vijay vmware:addcluster failed in basiczone - Key: CLOUDSTACK-2730 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: sadhu suresh Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Attachments: management-server.log In case of vmware ,when i try to configure basic zone with shared network.addcluster failed with Creating cluster Something went wrong; please correct the following:Don't support hypervisor type VMware in advanced security enabled zone even though i select the bassic and shared network. 1.select the zone type as basic 2.select the network type as shared 3.provide pod ,guest details and configure primary and secondary detaisl 4.click on finish to create basic zone with shared network mode Actual result: even though i select shared network in basic zone,it sends security group enble to true internally. due to this addcluster failed . It throws following error: Creating cluster Something went wrong; please correct the following:Don't support hypervisor type VMware in advanced security enabled zone mysql select * from data_center where id=2\G; *** 1. row *** id: 2 name: zone1 uuid:
[jira] [Updated] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-2730:
Priority: Major (was: Blocker)
vmware:addcluster failed in basiczone
-
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
acl_type: Domain
network_domain: cs1cloud.internal
reservation_id: NULL
guest_type: Shared
restart_required: 0
created: 2013-05-29 12:21:04
removed: NULL
specify_ip_ranges: 1
vpc_id: NULL
ip6_gateway: NULL
ip6_cidr: NULL
network_cidr: NULL
display_network: 1
network_acl_id: NULL
1 row in set (0.00 sec)
http://10.147.59.83:8080/client/api?command=createZonenetworktype=Basicname=zone1dns1=10.103.128.16internaldns1=10.103.128.16response=jsonsessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D_=1369810303912
{ createzoneresponse : { zone :
{id:c642382d-8587-4cd7-a1e9-5a488bb47da7,name:zone1,dns1:10.103.128.16,internaldns1:10.103.128.16,networktype:Basic,securitygroupsenabled:true,allocationstate:Disabled,zonetoken:68de3ddf-3a08-3371-9506-a57a4a0a8af5,dhcpprovider:VirtualRouter,localstorageenabled:false}
} }
[jira] [Resolved] (CLOUDSTACK-750) nTier Apps 2.0 : KVM Hypervisor support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonny Chhen resolved CLOUDSTACK-750. Resolution: Fixed Hypervisor is not displayed when we deploy a VM in the VPC. The hypervisor is determined by the chosen template. No UI needed. nTier Apps 2.0 : KVM Hypervisor support Key: CLOUDSTACK-750 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-750 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Brian Federle Fix For: 4.2.0 This item is sub task (2.5) of https://issues.apache.org/jira/browse/CLOUDSTACK-621 VPC KVM Hypervisor support was added by Marcus Sorensen in 4.0. Creating this issue for tracking purpose -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2771) Unable to create guest VM in basic zone: Zone is dedicated
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-2771: --- Summary: Unable to create guest VM in basic zone: Zone is dedicated Key: CLOUDSTACK-2771 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2771 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: 4.2.0, vmware setup (haven't checked if this issue is seen in non-vmware cloudstack deployments). Reporter: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 1) Create a basic zone in cloudstack using the zone wizard, with hypervisor type set to vmware. Select DefaultSharedNetworkOffering as the network offering. 2) Attempt to create a guest VM using the instance wizard. The operation fails with the following exception seen in the logs: WARN [apache.cloudstack.alerts] (Job-Executor-9:job-9) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated. at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
Sheng Yang created CLOUDSTACK-2772: -- Summary: Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed Key: CLOUDSTACK-2772 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.0.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.1.0, 4.2.0, 4.0.2 When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670699#comment-13670699
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2730:
-
Hi Sadhu,
I however also see in the api.log :
2013-05-30 06:25:04,535 INFO [cloud.api.ApiServer]
(1098573588@qtp-414027396-3:null) (userId=2 accountId=2
sessionId=1w0iv5bem478ngltlv2re3c2q) 10.217.252.54 -- GET
command=createZonenetworktype=Basicname=bzone1dns1=8.8.8.8internaldns1=10.223.110.254domainid=c24461de-c929-11e2-bd29-000c29db3315response=jsonsessionkey=ig%2BOPPVzg%2Fq5kmvsnRyvASKKhsE%3D_=1369943269624
200 { createzoneresponse : { zone :
{id:e75121e3-7a3f-4106-a47f-da3917a8b262,name:bzone1,dns1:8.8.8.8,internaldns1:10.223.110.254,networktype:Basic,securitygroupsenabled:true,allocationstate:Disabled,zonetoken:f419ad99-3d70-3442-904e-b9ffd92e9185,dhcpprovider:VirtualRouter,localstorageenabled:false}
} }
So looks like the GUI is sending the securitygroupsenabled flag as true -
someone from the GUI team will need to take a look at this and fix the way the
createzone API is being issued from the cloudstack GUI.
BTW I've logged https://issues.apache.org/jira/browse/CLOUDSTACK-2771 to track
the VM creation failure issue.
Regards,
Vijay
vmware:addcluster failed in basiczone
-
Key: CLOUDSTACK-2730
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Venkata Siva Vijayendra Bhamidipati
Attachments: management-server.log
In case of vmware ,when i try to configure basic zone with shared
network.addcluster failed with
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone even though
i select the bassic and shared network.
1.select the zone type as basic
2.select the network type as shared
3.provide pod ,guest details and configure primary and secondary detaisl
4.click on finish to create basic zone with shared network mode
Actual result:
even though i select shared network in basic zone,it sends security group
enble to true internally. due to this addcluster failed .
It throws following error:
Creating cluster Something went wrong; please correct the following:Don't
support hypervisor type VMware in advanced security enabled zone
mysql select * from data_center where id=2\G;
*** 1. row ***
id: 2
name: zone1
uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
description: NULL
dns1: 10.103.128.16
dns2: NULL
internal_dns1: 10.103.128.16
internal_dns2: NULL
gateway: NULL
netmask: NULL
router_mac_address: 02:00:00:00:00:01
mac_address: 23
guest_network_cidr: NULL
domain: NULL
domain_id: NULL
networktype: Basic
dns_provider: VirtualRouter
gateway_provider: NULL
firewall_provider: NULL
dhcp_provider: VirtualRouter
lb_provider: ElasticLoadBalancerVm
vpn_provider: NULL
userdata_provider: VirtualRouter
allocation_state: Disabled
zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
is_security_group_enabled: 1
is_local_storage_enabled: 0
removed: NULL
owner: NULL
created: NULL
lastUpdated: NULL
engine_state: Disabled
ip6_dns1: NULL
ip6_dns2: NULL
1 row in set (0.00 sec)
mysql select * from networks where id=209\G;
*** 1. row ***
id: 209
name: defaultGuestNetwork
uuid: eca88272-2ad4-47a8-ab90-442393b6d034
display_text: defaultGuestNetwork
traffic_type: Guest
broadcast_domain_type: Native
broadcast_uri: vlan://untagged
gateway: NULL
cidr: NULL
mode: Dhcp
network_offering_id: 7
physical_network_id: 201
data_center_id: 2
guru_name: DirectPodBasedNetworkGuru
state: Setup
related: 209
domain_id: 1
account_id: 1
dns1: NULL
dns2: NULL
guru_data: NULL
set_fields: 0
[jira] [Updated] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang updated CLOUDSTACK-2772: --- Description: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. was: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed --- Key: CLOUDSTACK-2772 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.0.2, 4.1.0, 4.2.0 When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang updated CLOUDSTACK-2772: --- Description: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in MASTER router's root directory. BACKUP router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. was: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed --- Key: CLOUDSTACK-2772 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.0.2, 4.1.0, 4.2.0 When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in MASTER router's root directory. BACKUP router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670719#comment-13670719 ] ASF subversion and git services commented on CLOUDSTACK-2772: - Commit 70ca581499b00db2199f8d9b30fb72eef53f8b2d in branch refs/heads/master from Sheng Yang sheng.y...@citrix.com [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=70ca581 ] CLOUDSTACK-2772: Programming firewall rules to VR when recovering redundant network Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed --- Key: CLOUDSTACK-2772 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.0.2, 4.1.0, 4.2.0 When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in MASTER router's root directory. BACKUP router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang resolved CLOUDSTACK-2772. Resolution: Fixed Fix Version/s: (was: 4.0.2) (was: 4.1.0) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed --- Key: CLOUDSTACK-2772 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.2.0 When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in MASTER router's root directory. BACKUP router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2770) UI to add Baremetal DHCP server, Baremetal PXE server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670746#comment-13670746 ] ASF subversion and git services commented on CLOUDSTACK-2770: - Commit 0a01f25ffa21596f4116b1852a77a459e1db9092 in branch refs/heads/ui-baremetalDhcp-baremetalPxe from Jessica Wang jessicaw...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a01f25 ] CLOUDSTACK-2770: UI - Infrastructure menu - physical netework - network service providers - add Baremetal DHCP, Baremetal PXE. UI to add Baremetal DHCP server, Baremetal PXE server - Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang http://support.citrix.com/article/CTX135163 Cannot Add PXE/DHCP Server to Setup BareMetal Provisioning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2770) UI to add Baremetal DHCP server, Baremetal PXE server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670781#comment-13670781 ] ASF subversion and git services commented on CLOUDSTACK-2770: - Commit 1076582147b987351c98ce199f29f8c6e2c9f007 in branch refs/heads/ui-baremetalDhcp-baremetalPxe from Jessica Wang jessicaw...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1076582 ] CLOUDSTACK-2770: UI - Infrastructure menu - physical netework - network service providers - Baremetal PXE - Add Baremetal PXE Device dialog - add Tftp Root Diectory field. UI to add Baremetal DHCP server, Baremetal PXE server - Key: CLOUDSTACK-2770 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2770 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang http://support.citrix.com/article/CTX135163 Cannot Add PXE/DHCP Server to Setup BareMetal Provisioning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2771) Unable to create guest VM in basic zone: Zone is dedicated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670789#comment-13670789 ] ASF subversion and git services commented on CLOUDSTACK-2771: - Commit 7296cca9ac1121b962739a474f9d9ce0bd162fb6 in branch refs/heads/master from Prachi Damle pra...@cloud.com [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7296cca ] CLOUDSTACK-2771: Unable to create guest VM in basic zone: Zone is dedicated Changes: - Check the domain of the dedicated zone Unable to create guest VM in basic zone: Zone is dedicated -- Key: CLOUDSTACK-2771 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2771 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: 4.2.0, vmware setup (haven't checked if this issue is seen in non-vmware cloudstack deployments). Reporter: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 1) Create a basic zone in cloudstack using the zone wizard, with hypervisor type set to vmware. Select DefaultSharedNetworkOffering as the network offering. 2) Attempt to create a guest VM using the instance wizard. The operation fails with the following exception seen in the logs: WARN [apache.cloudstack.alerts] (Job-Executor-9:job-9) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated. at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2773) UI - dialog - if field B depends on dropdown field A, and dropdown field A doesn't have any option, dialog will fail to po up
Jessica Wang created CLOUDSTACK-2773: Summary: UI - dialog - if field B depends on dropdown field A, and dropdown field A doesn't have any option, dialog will fail to po up Key: CLOUDSTACK-2773 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2773 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jessica Wang e.g. Where there is no zone, go to Network menu Guest Networks section click Add Isolated Guest Network dialog = dialog fails to pop up. Because NetworkOffering dropdown depends on Zone dropdown, and Zone dropdown doesn't have any option, dialog.js fails to handle this scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2771) Unable to create guest VM in basic zone: Zone is dedicated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle reassigned CLOUDSTACK-2771: Assignee: Prachi Damle Unable to create guest VM in basic zone: Zone is dedicated -- Key: CLOUDSTACK-2771 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2771 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: 4.2.0, vmware setup (haven't checked if this issue is seen in non-vmware cloudstack deployments). Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Prachi Damle Fix For: 4.2.0 1) Create a basic zone in cloudstack using the zone wizard, with hypervisor type set to vmware. Select DefaultSharedNetworkOffering as the network offering. 2) Attempt to create a guest VM using the instance wizard. The operation fails with the following exception seen in the logs: WARN [apache.cloudstack.alerts] (Job-Executor-9:job-9) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated. at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2774) MS: Upon changing account membership of a VM snapshots are not marked as removed
Parth Jagirdar created CLOUDSTACK-2774: -- Summary: MS: Upon changing account membership of a VM snapshots are not marked as removed Key: CLOUDSTACK-2774 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2774 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Change account membership. If a VM with snapshot is moved across domains then snapshot associated with that VM are not removed from DB. This behavior is not in sync with FS. Create a VM in domain1 under account d1. Create a snapshot for this VM. Move this VM to domian2 with account d2 as admin. Observe the snapshot is not listed in d2 UI view. Observe snapshot is still there under DB. Observe that upon moving VM back to d1 the snapshot gets listed on UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2771) Unable to create guest VM in basic zone: Zone is dedicated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-2771. -- Resolution: Fixed Unable to create guest VM in basic zone: Zone is dedicated -- Key: CLOUDSTACK-2771 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2771 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: 4.2.0, vmware setup (haven't checked if this issue is seen in non-vmware cloudstack deployments). Reporter: Venkata Siva Vijayendra Bhamidipati Assignee: Prachi Damle Fix For: 4.2.0 1) Create a basic zone in cloudstack using the zone wizard, with hypervisor type set to vmware. Select DefaultSharedNetworkOffering as the network offering. 2) Attempt to create a guest VM using the instance wizard. The operation fails with the following exception seen in the logs: WARN [apache.cloudstack.alerts] (Job-Executor-9:job-9) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 5, on Host with Id: null ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-9) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM. Zone bzone1 is dedicated. at com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:454) at com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:213) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3268) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2807) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2793) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1084) vpc static one to one nat failure
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-1084.
---
Resolution: Duplicate
Duplicate of https://issues.apache.org/jira/browse/CLOUDSTACK-2761
vpc static one to one nat failure
-
Key: CLOUDSTACK-1084
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1084
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: VMware
Affects Versions: 4.0.0
Reporter: brandon arms
Priority: Blocker
static nat rule fails for vpc:
acquire ip address log:
2013-01-29 14:34:05,584 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-13:null) Associate IP address called by the user 6 account 6
2013-01-29 14:34:05,585 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-13:null) Associate IP address lock acquired
2013-01-29 14:34:05,589 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-13:null) Got 8.25.163.133 to assign for account 6 in zone 3
2013-01-29 14:34:05,602 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-13:null) Releasing lock account Acct[6-barms]
2013-01-29 14:34:05,603 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-13:null) Associate IP address lock released
2013-01-29 14:34:05,615 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-13:null) submit async job-353, details: AsyncJobVO {id:353,
userId: 6, accountId: 6, sessionKey: null, instanceType: IpAddress,
instanceId: 17, cmd: com.cloud.api.commands.AssociateIPAddrCmd,
cmdOriginator: null, cmdInfo:
{id:17,response:json,sessionkey:c5ysvZL+Nxs2EwFefOsNuWL6/NY\u003d,ctxUserId:6,_:1359488045538,ctxAccountId:6,vpcid:1606e883-6750-42be-b42b-663cb56dba46,ctxStartEventId:1519},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 143316583244,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-01-29 14:34:05,618 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-12:job-353) Executing com.cloud.api.commands.AssociateIPAddrCmd
for job-353
2013-01-29 14:34:05,628 DEBUG [network.vpc.VpcManagerImpl]
(Job-Executor-12:job-353) Associating ip Ip[8.25.163.133-3] to vpc [VPC
[8-Tenant1-VPC]
2013-01-29 14:34:05,638 DEBUG [network.vpc.VpcManagerImpl]
(Job-Executor-12:job-353) Successfully assigned ip Ip[8.25.163.133-3] to vpc
[VPC [8-Tenant1-VPC]
2013-01-29 14:34:05,644 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-12:job-353) Complete async job-353, jobStatus: 1, resultCode:
0, result: com.cloud.api.response.IPAddressResponse@3e8d1fbf
2013-01-29 14:34:05,649 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-12:job-353) Done executing
com.cloud.api.commands.AssociateIPAddrCmd for job-353
2013-01-29 14:34:10,653 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-23:null) Async job-353 completed
enable static nat (failure):
2013-01-29 14:36:13,741 DEBUG [network.rules.RulesManagerImpl]
(catalina-exec-3:null) The ip is not associated with the VPC network id=238,
so assigning
2013-01-29 14:36:13,745 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-3:null) Associating ip Ip[8.25.163.133-3] to network
Ntwk[238|Guest|12]
2013-01-29 14:36:13,752 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-3:null) Successfully associated ip address 8.25.163.133 to
network Ntwk[238|Guest|12]
2013-01-29 14:36:13,770 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl] (catalina-exec-3:null)
Applying vpc ip association in network Ntwk[238|Guest|12]
2013-01-29 14:36:13,786 DEBUG [agent.transport.Request]
(catalina-exec-3:null) Seq 10-328139827: Sending { Cmd , MgmtId:
143316583244, via: 10, Ver: v1, Flags: 11,
[{routing.IpAssocVpcCommand:{ipAddresses:[{accountId:6,publicIp:8.25.163.133,sourceNat:false,add:true,oneToOneNat:true,firstIP:false,vlanId:500,vlanGateway:8.25.163.129,vlanNetmask:255.255.255.240,vifMacAddress:06:4b:ce:00:00:1c,networkRate:200,trafficType:Public,networkName:vSwitch1}],accessDetails:{router.guest.ip:8.25.163.131,zone.network.type:Advanced,router.ip:172.31.200.166,router.name:r-64-VM},wait:0}}]
}
2013-01-29 14:36:13,786 DEBUG [agent.transport.Request]
(catalina-exec-3:null) Seq 10-328139827: Executing: { Cmd , MgmtId:
143316583244, via: 10, Ver: v1, Flags: 11,
[jira] [Closed] (CLOUDSTACK-2774) MS: Upon changing account membership of a VM snapshots are not marked as removed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar closed CLOUDSTACK-2774. -- Resolution: Invalid Not a Valid bug. MS: Upon changing account membership of a VM snapshots are not marked as removed Key: CLOUDSTACK-2774 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2774 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Change account membership. If a VM with snapshot is moved across domains then snapshot associated with that VM are not removed from DB. This behavior is not in sync with FS. Create a VM in domain1 under account d1. Create a snapshot for this VM. Move this VM to domian2 with account d2 as admin. Observe the snapshot is not listed in d2 UI view. Observe snapshot is still there under DB. Observe that upon moving VM back to d1 the snapshot gets listed on UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1327) Cloudstack allows users to import huge templates from unauthorised URLs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670863#comment-13670863 ] Alena Prokharchyk commented on CLOUDSTACK-1327: --- The max template size that can be downloaded by the regular user, is limited via max.template.iso.size global config parameter (The maximum size for a downloaded template or ISO (in GB)). Default value is 50GB. Cloudstack allows users to import huge templates from unauthorised URLs --- Key: CLOUDSTACK-1327 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1327 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Template Affects Versions: 4.0.1 Environment: Centos 6 x86_64 kvm hypervisors Reporter: Nux Priority: Critical Because Cloudstack deploys instances as r/w snapshots of the template, importing a template with, say 1 TB diskspace will give you 1 TB instances... this will lead to service abuse. Currently Cloudstack allows regular users to install templates from not allowed URLs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2720) Unable to assign template to specific user.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-2720. --- Resolution: Fixed Marking the problem as fixed as its possible to change the template permissions using updateTemplatePermissions API. Unable to assign template to specific user. --- Key: CLOUDSTACK-2720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2720 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Environment: KVM Reporter: Dean Kamali Labels: template Not sure why I can't as an admin, to assign a template to a user? example: after a user uploads his template to our ftp server, I am as an admin, unable to assign that template to a user, unless I log in with his account and upload it. using the admin account, I'm only able to make templates public / featured, but I not make it available to specific user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2720) Unable to assign template to specific user.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670896#comment-13670896 ] Alena Prokharchyk commented on CLOUDSTACK-2720: --- Dean, admin can grant permissions to use the template, to the regular user. Check this API: http://cloudstack.apache.org/docs/api/apidocs-4.0.0/root_admin/updateTemplatePermissions.html This command was never supported in the cloudStack UI though. Unable to assign template to specific user. --- Key: CLOUDSTACK-2720 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2720 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Environment: KVM Reporter: Dean Kamali Labels: template Not sure why I can't as an admin, to assign a template to a user? example: after a user uploads his template to our ftp server, I am as an admin, unable to assign that template to a user, unless I log in with his account and upload it. using the admin account, I'm only able to make templates public / featured, but I not make it available to specific user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2775) PVLAN - Ubuntu 13.04 KVM openvswitch - VM cannot reach DHCP server, outside world
angeline shen created CLOUDSTACK-2775: - Summary: PVLAN - Ubuntu 13.04 KVM openvswitch - VM cannot reach DHCP server, outside world Key: CLOUDSTACK-2775 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2775 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: MS ubuntu 13.04 KVM ACS 4.2 PVLAN build 417 host ubuntu 13.04 KVM ACS 4.2 PVLAN build 22 Reporter: angeline shen Assignee: Sheng Yang Priority: Critical Fix For: 4.2.0 1. advance zone. Add 2 hosts. Create PVLAN networks. 2. VMs deployed on 1 host cannot reach DHCP server outside wide. VMs deployed on other host able to reach DHCP server outside wide. Per Sheng's analysis : root@ubuntu8161:~# ovs-ofctl show cloudbr0 OFPT_FEATURES_REPLY (xid=0x1): dpid:bc305bd415d2 n_tables:255, n_buffers:256 capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE 10(em1): addr:bc:30:5b:d4:15:d2 config: 0 state: 0 current:1GB-FD COPPER AUTO_NEG advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD AUTO_NEG supported: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG speed: 1000 Mbps now, 1000 Mbps max 288(vnet1): addr:fe:58:38:00:00:03 config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 100 Mbps max 289(vnet2): addr:fe:fd:e6:00:00:08 config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 100 Mbps max 290(vnet3): addr:fe:0d:68:00:00:04 config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 100 Mbps max 291(vnet4): addr:fe:ca:c6:00:00:0e config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 100 Mbps max 292(vnet6): addr:fe:3f:3a:00:00:0d config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 100 Mbps max 293(vnet7): addr:fe:41:98:00:00:10 config: 0 state: 0 current:10MB-FD COPPER speed: 10 Mbps now, 100 Mbps max LOCAL(cloudbr0): addr:bc:30:5b:d4:15:d2 config: 0 state: 0 speed: 100 Mbps now, 100 Mbps max OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2687) NPE with deploy VM when there are no resources available
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670911#comment-13670911 ] Alena Prokharchyk commented on CLOUDSTACK-2687: --- Plus can you attach management server log file. NPE with deploy VM when there are no resources available - Key: CLOUDSTACK-2687 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2687 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Sailaja Mada Fix For: 4.2.0 Setup : Advanced Zone Steps : 1. Try to deploy VM when there are resources unavailable ( Host does not enough resources Or host is in alert state ) Observation : 2013-05-27 11:24:18,951 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-57:job-101) Destroying vm VM[User|c8a3fb3f-e264-4b09-b6b6-1e2b07a20df1] as it failed to create on Host with Id:null 2013-05-27 11:24:18,966 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-101) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null 2013-05-27 11:24:18,974 WARN [apache.cloudstack.alerts] (Job-Executor-57:job-101) alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: Failed to deploy Vm with Id: 11, on Host with Id: null 2013-05-27 11:24:19,322 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-57:job-101) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd java.lang.NullPointerException at com.cloud.vm.UserVmManagerImpl.finalizeStop(UserVmManagerImpl.java:3041) at com.cloud.vm.VirtualMachineManagerImpl.sendStop(VirtualMachineManagerImpl.java:978) at com.cloud.vm.VirtualMachineManagerImpl.cleanup(VirtualMachineManagerImpl.java:1005) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:932) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:547) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3185) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2726) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2712) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:419) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-05-27 11:24:19,323 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-57:job-101) Complete async job-101, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null 2013-05-27 11:24:20,498 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) ===START=== 10.144.6.19 -- GET command=queryAsyncJobResultjobId=74563444-5481-4145-a0ab-f80e1db4response=jsonsessionkey=6Y8QsASlVJM2%2F%2BzSeYZnDac1lD8%3D_=1369634220149 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2776) UI Implicit dedication planner: createServiceOffering UI should be changed to take in key-value details
Prachi Damle created CLOUDSTACK-2776: Summary: UI Implicit dedication planner: createServiceOffering UI should be changed to take in key-value details Key: CLOUDSTACK-2776 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2776 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Prachi Damle Priority: Critical Fix For: 4.2.0 The UI changes done to the createServiceOffering page as part of the Implicit dedication planner are not correct and very specific to this feature. Instead we need a generic design. We should make following changes: 1) Create Service Offering Page should show option ‘Add Details’ and then take in 2 text boxes titled ‘key’ and ‘value’ - This is same as the UI for adding Tags to a resource like network 2) After adding one pair, UI can show the option to add another key-value detail 3) UI can then send all the key-value pairs in a Map while calling CreateServiceOffering API -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2777) AWSAPI: build and packaging issue causing EC2 SOAP test failures
Prachi Damle created CLOUDSTACK-2777: Summary: AWSAPI: build and packaging issue causing EC2 SOAP test failures Key: CLOUDSTACK-2777 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2777 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Packaging Reporter: Prachi Damle Fix For: 4.2.0 awsapi webapp is not getting deployed on axis2 when management server is started. Following file is missing and causing this issue: webapps7080/awsapi/WEB-INF/services/cloud-ec2.aar I don’t see this file on a setup using rpm packages under: /usr/share/cloudstack-bridge/webapps/awsapi/WEB-INF/services. So looks like the .aar file is not being generated by the apache build. Apache build should create this jar file [cloud-ec2.aar] too and package it under webapps7080/awsapi/WEB-INF/services -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
