[jira] [Created] (CLOUDSTACK-2836) [UI][Dedicated Resources : Guest Vlans per tenant] The new UI limits the feature
Abhinav Roy created CLOUDSTACK-2836: --- Summary: [UI][Dedicated Resources : Guest Vlans per tenant] The new UI limits the feature Key: CLOUDSTACK-2836 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2836 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.0.2, 4.2.0 Reporter: Abhinav Roy Assignee: Jessica Wang Priority: Critical Fix For: 4.2.0 The new UI which has a drop down for dedicating guest vlans has the following limitations : --- 1. Even after a range is dedicated to some account, it is shown in the drop down menu. 2. The feature enables us to dedicate a sub-range of the vlan range also but this UI limits that feature , Ex- If there is a vlan range V1 - V10 available then the admin is allowed to dedicate V1 - V5 or V6 - V8 also to any account but the UI limits this feature. We can only dedicate the full range with this UI 3. If there is a vlan range available like V1 - V5 and then admin adds a range V6 - V9 then the new UI will allow us only to dedicate V1 - V9 and we can't dedicate the sub ranges. 4. When we add a new range then it is not immediately listed in the dropdown menu, for that to be shown we need to refresh the browser page and then go all the way to that location and then start dedicating. NOTE : All these issues were not there in the previous UI where the admin had to manually enter the range and then dedicate, so can we please revert to the previous UI and avoid all these issues? -- 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-2836) [UI][Dedicated Resources : Guest Vlans per tenant] The new UI limits the feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-2836: Affects Version/s: (was: 4.0.2) > [UI][Dedicated Resources : Guest Vlans per tenant] The new UI limits the > feature > > > Key: CLOUDSTACK-2836 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2836 > 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: Abhinav Roy >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > The new UI which has a drop down for dedicating guest vlans has the following > limitations : > --- > 1. Even after a range is dedicated to some account, it is shown in the drop > down menu. > 2. The feature enables us to dedicate a sub-range of the vlan range also but > this UI limits that feature , > Ex- If there is a vlan range V1 - V10 available then the admin is allowed to > dedicate V1 - V5 or V6 - V8 also to any account but the UI limits this > feature. We can only dedicate the full range with this UI > 3. If there is a vlan range available like V1 - V5 and then admin adds a > range V6 - V9 then the new UI will allow us only to dedicate V1 - V9 and we > can't dedicate the sub ranges. > 4. When we add a new range then it is not immediately listed in the dropdown > menu, for that to be shown we need to refresh the browser page and then go > all the way to that location and then start dedicating. > NOTE : All these issues were not there in the previous UI where the admin had > to manually enter the range and then dedicate, so can we please revert to the > previous UI and avoid all these issues? -- 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-2835) VR Deployement from admin registered tamplate is failing because registered template type is user.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2835: -- Attachment: Logs.rar Logs and DB dump > VR Deployement from admin registered tamplate is failing because registered > template type is user. > --- > > Key: CLOUDSTACK-2835 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2835 > 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: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: Logs.rar > > > Step to reproduce > -- > -- > 1-Set Global parameter "router.template.xen" to some string say "newtmpl" . > 2-Register a system vm template with name "newtmpl" > 3-Deploy a vm with new network > Expected > --- > New router vm should come with newly registered template > Actual > > Router vm is not coming up with error "2013-06-04 07:39:20,431 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > XenServer won't support system vm, skip it" > Logs > > > 2013-06-04 07:39:20,328 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) lock account 2 is acquired > 2013-06-04 07:39:20,362 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing lock account 2 > 2013-06-04 07:39:20,368 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Asking VirtualRouter to implemenet Ntwk[204|Guest|8] > 2013-06-04 07:39:20,373 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Lock is acquired for network id 204 as a part of router startup in > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))] > 2013-06-04 07:39:20,396 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Adding nic for Virtual Router in Guest network Ntwk[204|Guest|8] > 2013-06-04 07:39:20,397 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Adding nic for Virtual Router in Control network > 2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Found existing network configuration for offering > [Network Offering [3-Control-System-Control-Network]: Ntwk[202|Control|3] > 2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing lock for Acct[1-system] > 2013-06-04 07:39:20,402 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Adding nic for Virtual Router in Public network > 2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Found existing network configuration for offering > [Network Offering [1-Public-System-Public-Network]: Ntwk[200|Public|1] > 2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing lock for Acct[1-system] > 2013-06-04 07:39:20,418 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Creating the router 4 in datacenter > com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$9e67d269@1 > 2013-06-04 07:39:20,418 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Allocating the domR with the hypervisor type XenServer > 2013-06-04 07:39:20,431 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > XenServer won't support system vm, skip it > 2013-06-04 07:39:20,433 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Lock is released for network id 204 as a part of router startup in > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))] > 2013-06-04 07:39:20,437 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Cleaning up because we're unable to implement the > network Ntwk[204|Guest|8] > 2013-06-04 07:39:20,465 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing 0 port forwarding rules for network id=204 > as a part of shutdownNetworkRules > 2013-06-04 07:39:20,465 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-1:job-13) There are no rules to forward to the network elements > 2013-06-04 07:39:20,467 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing 0 static nat rules for network id=204 as a > part of shutdo
[jira] [Created] (CLOUDSTACK-2835) VR Deployement from admin registered tamplate is failing because registered template type is user.
prashant kumar mishra created CLOUDSTACK-2835: - Summary: VR Deployement from admin registered tamplate is failing because registered template type is user. Key: CLOUDSTACK-2835 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2835 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: prashant kumar mishra Fix For: 4.2.0 Step to reproduce -- -- 1-Set Global parameter "router.template.xen" to some string say "newtmpl" . 2-Register a system vm template with name "newtmpl" 3-Deploy a vm with new network Expected --- New router vm should come with newly registered template Actual Router vm is not coming up with error "2013-06-04 07:39:20,431 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) XenServer won't support system vm, skip it" Logs 2013-06-04 07:39:20,328 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) lock account 2 is acquired 2013-06-04 07:39:20,362 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing lock account 2 2013-06-04 07:39:20,368 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Asking VirtualRouter to implemenet Ntwk[204|Guest|8] 2013-06-04 07:39:20,373 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Lock is acquired for network id 204 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))] 2013-06-04 07:39:20,396 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Adding nic for Virtual Router in Guest network Ntwk[204|Guest|8] 2013-06-04 07:39:20,397 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Adding nic for Virtual Router in Control network 2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Found existing network configuration for offering [Network Offering [3-Control-System-Control-Network]: Ntwk[202|Control|3] 2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing lock for Acct[1-system] 2013-06-04 07:39:20,402 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Adding nic for Virtual Router in Public network 2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Found existing network configuration for offering [Network Offering [1-Public-System-Public-Network]: Ntwk[200|Public|1] 2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing lock for Acct[1-system] 2013-06-04 07:39:20,418 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Creating the router 4 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$9e67d269@1 2013-06-04 07:39:20,418 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Allocating the domR with the hypervisor type XenServer 2013-06-04 07:39:20,431 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) XenServer won't support system vm, skip it 2013-06-04 07:39:20,433 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Lock is released for network id 204 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))] 2013-06-04 07:39:20,437 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Cleaning up because we're unable to implement the network Ntwk[204|Guest|8] 2013-06-04 07:39:20,465 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing 0 port forwarding rules for network id=204 as a part of shutdownNetworkRules 2013-06-04 07:39:20,465 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-1:job-13) There are no rules to forward to the network elements 2013-06-04 07:39:20,467 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing 0 static nat rules for network id=204 as a part of shutdownNetworkRules 2013-06-04 07:39:20,467 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-1:job-13) There are no rules to forward to the network elements 2013-06-04 07:39:20,473 DEBUG [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-1:job-13) Revoking 0 Public load balancing rules for network id=204 2013-06-04 07:39:20,473 DEBUG [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-1:job-13) There are no Load Balancing Rules to forward to t
[jira] [Commented] (CLOUDSTACK-1194) Bug with the web interface (re isolation method)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674114#comment-13674114 ] Pranav Saxena commented on CLOUDSTACK-1194: --- I am still not able to reproduce it on master . It works fine for me!! > Bug with the web interface (re isolation method) > > > Key: CLOUDSTACK-1194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, UI >Affects Versions: 4.0.1 > Environment: Centos 6 x86_64 >Reporter: Nux >Assignee: Hiroaki Kawai > Attachments: isolation_method.png, isolation.png > > > By total chance I was using Chrome (24.0) today instead of Firefox (stock > EL6, 10.0.12 ESR) and when creating a new zone on Chrome it offers me "VLAN, > GRE or STT" whereas this dropdown menu is not visible in Firefox at all. See > the images: > Firefox: http://img.nux.ro/9Nx-Selection_071.png > Chrome: http://img.nux.ro/P3b-Selection_070.png -- 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-1194) Bug with the web interface (re isolation method)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranav Saxena updated CLOUDSTACK-1194: -- Attachment: isolation.png > Bug with the web interface (re isolation method) > > > Key: CLOUDSTACK-1194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, UI >Affects Versions: 4.0.1 > Environment: Centos 6 x86_64 >Reporter: Nux >Assignee: Hiroaki Kawai > Attachments: isolation_method.png, isolation.png > > > By total chance I was using Chrome (24.0) today instead of Firefox (stock > EL6, 10.0.12 ESR) and when creating a new zone on Chrome it offers me "VLAN, > GRE or STT" whereas this dropdown menu is not visible in Firefox at all. See > the images: > Firefox: http://img.nux.ro/9Nx-Selection_071.png > Chrome: http://img.nux.ro/P3b-Selection_070.png -- 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-901) QA enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-901. --- > QA enable storage xenmotion support in XenServer 6.1 feature > > > Key: CLOUDSTACK-901 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-901 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Reporter: Chip Childers >Assignee: Srikanteswararao Talluri > 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] [Resolved] (CLOUDSTACK-901) QA enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-901. - Resolution: Fixed testing is completed > QA enable storage xenmotion support in XenServer 6.1 feature > > > Key: CLOUDSTACK-901 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-901 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Reporter: Chip Childers >Assignee: Srikanteswararao Talluri > 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-2834) Network ACL list should not accept duplicate ACL rules.
manasaveloori created CLOUDSTACK-2834: - Summary: Network ACL list should not accept duplicate ACL rules. Key: CLOUDSTACK-2834 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2834 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 Reporter: manasaveloori Priority: Minor Fix For: 4.2.0 Steps: 1. Have a CS with advanced zone. 2. Create a VPC. 3. Create a network ACL list. 4. Add same ACL rule multiple times. Expected behavior. The ACL list should check for duplicate entries into the list before adding. -- 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-847) [DOC] Document the ability to use multiple IP ranges
[ https://issues.apache.org/jira/browse/CLOUDSTACK-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674102#comment-13674102 ] ASF subversion and git services commented on CLOUDSTACK-847: Commit 13eaa9a5b82037c84ceefa448e3fc7e69b2becf3 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=13eaa9a ] CLOUDSTACK-847 > [DOC] Document the ability to use multiple IP ranges > > > Key: CLOUDSTACK-847 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-847 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley >Assignee: Radhika Nair > Fix For: 4.2.0 > > > Document the ability to make use of multiple IP ranges. -- 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-2737) [SXM] findHostsForMigration is resulting in an exception when there are no suitable tagged storage pools
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-2737: - Assignee: Devdeep Singh > [SXM] findHostsForMigration is resulting in an exception when there are no > suitable tagged storage pools > > > Key: CLOUDSTACK-2737 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2737 > 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: Srikanteswararao Talluri >Assignee: Devdeep Singh >Priority: Blocker > Fix For: 4.2.0 > > > Steps to reproduce: > 1. Create a disk offering and Compute offering with storage tags "test" > 2. deploy a VM using the above created Disk and Compute offering. > 3. Now, issue findHostsForMigration API for this VM > http://10.147.38.166:8080/client/api?command=findHostsForMigration&VirtualMachineId=98cd65b6-aaf5-46fc-b5ce-427531ac8f6f&response=json&sessionkey=FWGf3HaYW6HPFgfkkmGQhxDUNUI%3D&_=1369828635745 > 013-05-29 22:51:49,821 ERROR [cloud.api.ApiServer] (catalina-exec-9:null) > unhandled exception executing api command: findHostsForMigration > java.util.ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:782) > at java.util.ArrayList$Itr.next(ArrayList.java:754) > at > com.cloud.server.ManagementServerImpl.listHostsForMigrationOfVM(ManagementServerImpl.java:1219) > at > org.apache.cloudstack.api.command.admin.host.FindHostsForMigrationCmd.execute(FindHostsForMigrationCmd.java:76) > 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:2274) > 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-29 22:51:49,825 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) > ===END=== 10.252.241.180 -- GET > command=findHostsForMigration&VirtualMachineId=98cd65b6-aaf5-46fc-b5ce-427531ac8f6f&response=json&sessionkey=FWGf3HaYW6HPFgfkkmGQhxDUNUI%3D&_=1369828540362 -- 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-2014) LDAP user provisioning
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Duffy reassigned CLOUDSTACK-2014: - Assignee: Ian Duffy > LDAP user provisioning > -- > > Key: CLOUDSTACK-2014 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2014 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Abhinandan Prateek >Assignee: Ian Duffy > Labels: gsoc2013 > Fix For: Future > > > Need to automate the way the LDAP users are provisioned into cloud stack. > This will mean better integration with a LDAP server, ability to import users > and a way to define how the LDAP user maps to the cloudstack users. > Expertise: Java, JNDI and ldap -- 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-2828) Enable LRTM load balancing type for netscaler
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-2828: --- Priority: Major (was: Minor) > Enable LRTM load balancing type for netscaler > - > > Key: CLOUDSTACK-2828 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2828 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Nick Wales > > We use LRTM extensively on our non cloudstack managed netscaler devices. > Would love to see it implemented in an upcoming release. -- 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-2648) [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises created on VR in case of multiple subnets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2648. -- Resolution: Fixed > [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises > created on VR in case of multiple subnets > --- > > Key: CLOUDSTACK-2648 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2648 > 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 on master: > CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz >Reporter: Sanjeev N >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.rar, SMlog > > > Reboot or start/stop router vm deletes the ip alises created on VR in case of > multiple subnets > Steps to Reproduce: > = > 1.Bring up CS in basic zone with xenserver6.1 > 2.Exhaust all the guest IP addresses in primary ip range by deploying guest > vms > 3.Add new guest IP range in new subnet > 4.Deploy guest vms using the ip addresses from the new range > 5.Reboot or stop/start VR > Observations: > > After step4 ip alias gets created on VR with IP address from the new subnet. > After reboot or stop/start of the VR ip alias is getting removed from the VR. > Verified the SMlog and found the following command getting executed with the > VR is rebooted related to ip alias: > [22250] 2013-05-23 11:13:30.654474 VMOPS enter deleteipAlias > [22250] 2013-05-23 11:13:30.654559 ['bin/bash', > '/opt/xensource/bin/deleteipAlias.sh', '169.254.3.21', '', > '18:10.147.43.132:255.255.255.192-21:10.147.43.195:255.255.255.192-'] > [22250] 2013-05-23 11:13:31.338199pread SUCCESS > [22250] 2013-05-23 11:13:31.338311 VMOPS exit deleteipAlias > IP aliases information is being passed to deleteipAlias.sh and due to which > ip alias are getting removed. -- 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-2620) [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address in case of multiple subnets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2620. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a69b82 > [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address > in case of multiple subnets > - > > Key: CLOUDSTACK-2620 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2620 > 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: Build from master branch: > CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz >Reporter: Sanjeev N >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > > [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address > in case of multiple subnets > Steps to Reproduce: > > 1.Bring up CS in basic zone with Xen61 server > 2.Consume all the guest IP ranges in the existing subnet > 3.Add guest ip range in new CIDR > 4.Deploy guest vm > 5.Verify the nameserver in /etc/resolve.conf in guest vm > Expected Behaviour: > = > nameserver on guest vm should be set to ip alias address on VR > Actual Behaviour: > == > nameserver on guest vm was set to zone level internal DNS ip address instead > of VR's ip alias address. > Observations: > === > Primary ip range: 10.147.43.3-10.147.43.7 GW:10.147.43.1 Netmask: > 255.255.255.128 > New IP Range : 10.147.43.130-10.147.43.133 GW: 10.147.43.129 Netmask: > 255.255.255.192 > When the vm is deployed with IP address from the new CIDR , ip alis on VR got > created with ip address from new CIDR. > ip alias on the VR was set to 10.147.43.132 > root@r-4-VM:/etc# ifconfig > eth0 Link encap:Ethernet HWaddr 06:ba:90:00:00:0e > inet addr:10.147.43.6 Bcast:10.147.43.127 Mask:255.255.255.128 > inet6 addr: fe80::4ba:90ff:fe00:e/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:36018 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1007 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1919944 (1.8 MiB) TX bytes:46214 (45.1 KiB) > Interrupt:24 > eth0:18 Link encap:Ethernet HWaddr 06:ba:90:00:00:0e > inet addr:10.147.43.132 Bcast:10.147.43.191 Mask:255.255.255.192 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:24 > During ip alias creation process dnsmasq.conf was re-generated with new ip > range and dhcp-option was set as following: > dhcp-option=6,10.103.128.16,10.103.128.16 > dnsmasq.conf regeneration process is taking DNS values set at zone level and > replacing with the exiting values in the file. Hence guest vms are getting > internal DNS ip address as nemeserver. > Impact: > == > Since guest vms nameserver is set to an IP address other than VR's , vm to vm > communication using domain names will fail. -- 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-2398) packaging does not update systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam reopened CLOUDSTACK-2398: > packaging does not update systemvm.iso > -- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.2.0 > Environment: Master branch build > KVM >Reporter: Rayees Namathponnan >Priority: Critical > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt > "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > > Good: DNS resolves download.cloud.com > > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > > Good: Java process is running > > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in > > Jenkins.cloudstack.org -- 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-2398) packaging does not update systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-2398: --- Priority: Critical (was: Blocker) > packaging does not update systemvm.iso > -- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.2.0 > Environment: Master branch build > KVM >Reporter: Rayees Namathponnan >Priority: Critical > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt > "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > > Good: DNS resolves download.cloud.com > > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > > Good: Java process is running > > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in > > Jenkins.cloudstack.org -- 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-2398) packaging does not update systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam reassigned CLOUDSTACK-2398: -- Assignee: (was: Rajesh Battala) This is a packaging issues. systemvm.iso isn't getting the latest in the packages. > packaging does not update systemvm.iso > -- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.2.0 > Environment: Master branch build > KVM >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt > "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > > Good: DNS resolves download.cloud.com > > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > > Good: Java process is running > > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in > > Jenkins.cloudstack.org -- 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-2398) packaging does not update systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-2398: --- Summary: packaging does not update systemvm.iso (was: [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with permission error ) > packaging does not update systemvm.iso > -- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.2.0 > Environment: Master branch build > KVM >Reporter: Rayees Namathponnan >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt > "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > > Good: DNS resolves download.cloud.com > > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > > Good: Java process is running > > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in > > Jenkins.cloudstack.org -- 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-2398) [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with permission error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-2398: --- Component/s: (was: Template) Packaging > [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with > permission error > -- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.2.0 > Environment: Master branch build > KVM >Reporter: Rayees Namathponnan >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt > "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > > Good: DNS resolves download.cloud.com > > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > > Good: Java process is running > > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in > > Jenkins.cloudstack.org -- 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-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-tabpanel&focusedCommentId=13674045#comment-13674045 ] Harikrishna Patnala commented on CLOUDSTACK-2728: - In RB https://reviews.apache.org/r/11618/ > 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-2820) Global parameter "network.throttling.rate" is not controlling data transfer rate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674044#comment-13674044 ] prashant kumar mishra commented on CLOUDSTACK-2820: --- This doc " http://docs.vmd.citrix.com/XenServer/4.0.1/reference/reference.html#networking_qos"; also talk about n/w throttling > Global parameter "network.throttling.rate" is not controlling data transfer > rate > > > Key: CLOUDSTACK-2820 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2820 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, XenServer >Affects Versions: 4.2.0 > Environment: Hypervisor XS 6.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar > > > Virtual router's interfaces are getting QOS based on GP > "network.throttling.rate" value but in actual there is no control on data > transfer rate. > Steps to rep > --- > 1-Set GP "network.throttling.rate" to some value say 3 Mb/s;restart MS > 2-down load a file in VR > 3-copy file from vm to some location using rsunc/scp > expected > - > Transfer rate should not be more that 3Mb/s > Actual > - > i see transfer rate 15.50 MB/sec > My observation > - > I manually set transfer rate to 100KB/s on VR interface ,saw same > issue.Looks like Xenserver issue > Details > --- > root@r-3858-VM:~# rsync -avzSP acton-systemvm-02062012.vhd.bz2 > 10.147.59.200:/root/ > The authenticity of host '10.147.59.200 (10.147.59.200)' can't be established. > RSA key fingerprint is a8:2a:cb:0f:f9:3f:41:eb:b1:b5:a6:4b:59:0c:df:39. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '10.147.59.200' (RSA) to the list of known hosts. > root@10.147.59.200's password: > sending incremental file list > acton-systemvm-02062012.vhd.bz2 >140616708 100% 15.50MB/s0:00:08 (xfer#1, to-check=0/1) > sent 140664010 bytes received 31 bytes 9075099.42 bytes/sec > total size is 140616708 speedup is 1.00 -- 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-2089) API dispatcher not able to handle multiple entities while translating UUID to internaID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-2089. - Resolution: Not A Problem This might be helpful in future but currently the API for updateConfiguration has modified from "scope and scopeid" to "zoneid, clusterid, storageid, accountid". So right now no need to change the api dispatcher. > API dispatcher not able to handle multiple entities while translating UUID to > internaID > --- > > Key: CLOUDSTACK-2089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2089 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.2.0 > > > Currently API dispatcher assumes single entity type for UUID defined on > @EntityReference of a response class even if we can able to provide list of > entity types (Class[] entityType()). > This needs to be supported in order to have some kind of generic APIs that > has ID referring multiple entities (of course one entity in one go). > For listing/updating configuration parameters (@Granular global parameters) > we provide scope (zone/cluster/pool/account) and id. This id can be of any > entity(zone/cluster/pool/account). -- 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-2089) API dispatcher not able to handle multiple entities while translating UUID to internaID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala reassigned CLOUDSTACK-2089: --- Assignee: Harikrishna Patnala > API dispatcher not able to handle multiple entities while translating UUID to > internaID > --- > > Key: CLOUDSTACK-2089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2089 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.2.0 > > > Currently API dispatcher assumes single entity type for UUID defined on > @EntityReference of a response class even if we can able to provide list of > entity types (Class[] entityType()). > This needs to be supported in order to have some kind of generic APIs that > has ID referring multiple entities (of course one entity in one go). > For listing/updating configuration parameters (@Granular global parameters) > we provide scope (zone/cluster/pool/account) and id. This id can be of any > entity(zone/cluster/pool/account). -- 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-2398) [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with permission error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674031#comment-13674031 ] Rayees Namathponnan commented on CLOUDSTACK-2398: - Tests still fails in latest master build and system template from jenkins.cloudstack.org > [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with > permission error > -- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 > Environment: Master branch build > KVM >Reporter: Rayees Namathponnan >Assignee: Rajesh Battala >Priority: Blocker > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt > "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > > Good: DNS resolves download.cloud.com > > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > > Good: Java process is running > > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in > > Jenkins.cloudstack.org -- 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-2820) Global parameter "network.throttling.rate" is not controlling data transfer rate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674030#comment-13674030 ] prashant kumar mishra commented on CLOUDSTACK-2820: --- This post "http://xmodulo.com/2012/10/how-to-rate-limit-xenserver-vms-network-interfaces.html"; talk about how to set network throttling rate on vm interface . Ofcourse , after MS restart i did VR stop/start . > Global parameter "network.throttling.rate" is not controlling data transfer > rate > > > Key: CLOUDSTACK-2820 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2820 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, XenServer >Affects Versions: 4.2.0 > Environment: Hypervisor XS 6.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar > > > Virtual router's interfaces are getting QOS based on GP > "network.throttling.rate" value but in actual there is no control on data > transfer rate. > Steps to rep > --- > 1-Set GP "network.throttling.rate" to some value say 3 Mb/s;restart MS > 2-down load a file in VR > 3-copy file from vm to some location using rsunc/scp > expected > - > Transfer rate should not be more that 3Mb/s > Actual > - > i see transfer rate 15.50 MB/sec > My observation > - > I manually set transfer rate to 100KB/s on VR interface ,saw same > issue.Looks like Xenserver issue > Details > --- > root@r-3858-VM:~# rsync -avzSP acton-systemvm-02062012.vhd.bz2 > 10.147.59.200:/root/ > The authenticity of host '10.147.59.200 (10.147.59.200)' can't be established. > RSA key fingerprint is a8:2a:cb:0f:f9:3f:41:eb:b1:b5:a6:4b:59:0c:df:39. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '10.147.59.200' (RSA) to the list of known hosts. > root@10.147.59.200's password: > sending incremental file list > acton-systemvm-02062012.vhd.bz2 >140616708 100% 15.50MB/s0:00:08 (xfer#1, to-check=0/1) > sent 140664010 bytes received 31 bytes 9075099.42 bytes/sec > total size is 140616708 speedup is 1.00 -- 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-2786) System VM on vmware setup is not coming up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674018#comment-13674018 ] Abhinandan Prateek commented on CLOUDSTACK-2786: Shwetha, Can you specify the details of the template you are using ? > System VM on vmware setup is not coming up > -- > > Key: CLOUDSTACK-2786 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2786 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware >Affects Versions: 4.2.0 > Environment: build: > CloudStack-non-OSS-MASTER-426-rhel6.3.tar.gz > ESXI5.1 host > NFS Storage >Reporter: shweta agarwal >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log > > > Repro steps: > 1. Create a VMware zone > 2. Enable it > Bug: > I am hitting exception > 2013-05-31 10:59:13,178 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-1:10.147.40.27) Template routing-8 is not setup yet, setup > template from secondary storage with uuid name: > d5beee04cb3e3a8593e41cb574cc0e9f > 2013-05-31 10:59:13,193 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-1:10.147.40.27) Executing copyTemplateFromSecondaryToPrimary. > secondaryStorage: > nfs://10.147.28.7/export/home/shweta/vmwaresecondary.premium, > templatePathAtSecondaryStorage: template/tmpl/1/8/, templateName: routing-8 > 2013-05-31 10:59:13,203 DEBUG [vmware.manager.VmwareManagerImpl] > (DirectAgent-1:10.147.40.27) Executing: sudo mount -t nfs > 10.147.28.7:/export/home/shweta/vmwaresecondary.premium > /var/cloudstack/mnt/VM/6909931290812.606fba60 > 2013-05-31 10:59:13,217 WARN [vmware.manager.VmwareManagerImpl] > (DirectAgent-1:10.147.40.27) Exception: sudo mount -t nfs > 10.147.28.7:/export/home/shweta/vmwaresecondary.premium > /var/cloudstack/mnt/VM/6909931290812.606fba60 > java.io.IOException: Cannot run program "sudo": java.io.IOException: > error=12, Cannot allocate memory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > at > com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.mount(VmwareManagerImpl.java:690) > at > com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.getMountPoint(VmwareManagerImpl.java:598) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:559) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:262) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3939) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:436) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) > 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) > Caused by: java.io.IOException: java.io.IOException: error=12, Cannot > allocate memory > at java.lang.UNIXProcess.(UNIXProcess.java:164) > at java.lang.ProcessImpl.start(ProcessImpl.java:81) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:468) > ... 17 more > 2013-05-31 10:59:13,218 WARN [vmware.manager.VmwareManagerImpl] > (DirectAgent-1:10.147.40.27) Unable to mount > 10.147.28.7:/export/home/shweta/vmwaresecondary.premium due to > java.io.IOException: Cannot run program "sudo": java.io.IOException: > error=12, Cannot allocate memory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > > > at com.cloud.utils.script.Script.execute(S
[jira] [Resolved] (CLOUDSTACK-2740) Talk with Hugo
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna resolved CLOUDSTACK-2740. -- Resolution: Fixed > 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] [Created] (CLOUDSTACK-2833) Deploy CS with Nicira NVP, Midonet Plugin
tuna created CLOUDSTACK-2833: Summary: Deploy CS with Nicira NVP, Midonet Plugin Key: CLOUDSTACK-2833 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2833 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna Try to using Nicira NVP, Midonet plugin. Then compare with the native SDN controller. I'll make some document on Wiki. -- 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-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 updated CLOUDSTACK-1779: - Fix Version/s: 4.2.0 > 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 > Fix For: 4.2.0 > > > 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-2793) PVLAN - Ubuntu 13.04 - Unable to start Stopped VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-2793: -- Attachment: management-server.log.gz > PVLAN - Ubuntu 13.04 - Unable to start Stopped VM > - > > Key: CLOUDSTACK-2793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2793 > 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 > host ubuntu 13.04 KVM ACS 4.2 PVLAN >Reporter: angeline shen >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.gz, management-server.log.gz, > Screenshot-CloudStack - Mozilla Firefox-5.png > > > 1. advance zone. Add 2 hosts. > create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, > netmask, start IP, end IP > gatewayprimary vlan secondary vlan IP > network1: 10.223.161.65 1611998 > 10.223.161.110- 10.223.161.113 > network2: 10.223.161.1291612997 > 10.223.161.150-10.223.161.153 > 2. Deploy VMs in both PVLAN shared network > 3. stop VMs in both PVLAN shared networks > 4. Start stopped VMs in network2 failed . Start stopped VMs in network1 > succeeded. > 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-57:job-55) Successfully released network resources for the vm > VM[User|z1admin1612-153V86] > 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-57:job-55) Successfully cleanued up resources for the vm > VM[User|z1admin1612-153V86] in Starting state > 2013-05-31 20:01:36,077 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) VM state transitted from :Starting to Stopped with > event: OperationFailedvm's original host id: 4 new host id: null host id > before s > tate transition: 4 > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) Hosts's actual total CPU: 9040 and CPU after > applying overprovisioning: 9040 > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) Hosts's actual total RAM: 16816881664 and RAM after > applying overprovisioning: 16816881664 > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) release cpu from host: 4, old used: 1200,reserved: > 0, actual total: 9040, total with overprovisioning: 9040; new used: > 1100,reserved > :0; movedfromreserved: false,moveToReserveredfalse > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) release mem from host: 4, old used: > 2281701376,reserved: 0, total: 16816881664; new used: 1744830464,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-31 20:01:36,101 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-57:job-55) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.StartVMCmd > com.cloud.exception.AgentUnavailableException: Resource [Host:4] is > unreachable: Host 4: Unable to start instance due to Unable to get answer > that is of class com.cloud.agent.api.StartAnswer > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:937) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3243) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1786) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120) > 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
[jira] [Updated] (CLOUDSTACK-2793) PVLAN - Ubuntu 13.04 - Unable to start Stopped VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-2793: -- Description: 1. advance zone. Add 2 hosts. create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, netmask, start IP, end IP gatewayprimary vlan secondary vlan IP network1: 10.223.161.65 1611998 10.223.161.110- 10.223.161.113 network2: 10.223.161.1291612997 10.223.161.150-10.223.161.153 2. Deploy VMs in both PVLAN shared network 3. stop VMs in both PVLAN shared networks 4. Start stopped VMs in network2 failed . Start stopped VMs in network1 succeeded. 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-57:job-55) Successfully released network resources for the vm VM[User|z1admin1612-153V86] 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-57:job-55) Successfully cleanued up resources for the vm VM[User|z1admin1612-153V86] in Starting state 2013-05-31 20:01:36,077 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-55) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: 4 new host id: null host id before s tate transition: 4 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-55) Hosts's actual total CPU: 9040 and CPU after applying overprovisioning: 9040 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-55) Hosts's actual total RAM: 16816881664 and RAM after applying overprovisioning: 16816881664 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-55) release cpu from host: 4, old used: 1200,reserved: 0, actual total: 9040, total with overprovisioning: 9040; new used: 1100,reserved :0; movedfromreserved: false,moveToReserveredfalse 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-57:job-55) release mem from host: 4, old used: 2281701376,reserved: 0, total: 16816881664; new used: 1744830464,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-05-31 20:01:36,101 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-57:job-55) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.StartVMCmd com.cloud.exception.AgentUnavailableException: Resource [Host:4] is unreachable: Host 4: Unable to start instance due to Unable to get answer that is of class com.cloud.agent.api.StartAnswer at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:937) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3243) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1786) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120) 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) Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is of class com.cloud.agent.api.StartAnswer at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:873) ... 19 more 2013-05-31 20:01:36,102 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-57:job-55) Complete async job-55, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is unreachable: Host 4: Unable to start instance due to Unable to get answer that is of class com.cloud.agent.api.StartAnswer 2013-05-31 20:01:36,735 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) HostStatsCollector is running... 2013-05-31 20:01:36,953 DEBUG [agent.trans
[jira] [Updated] (CLOUDSTACK-2793) PVLAN - Ubuntu 13.04 - Unable to start Stopped VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-2793: -- Assignee: Sheng Yang (was: angeline shen) > PVLAN - Ubuntu 13.04 - Unable to start Stopped VM > - > > Key: CLOUDSTACK-2793 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2793 > 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 > host ubuntu 13.04 KVM ACS 4.2 PVLAN >Reporter: angeline shen >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.gz, Screenshot-CloudStack - > Mozilla Firefox-5.png > > > 1. advance zone. Add 2 hosts. > create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, > netmask, start IP, end IP > 2. Deploy VMs in PVLAN shared network > 3. stop VM > 4. Start stopped VM failed > 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-57:job-55) Successfully released network resources for the vm > VM[User|z1admin1612-153V86] > 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-57:job-55) Successfully cleanued up resources for the vm > VM[User|z1admin1612-153V86] in Starting state > 2013-05-31 20:01:36,077 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) VM state transitted from :Starting to Stopped with > event: OperationFailedvm's original host id: 4 new host id: null host id > before s > tate transition: 4 > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) Hosts's actual total CPU: 9040 and CPU after > applying overprovisioning: 9040 > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) Hosts's actual total RAM: 16816881664 and RAM after > applying overprovisioning: 16816881664 > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) release cpu from host: 4, old used: 1200,reserved: > 0, actual total: 9040, total with overprovisioning: 9040; new used: > 1100,reserved > :0; movedfromreserved: false,moveToReserveredfalse > 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-57:job-55) release mem from host: 4, old used: > 2281701376,reserved: 0, total: 16816881664; new used: 1744830464,reserved:0; > movedfromreserved: false,moveToReserveredfalse > 2013-05-31 20:01:36,101 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-57:job-55) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.StartVMCmd > com.cloud.exception.AgentUnavailableException: Resource [Host:4] is > unreachable: Host 4: Unable to start instance due to Unable to get answer > that is of class com.cloud.agent.api.StartAnswer > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:937) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3243) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1786) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120) > 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) > Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get > answer that is of class com.cloud.agent.api.StartAnswer > at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80) > at > com.cloud.vm.VirtualMachineManager
[jira] [Commented] (CLOUDSTACK-2782) UI Support to add/remove VMware DC to CloudStack zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673801#comment-13673801 ] ASF subversion and git services commented on CLOUDSTACK-2782: - Commit 84634d4cf62d50f95e2e76445f77049d3eb8ca8e in branch refs/heads/master from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=84634d4 ] CLOUDSTACK-2782: UI - Infrastructure menu - zone detail page - rename action name to be more clear. > UI Support to add/remove VMware DC to CloudStack zone. > -- > > Key: CLOUDSTACK-2782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Need to modify zone wizard to allow adding VMware DC to Cloudstack zone. > We allow adding/removing cluster to/from zone outside of zone creation > wizard. Similarly need means to add/remove VMware DC to CloudStack zone. > API commands are - > To remove VMware DC from cloudstack zone :- > http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json > To add VMware DC to cloudstack zone :- > http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=keys&url=http%3A%2F%2FVCENTER%2Fdc%2Fc2&response=json -- 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-2782) UI Support to add/remove VMware DC to CloudStack zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673790#comment-13673790 ] ASF subversion and git services commented on CLOUDSTACK-2782: - Commit 5a525211de4da25fd89084b391357109688bbcca in branch refs/heads/master from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5a52521 ] CLOUDSTACK-2782: UI - Infrastructure menu - zone detail page - implement Remove VMWare DC action. > UI Support to add/remove VMware DC to CloudStack zone. > -- > > Key: CLOUDSTACK-2782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Need to modify zone wizard to allow adding VMware DC to Cloudstack zone. > We allow adding/removing cluster to/from zone outside of zone creation > wizard. Similarly need means to add/remove VMware DC to CloudStack zone. > API commands are - > To remove VMware DC from cloudstack zone :- > http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json > To add VMware DC to cloudstack zone :- > http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=keys&url=http%3A%2F%2FVCENTER%2Fdc%2Fc2&response=json -- 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-2825) SSVM:MS: Unable to download default template with socket error and stream closed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar closed CLOUDSTACK-2825. -- Resolution: Invalid Fix Version/s: 4.2.0 Restarted the agent on SSVM which fixed the issue. > SSVM:MS: Unable to download default template with socket error and stream > closed > > > Key: CLOUDSTACK-2825 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2825 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template >Affects Versions: 4.2.0 > Environment: Master >Reporter: Parth Jagirdar >Priority: Critical > Fix For: 4.2.0 > > Attachments: template_error.txt > > > Using new System VM templates. > Default template download failed with “socket error”. Upon destroying SSVM > multiple times this Error changes to “Stream Closed”. > NFS is reachable via SSVM and is mounted. > Able to register other templates and ISO’s. > Some errors in MS/SSVM and catalina logs. (Attached) (First is MS then > catalina and last is SSVM separated by a line) -- 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-2782) UI Support to add/remove VMware DC to CloudStack zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673772#comment-13673772 ] ASF subversion and git services commented on CLOUDSTACK-2782: - Commit bfe05acd95e8327cce96bc9a300f3803d03f9cce in branch refs/heads/master from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bfe05ac ] CLOUDSTACK-2782: UI - Infrastructure menu - zone detail page - add new action Add VMWare DC. > UI Support to add/remove VMware DC to CloudStack zone. > -- > > Key: CLOUDSTACK-2782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Need to modify zone wizard to allow adding VMware DC to Cloudstack zone. > We allow adding/removing cluster to/from zone outside of zone creation > wizard. Similarly need means to add/remove VMware DC to CloudStack zone. > API commands are - > To remove VMware DC from cloudstack zone :- > http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json > To add VMware DC to cloudstack zone :- > http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=keys&url=http%3A%2F%2FVCENTER%2Fdc%2Fc2&response=json -- 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-2832) Automation: support restore for VM created from ISO
Sudha Ponnaganti created CLOUDSTACK-2832: Summary: Automation: support restore for VM created from ISO Key: CLOUDSTACK-2832 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2832 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti 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-2831) Automation : New mapping model for CloudStack zone and Vmware datacenter
Sudha Ponnaganti created CLOUDSTACK-2831: Summary: Automation : New mapping model for CloudStack zone and Vmware datacenter Key: CLOUDSTACK-2831 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2831 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti 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-2829) QA Allow specification of different VIF drivers per traffic type in KVM
Sudha Ponnaganti created CLOUDSTACK-2829: Summary: QA Allow specification of different VIF drivers per traffic type in KVM Key: CLOUDSTACK-2829 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2829 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti 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-2830) Automation : Allow specification of different VIF drivers per traffic type in KVM
Sudha Ponnaganti created CLOUDSTACK-2830: Summary: Automation : Allow specification of different VIF drivers per traffic type in KVM Key: CLOUDSTACK-2830 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2830 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti 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-2828) Enable LRTM load balancing type for netscaler
Nick Wales created CLOUDSTACK-2828: -- Summary: Enable LRTM load balancing type for netscaler Key: CLOUDSTACK-2828 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2828 Project: CloudStack Issue Type: Wish Security Level: Public (Anyone can view this level - this is the default.) Components: Network Devices Reporter: Nick Wales Priority: Minor We use LRTM extensively on our non cloudstack managed netscaler devices. Would love to see it implemented in an upcoming release. -- 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-2029) zone wide primary storage support for cloudstack over vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673695#comment-13673695 ] Sudha Ponnaganti commented on CLOUDSTACK-2029: -- looks like this is already merged. Can the status be changed?? > zone wide primary storage support for cloudstack over vmware deployments > > > Key: CLOUDSTACK-2029 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > > Support for primary storage that span across clusters in CloudStack zone. > Similar to Amazon's EBS. > This is to facilitate virtual disk availability across clusters. > Functional Specification: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target > > A dedicated section is being added to the above FS with specifics around > VMware resource support. > Code for this feature can be found in branch > refs/heads/zone-primarystorage-vmware -- 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-1594) Secondary storage host always remains Alert status
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu reassigned CLOUDSTACK-1594: -- Assignee: (was: Anthony Xu) > Secondary storage host always remains Alert status > -- > > Key: CLOUDSTACK-1594 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1594 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.0.0, 4.2.0 > Environment: CS 4.2.0 > CentOS 6.2 x86_64 > Xenserver 6.0.1 >Reporter: roxanne chang >Priority: Minor > Fix For: 4.2.0 > > > The same problem as bug-668 > [https://issues.apache.org/jira/browse/CLOUDSTACK-668] -- 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-2827) Windows 8 (64 bit) guest OS enablement on KVM in cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-2827: --- Assignee: Venkata Siva Vijayendra Bhamidipati > Windows 8 (64 bit) guest OS enablement on KVM in cloudstack > --- > > Key: CLOUDSTACK-2827 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2827 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 > Environment: KVM deployments in cloudstack. >Reporter: Venkata Siva Vijayendra Bhamidipati >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Minor > Fix For: 4.2.0 > > > We need to provide the option for users to create a Windows 8 (64 bit) guest > VM on KVM server deployments in cloudstack. -- 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-2827) Windows 8 (64 bit) guest OS enablement on KVM in cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-2827: Status: Ready To Review (was: In Progress) > Windows 8 (64 bit) guest OS enablement on KVM in cloudstack > --- > > Key: CLOUDSTACK-2827 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2827 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 > Environment: KVM deployments in cloudstack. >Reporter: Venkata Siva Vijayendra Bhamidipati >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Minor > Fix For: 4.2.0 > > > We need to provide the option for users to create a Windows 8 (64 bit) guest > VM on KVM server deployments in cloudstack. -- 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-2826) Windows 8 64 bit guest OS support for KVM in cloudstack
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-2826: --- Summary: Windows 8 64 bit guest OS support for KVM in cloudstack Key: CLOUDSTACK-2826 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2826 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: KVM deployments on cloudstack Reporter: Venkata Siva Vijayendra Bhamidipati Priority: Minor Fix For: 4.2.0 We need to enable the option of creating a Windows 8 (64 bit) guest VM on a KVM server using cloudstack. -- 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-2827) Windows 8 (64 bit) guest OS enablement on KVM in cloudstack
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-2827: --- Summary: Windows 8 (64 bit) guest OS enablement on KVM in cloudstack Key: CLOUDSTACK-2827 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2827 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: KVM deployments in cloudstack. Reporter: Venkata Siva Vijayendra Bhamidipati Priority: Minor Fix For: 4.2.0 We need to provide the option for users to create a Windows 8 (64 bit) guest VM on KVM server deployments in cloudstack. -- 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-2825) SSVM:MS: Unable to download default template with socket error and stream closed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-2825: --- Attachment: template_error.txt > SSVM:MS: Unable to download default template with socket error and stream > closed > > > Key: CLOUDSTACK-2825 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2825 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template >Affects Versions: 4.2.0 > Environment: Master >Reporter: Parth Jagirdar >Priority: Critical > Attachments: template_error.txt > > > Using new System VM templates. > Default template download failed with “socket error”. Upon destroying SSVM > multiple times this Error changes to “Stream Closed”. > NFS is reachable via SSVM and is mounted. > Able to register other templates and ISO’s. > Some errors in MS/SSVM and catalina logs. (Attached) (First is MS then > catalina and last is SSVM separated by a line) -- 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-2825) SSVM:MS: Unable to download default template with socket error and stream closed
Parth Jagirdar created CLOUDSTACK-2825: -- Summary: SSVM:MS: Unable to download default template with socket error and stream closed Key: CLOUDSTACK-2825 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2825 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Template Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Priority: Critical Attachments: template_error.txt Using new System VM templates. Default template download failed with “socket error”. Upon destroying SSVM multiple times this Error changes to “Stream Closed”. NFS is reachable via SSVM and is mounted. Able to register other templates and ISO’s. Some errors in MS/SSVM and catalina logs. (Attached) (First is MS then catalina and last is SSVM separated by a line) -- 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-2823) SystemVMs start fail and have no HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-2823. Resolution: Duplicate > SystemVMs start fail and have no HA > --- > > Key: CLOUDSTACK-2823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: CentOS 6.4, KVM > CloudStack master >Reporter: Wei Zhou > > Host: > [root@cs-kvm015 ~]# virsh version > Compiled against library: libvirt 0.10.2 > Using library: libvirt 0.10.2 > Using API: QEMU 0.10.2 > Running hypervisor: QEMU 0.12.1 > Network: > em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 > (Can not connect outside) > em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.* > Issue descripion > (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, > management) > (2) After I destroyed SystemVM, no new SystemVM will be created automatically. > This issue only exists on master branch > Deploy 4.1 successfully, and SystemVms work 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] [Commented] (CLOUDSTACK-2759) listNetworks should show ACL applied state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673603#comment-13673603 ] Alena Prokharchyk commented on CLOUDSTACK-2759: --- I wouldn't return network ACL status as a part of the listNetworks call. As we don't return other Services current state (DHCP, PF, LB, DNS). All these details can be retrieved via listNetworkACLs/listLbRules/listPfRules calls. > 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] [Commented] (CLOUDSTACK-2754) System Vms do not start after the zone is set up and enabled.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673598#comment-13673598 ] Alena Prokharchyk commented on CLOUDSTACK-2754: --- Sangeetha, can you paste the result of the below sql execution, to the bug: select * From host where type='SecondaryStorage'; > System Vms do not start after the zone is set up and enabled. > - > > Key: CLOUDSTACK-2754 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2754 > 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: Build from object_store >Reporter: Sangeetha Hariharan >Priority: Blocker > Fix For: 4.2.0 > > > System Vms do not start after the zone is set up and enabled. > Set up an advanced zone with kvm host. > Both primary(NFS) and secondary storages (NFS) have been configured correctly. > Management server logs: > 2013-05-29 16:20:46,531 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) No secondary storage available in zone 1, wait until it > is ready to launch secondary storage vm > 2013-05-29 16:20:46,531 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is not ready to launch secondary storage VM yet > 2013-05-29 16:20:46,674 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Zone host is ready, but console proxy template: 3 is > not ready on secondary storage. > 2013-05-29 16:20:46,674 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Zone 1 is not ready to launch console proxy yet -- 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-2731) changing global/account level parameter "remote.access.vpn.client.iprange" is not allcoacting new ip address to vpn client
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673584#comment-13673584 ] Alena Prokharchyk commented on CLOUDSTACK-2731: --- Changing the global config variable will affect only new VPNs. The old ones will continue to run with the old settings. This is by design, so closing the bug. > changing global/account level parameter "remote.access.vpn.client.iprange" is > not allcoacting new ip address to vpn client > - > > Key: CLOUDSTACK-2731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2731 > 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: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: Logs.rar > > > Steps to reproduce: > - > 1-Set global parameter "remote.access.vpn.client.iprange" to some > range;restart MS > 2-create a vpn > 3-connect to vpn > 4-check ip address of vpn client;it will get ip address from range define in > step1 > 5-chenge global parameter "remote.access.vpn.client.iprange" to some range > other that in step 1;restart MS > 6-connect to vpn > 7-check ip address of vpn client > Actual > -- > -- > client is still holding previous ip adrress > Expected > -- > Client should get ip address from new ip range -- 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-2731) changing global/account level parameter "remote.access.vpn.client.iprange" is not allcoacting new ip address to vpn client
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-2731. --- Resolution: Invalid > changing global/account level parameter "remote.access.vpn.client.iprange" is > not allcoacting new ip address to vpn client > - > > Key: CLOUDSTACK-2731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2731 > 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: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: Logs.rar > > > Steps to reproduce: > - > 1-Set global parameter "remote.access.vpn.client.iprange" to some > range;restart MS > 2-create a vpn > 3-connect to vpn > 4-check ip address of vpn client;it will get ip address from range define in > step1 > 5-chenge global parameter "remote.access.vpn.client.iprange" to some range > other that in step 1;restart MS > 6-connect to vpn > 7-check ip address of vpn client > Actual > -- > -- > client is still holding previous ip adrress > Expected > -- > Client should get ip address from new ip range -- 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-2766) [VPC] [UI] Firewall service should not be enabled for acquired public IPs in VPC as the VPC VR provides option to configure Network ACLs.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-2766: -- Summary: [VPC] [UI] Firewall service should not be enabled for acquired public IPs in VPC as the VPC VR provides option to configure Network ACLs. (was: [VPC]Firewall service should not be enabled for acquired public IPs in VPC as the VPC VR provides option to configure Network ACLs.) > [VPC] [UI] 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] [Commented] (CLOUDSTACK-2794) Global parameter "router.template.id"should be removed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673564#comment-13673564 ] Alena Prokharchyk commented on CLOUDSTACK-2794: --- Be careful when remove it for existing customers who reset this global config to non-default value. They either have to be notified about 3 new parameters that came into picture (so they can update them properly), or DB upgrade code should take care of it somehow. > Global parameter "router.template.id"should be removed > --- > > Key: CLOUDSTACK-2794 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2794 > 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: prashant kumar mishra >Priority: Minor > Fix For: 4.2.0 > > > Since template is being select depend on parameter > router.template.xen,router.template.kvm,router.template.vmware. > "router.template.id" should be removed -- 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-2817) NPE while executing the API listLoadBalancerRules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-2817: - Assignee: Alena Prokharchyk > NPE while executing the API listLoadBalancerRules > - > > Key: CLOUDSTACK-2817 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2817 > 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 >Reporter: Abhinav Roy >Assignee: Alena Prokharchyk > Fix For: 4.2.0 > > > Executing the API listLoadBalancerRules throws a NPE : > -- > http://10.102.192.175:8096/client/api?command=listLoadBalancerRules&listAll=true > > cloud-stack-version="4.2.0-SNAPSHOT">530 > 2013-06-03 15:48:26,272 ERROR [cloud.api.ApiServer] (ApiServer-2:null) > unhandled exception executing api command: listLoadBalancerRules > java.lang.NullPointerException > at > com.cloud.api.ApiResponseHelper.createLoadBalancerResponse(ApiResponseHelper.java:752) > at > org.apache.cloudstack.api.command.user.loadbalancer.ListLoadBalancerRulesCmd.execute(ListLoadBalancerRulesCmd.java:115) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:524) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:367) > at com.cloud.api.ApiServer.handle(ApiServer.java:298) > at > org.apache.http.protocol.HttpService.doService(HttpService.java:375) > at > org.apache.http.protocol.HttpService.handleRequest(HttpService.java:290) > at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:988) > 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) -- 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-2817) NPE while executing the API listLoadBalancerRules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673555#comment-13673555 ] Alena Prokharchyk commented on CLOUDSTACK-2817: --- Abhinav, can you present the steps to reproduce? Also DB dump of your current DB would be helpful, please attach it to the bug. > NPE while executing the API listLoadBalancerRules > - > > Key: CLOUDSTACK-2817 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2817 > 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 >Reporter: Abhinav Roy > Fix For: 4.2.0 > > > Executing the API listLoadBalancerRules throws a NPE : > -- > http://10.102.192.175:8096/client/api?command=listLoadBalancerRules&listAll=true > > cloud-stack-version="4.2.0-SNAPSHOT">530 > 2013-06-03 15:48:26,272 ERROR [cloud.api.ApiServer] (ApiServer-2:null) > unhandled exception executing api command: listLoadBalancerRules > java.lang.NullPointerException > at > com.cloud.api.ApiResponseHelper.createLoadBalancerResponse(ApiResponseHelper.java:752) > at > org.apache.cloudstack.api.command.user.loadbalancer.ListLoadBalancerRulesCmd.execute(ListLoadBalancerRulesCmd.java:115) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:524) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:367) > at com.cloud.api.ApiServer.handle(ApiServer.java:298) > at > org.apache.http.protocol.HttpService.doService(HttpService.java:375) > at > org.apache.http.protocol.HttpService.handleRequest(HttpService.java:290) > at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:988) > 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) -- 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-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:comment-tabpanel&focusedCommentId=13673467#comment-13673467 ] ASF subversion and git services commented on CLOUDSTACK-2744: - Commit b325f7d3bd6274c979549794d8155ffa1492924f in branch refs/heads/master from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b325f7d ] CLOUDSTACK-2744: UI - create network offering dialog - when VPC checkbox is unchecked and LB service is checked, provider option InternalLbVm should be disabled. > [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 >Assignee: Jessica Wang > 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] [Resolved] (CLOUDSTACK-766) nTier Apps 2.0 : Assign a VLAN ID to a network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-766. -- Resolution: Fixed > nTier Apps 2.0 : Assign a VLAN ID to a network > -- > > Key: CLOUDSTACK-766 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-766 > 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 a sub task (2.18) of > https://issues.apache.org/jira/browse/CLOUDSTACK-621 > Allow admins to specify a VLAN ID while defining a Tier of a VPC. -- 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-766) nTier Apps 2.0 : Assign a VLAN ID to a network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673423#comment-13673423 ] ASF subversion and git services commented on CLOUDSTACK-766: Commit acc71fb735ded8e9e6378699a140d72c67a6428d in branch refs/heads/master from Brian Federle [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=acc71fb ] CLOUDSTACK-766: Support assigning VLAN ID to network On add network form, if selected network offering has specifyVlan=true, show VLAN text field. > nTier Apps 2.0 : Assign a VLAN ID to a network > -- > > Key: CLOUDSTACK-766 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-766 > 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 a sub task (2.18) of > https://issues.apache.org/jira/browse/CLOUDSTACK-621 > Allow admins to specify a VLAN ID while defining a Tier of a VPC. -- 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-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 ] Jessica Wang reassigned CLOUDSTACK-2744: Assignee: Jessica Wang > [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 >Assignee: Jessica Wang > 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] [Resolved] (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 ] Jessica Wang resolved CLOUDSTACK-2744. -- Resolution: Fixed > [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] [Commented] (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:comment-tabpanel&focusedCommentId=13673402#comment-13673402 ] ASF subversion and git services commented on CLOUDSTACK-2744: - Commit 24d6055177e8430993eae81b217991e2a09ec0ca in branch refs/heads/master from Jessica Wang [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=24d6055 ] CLOUDSTACK-2744: UI - create network offering dialog - when LB Type is selected as PublicLb, hide internalLbVm from provider list. > [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] [Resolved] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-2463.
---
Resolution: Fixed
> CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found
> (configuration : advanced network with security groups)
>
>
> Key: CLOUDSTACK-2463
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2463
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: pre-4.0.0
>Reporter: Nicolas Lamirault
>Assignee: Alena Prokharchyk
>Priority: Blocker
> Attachments: advanceSG_toNonSG_zone_db_conversion
>
>
> According Wei Zhou last patch
> (https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a new
> secondary storage. The SSVM creation failed due to :
> 2013-05-13 15:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-05-13 15:17:52,879 INFO
> [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No
> running secondary storage vms found in datacenter id=1, starting one
> 2013-05-13 15:17:52,889 INFO [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) No stopped secondary storage vm is available, need to
> allocate a new secondary storage vm
> 2013-05-13 15:17:52,894 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Assign secondary storage vm from a newly started instance
> for request from data center : 1
> 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner]
> (secstorage-1:null) Unexpected exception Found 22 networks of type Guest when
> expect to find 1
> com.cloud.utils.exception.CloudRuntimeException: Found 22 networks of type
> Guest when expect to find 1
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:552)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:666)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
> at
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121)
> at
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52)
> at
> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
> at
> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
> at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> We try this patch :
> diff --git
> a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> index fca89dc..d40d22f 100755
> --- a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> +++ b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> @@ -541,7 +541,7 @@ public class SecondaryStorageManagerImpl extends
> ManagerBase implements Secondar
> DataCenter dc = _dcDao.findById(plan.getDataCenterId());
> TrafficType defaultTrafficType = TrafficType.Public;
> - if (dc.getNetworkType() == NetworkType.Basic ||
> dc.isSecurityGroupEnabled()) {
> + if (dc.getNetworkType() == NetworkType.Basic) {
> defaultTrafficType = TrafficType.Guest;
> }
> @@ -1143,7 +1143,7 @@ publi
[jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673370#comment-13673370 ] Alena Prokharchyk commented on CLOUDSTACK-2463: --- Attaching the instructions (as well as limitations) on how to convert Advance SG enabled zone to Advance SG disabled zone, attached to the bug. The instructions can be applied only while being on 2.2.x system. > CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found > (configuration : advanced network with security groups) > > > Key: CLOUDSTACK-2463 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2463 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: pre-4.0.0 >Reporter: Nicolas Lamirault >Assignee: Alena Prokharchyk >Priority: Blocker > Attachments: advanceSG_toNonSG_zone_db_conversion > > > According Wei Zhou last patch > (https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a new > secondary storage. The SSVM creation failed due to : > 2013-05-13 15:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage VM > 2013-05-13 15:17:52,879 INFO > [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No > running secondary storage vms found in datacenter id=1, starting one > 2013-05-13 15:17:52,889 INFO [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) No stopped secondary storage vm is available, need to > allocate a new secondary storage vm > 2013-05-13 15:17:52,894 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Assign secondary storage vm from a newly started instance > for request from data center : 1 > 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner] > (secstorage-1:null) Unexpected exception Found 22 networks of type Guest when > expect to find 1 > com.cloud.utils.exception.CloudRuntimeException: Found 22 networks of type > Guest when expect to find 1 > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:552) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:666) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > We try this patch : > diff --git > a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java > b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java > index fca89dc..d40d22f 100755 > --- a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java > +++ b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java > @@ -541,7 +541,7 @@ public class SecondaryStorageManagerImpl extends > ManagerBase implements Secondar > DataCenter dc = _dcDao.findById(plan.getDataCenterId()); > TrafficType defaultTrafficType = Traffi
[jira] [Updated] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk updated CLOUDSTACK-2463:
--
Attachment: advanceSG_toNonSG_zone_db_conversion
> CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found
> (configuration : advanced network with security groups)
>
>
> Key: CLOUDSTACK-2463
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2463
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: pre-4.0.0
>Reporter: Nicolas Lamirault
>Assignee: Alena Prokharchyk
>Priority: Blocker
> Attachments: advanceSG_toNonSG_zone_db_conversion
>
>
> According Wei Zhou last patch
> (https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a new
> secondary storage. The SSVM creation failed due to :
> 2013-05-13 15:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-05-13 15:17:52,879 INFO
> [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No
> running secondary storage vms found in datacenter id=1, starting one
> 2013-05-13 15:17:52,889 INFO [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) No stopped secondary storage vm is available, need to
> allocate a new secondary storage vm
> 2013-05-13 15:17:52,894 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Assign secondary storage vm from a newly started instance
> for request from data center : 1
> 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner]
> (secstorage-1:null) Unexpected exception Found 22 networks of type Guest when
> expect to find 1
> com.cloud.utils.exception.CloudRuntimeException: Found 22 networks of type
> Guest when expect to find 1
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:552)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:666)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
> at
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121)
> at
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52)
> at
> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
> at
> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
> at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> We try this patch :
> diff --git
> a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> index fca89dc..d40d22f 100755
> --- a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> +++ b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> @@ -541,7 +541,7 @@ public class SecondaryStorageManagerImpl extends
> ManagerBase implements Secondar
> DataCenter dc = _dcDao.findById(plan.getDataCenterId());
> TrafficType defaultTrafficType = TrafficType.Public;
> - if (dc.getNetworkType() == NetworkType.Basic ||
> dc.isSecurityGroupEnabled()) {
> + if (dc.getNetworkType() == NetworkType.Basic) {
> defaultTrafficType = TrafficType.Guest;
> }
[jira] [Updated] (CLOUDSTACK-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-2822: -- Component/s: Doc Assignee: (was: Alena Prokharchyk) Documentation bug. The release notes for 4.1: http://jenkins.buildacloud.org/job/docs-4.1-releasenotes/lastSuccessfulBuild/artifact/Apache_CloudStack-4.1.0-Release_Notes-en-US.pdf say to upload 3.0.5 vmWare template instead of 4.0 > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached logs. -- 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-2824) API:MS:Ability to delete events and alerts-Auto Purge for Alerts doesn't work
Parth Jagirdar created CLOUDSTACK-2824: -- Summary: API:MS:Ability to delete events and alerts-Auto Purge for Alerts doesn't work Key: CLOUDSTACK-2824 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2824 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.0 Environment: Master Reporter: Parth Jagirdar Auto Purge for Alerts doesn't work. However it works fine for Events. Change the global setting for desired number of days and restart MS. Observe that after set number of days elapsed, Alerts are still present. -- 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-2818) [N-tier : Internal LB between VPC tiers] createLoadBalancer and listLoadBalancer APIs don't take "public" as a value for the parameter "scheme"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673307#comment-13673307 ] Abhinav Roy commented on CLOUDSTACK-2818: - okay. Then please edit the FS. It says both are supported. > [N-tier : Internal LB between VPC tiers] createLoadBalancer and > listLoadBalancer APIs don't take "public" as a value for the parameter > "scheme" > --- > > Key: CLOUDSTACK-2818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2818 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Alena Prokharchyk > Fix For: 4.2.0 > > > listLoadBalancer and createLoadBalancer APIs don't take public as a value for > parameter "scheme" , marks it as invalid value for the parameter . > http://10.102.192.175:8096/client/api?command=createLoadBalancer&name=publicLB1&displayText=PublicLb1&networkId=205&sourceIpAddressNetworkId=205&scheme=public&algorithm=roundrobin&sourceport=22&instanceport=22 > cloud-stack-version="4.2.0-SNAPSHOT">4314350Invalid > value for scheme. Supported value is > Internal > 2013-06-03 16:00:15,835 INFO [cloud.api.ApiServer] (ApiServer-4:null) > (userId=1 accountId=1 sessionId=null) /10.144.7.12 -- GET > /client/api?command=createLoadBalancer&name=publicLB1&displayText=PublicLb1&networkId=205&sourceIpAddressNetworkId=205&scheme=public&algorithm=roundrobin&sourceport=22&instanceport=22 > HTTP/1.1 431 Invalid value for scheme. Supported value is Internal > 2013-06-03 16:09:54,070 INFO [cloud.api.ApiServer] (ApiServer-5:null) > (userId=1 accountId=1 sessionId=null) /10.144.7.12 -- GET > /client/api?command=listLoadBalancers&listAll=true&scheme=public HTTP/1.1 431 > Invalid value for scheme. Supported value is Internal -- 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-2675) Missing network_id on restarting/host adding to a new shared network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673304#comment-13673304 ] Tomasz Zieba commented on CLOUDSTACK-2675: -- I have found that there is a problem with INSERT SQL statement. When you are creating vm machine and take a shared network, CloudStack create following sql statements: 8 Query SET autocommit=0 8 Query SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED 8 Query SELECT 1 8 Query SET autocommit=1 8 Query SELECT vm_template.id, vm_template.format, vm_template.unique_name, vm_template.name, vm_template.public, vm_template.featured, vm_template.type, vm_template.url, vm_template.hvm, vm_template.bits, vm_template.created, vm_template.removed, vm_template.account_id, vm_template.checksum, vm_template.display_text, vm_template.enable_password, vm_template.guest_os_id, vm_template.bootable, vm_template.prepopulate, vm_template.cross_zones, vm_template.hypervisor_type, vm_template.extractable, vm_template.source_template_id, vm_template.template_tag, vm_template.uuid, vm_template.sort_key, vm_template.enable_sshkey FROM vm_template WHERE vm_template.type = 'SYSTEM' AND vm_template.hypervisor_type = 'XenServer' ORDER BY vm_template.id DESC 8 Query SET autocommit=1 9 Query SET autocommit=0 9 Query SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED 9 Query SELECT 1 9 Query SET autocommit=0 9 Query INSERT INTO vm_instance (vm_instance.id, vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, vm_instance.proxy_assign_time, vm_instance.state, vm_instance.private_ip_address, vm_instance.instance_name, vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, vm_instance.last_host_id, vm_instance.pod_id, vm_instance.private_mac_address, vm_instance.data_center_id, vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, vm_instance.update_time, vm_instance.domain_id, vm_instance.account_id, vm_instance.service_offering_id, vm_instance.reservation_id, vm_instance.hypervisor_type, vm_instance.uuid, vm_instance.type) VALUES (29, _binary'r-29-VM', _binary'L2fmUmx6ikdjMva5WFwRleblZTgaCjdH8JPYTcAVmcQ=', null, null, 'Stopped', null, _binary'r-29-VM', 1, 15, null, null, null, null, 1, 'DomainRouter', 1, 0, 0, '2013-06-03 14:27:17', null, 1, 1, 7, null, 'XenServer', _binary'29443e94-3960-4370-8970-4f2917bfb940', 'DomainRouter') 9 Query INSERT INTO domain_router (domain_router.element_id, domain_router.public_ip_address, domain_router.public_mac_address, domain_router.public_netmask, domain_router.is_redundant_router, domain_router.priority, domain_router.is_priority_bumpup, domain_router.redundant_state, domain_router.stop_pending, domain_router.role, domain_router.template_version, domain_router.scripts_version, domain_router.vpc_id, domain_router.id) VALUES (2, null, null, null, 0, 0, 0, 'UNKNOWN', 0, 'VIRTUAL_ROUTER', null, null, null, 29) 9 Query rollback 9 Query rollback 9 Query SET autocommit=1 There is a problem with " INSERT INTO domain_router " statement because the definition of domain_router table is the following: mysql> describe domain_router; +-+-+--+-+-+---+ | Field | Type| Null | Key | Default | Extra | +-+-+--+-+-+---+ | id | bigint(20) unsigned | NO | PRI | NULL| | | element_id | bigint(20) unsigned | NO | MUL | NULL| | | public_mac_address | varchar(17) | YES | | NULL| | | public_ip_address | char(40)| YES | | NULL| | | public_netmask | varchar(15) | YES | | NULL| | | guest_netmask | varchar(15) | YES | | NULL| | | guest_ip_address| char(40)| YES | | NULL| | | network_id | bigint(20) unsigned | NO | | NULL| | | is_redundant_router | int(1) unsigned | NO | | NULL| | | priority| int(4) unsigned | YES | | NULL| | | is_priority_bumpup | int(1) unsigned | NO | | NULL| | | redundant_state | varchar(64) | NO | | NULL| | | stop_pending| int(1) unsigned | NO | | NULL| | | role| varchar(64) | NO | | NULL| | | template_version| varchar(100)
[jira] [Commented] (CLOUDSTACK-2810) [ApiDiscover] listApis API doesn't contain any information about "addVmwareDc"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673298#comment-13673298 ] ASF subversion and git services commented on CLOUDSTACK-2810: - Commit db655ae8c76753fb63ac87d82a337159ec5d3517 in branch refs/heads/master from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=db655ae ] CLOUDSTACK-2810: Include new vmware APIs in discovery Discovery plugin will detect APIs from pluggable services and map them to those in commands.properties. Including the latter to complete the mapping so listApis now returns these APIs. Also included fix for API docs. Signed-off-by: Prasanna Santhanam > [ApiDiscover] listApis API doesn't contain any information about "addVmwareDc" > -- > > Key: CLOUDSTACK-2810 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2810 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 > Environment: commit # >Reporter: venkata swamybabu budumuru >Assignee: Prasanna Santhanam > Fix For: 4.2.0 > > Attachments: test.txt > > > Steps to reproduce : > 1. Have latest CS setup with at least one advanced zone. > 2. check the output for "listApis" API for "addVmwareDc" api info > Observations: > (i) addVmwareDc API is not in the list of APIs shown. > attaching the output from "curl --globoff > "http://10.147.59.194:8096/api?command=listApis"; > test.txt" > (ii) cloudmonkey utility after sync also doesn't list this API info due the > above issue. -- 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-2810) [ApiDiscover] listApis API doesn't contain any information about "addVmwareDc"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam resolved CLOUDSTACK-2810. Resolution: Fixed Assignee: Prasanna Santhanam (was: Sateesh Chodapuneedi) https://gist.github.com/vogxn/5699443 > [ApiDiscover] listApis API doesn't contain any information about "addVmwareDc" > -- > > Key: CLOUDSTACK-2810 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2810 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 > Environment: commit # >Reporter: venkata swamybabu budumuru >Assignee: Prasanna Santhanam > Fix For: 4.2.0 > > Attachments: test.txt > > > Steps to reproduce : > 1. Have latest CS setup with at least one advanced zone. > 2. check the output for "listApis" API for "addVmwareDc" api info > Observations: > (i) addVmwareDc API is not in the list of APIs shown. > attaching the output from "curl --globoff > "http://10.147.59.194:8096/api?command=listApis"; > test.txt" > (ii) cloudmonkey utility after sync also doesn't list this API info due the > above issue. -- 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-105) /tmp/stream-unix.####.###### stale sockets causing inodes to run out on Xenserver
[
https://issues.apache.org/jira/browse/CLOUDSTACK-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673287#comment-13673287
]
Stephen Turner commented on CLOUDSTACK-105:
---
Thanks, Caleb, that's good news.
> /tmp/stream-unix..## stale sockets causing inodes to run out on
> Xenserver
> -
>
> Key: CLOUDSTACK-105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-105
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Third-Party Bugs
>Affects Versions: pre-4.0.0
> Environment: Xenserver 6.0.2
> Cloudstack 3.0.2
>Reporter: Caleb Call
>Assignee: Devdeep Singh
> Fix For: 4.1.0
>
> Attachments: messages
>
>
> We came across an interesting issue in one of our clusters. We ran out of
> inodes on all of our cluster members (since when does this happen in 2012?).
> When this happened, it in turn made the / filesystem a read-only filesystem
> which in turn made all the hosts go in to emergency maintenance mode and as a
> result get marked down by Cloudstack. We found that it was caused by
> hundreds of thousands of stale socket files in /tmp named
> "stream-unix..##". To resolve the issue, we had to delete those
> stale socket files (find /tmp -name "*stream*" -mtime +7 -exec rm -v {} \;),
> then kill and restart xapi, then correct the emergency maintenance mode.
> These hosts had only been up for 45 days before this issue occurred.
> In our scouring of the interwebs, the only other instance we've been able to
> find of this (or similar) happening is in the same setup we are currently
> running. Xenserver 6.0.2 with CS 3.0.2. Do these stream-unix sockets have
> anything to do with Cloudstack? I would think if this was a Xenserver issue
> (bug), there would be a lot more on the internet about this happening. For a
> temporary workaround, we've added a cronjob to cleanup these files but we'd
> really like to address the actual issue that's causing these sockets to
> become stale and not get cleaned-up.
--
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-2815) Dedicated Resources API's are failing with Unknown API command with the enviornement created using RPM's (ex: listDedicatedZones )
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam resolved CLOUDSTACK-2815. Resolution: Fixed Assignee: Prasanna Santhanam Hadn't fixed the simulator context which I was testing. All commands should work now. > Dedicated Resources API's are failing with Unknown API command with the > enviornement created using RPM's (ex: listDedicatedZones ) > -- > > Key: CLOUDSTACK-2815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2815 > 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 >Assignee: Prasanna Santhanam >Priority: Critical > Attachments: apilog.log, management-server.log > > > Setup: > 1. Advanced Networking Zone with VMWARE > Observation: > This is regarding the feature that is committed to the master recently > (CLOUDSTACK-681: Dedicated Resources - Explicit Dedication, Private zone, > pod, cluster or host) . > I have created the setup using latest 4.2 RPM’s . In my setup all the API > calls related to this feature are failing saying “Unknown API commands” > Is there any issue with the packaging ?? > 1) Same behavior observed with UI/API. > 2 ) Dedicated resources jar's are present in my setup: > [root@asf41 management]# find / -name cloud-plugin-dedicated-resources* > -print > /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-dedicated-resources-4.2.0-SNAPSHOT.jar > 2013-06-03 15:40:50,092 INFO [cloud.api.ApiServer] (catalina-exec-11:null) > (userId=2 accountId=2 sessionId=1168F5DF82DF426D8686126E0578D94D) 10.144.6.19 > -- GET > command=listDedicatedZones&zoneid=fdf01d6f-7a47-4bab-ba5a-d90188b83208&response=json&sessionkey=DNyID50jXFt8kwajxyDfxKFOYsw%3D&_=1370254416347 > Unknown API command: listDedicatedZones 432 Unknown API command: > listDedicatedZones > 2013-06-03 15:42:19,136 INFO [cloud.api.ApiServer] (catalina-exec-21:null) > (userId=2 accountId=2 sessionId=1168F5DF82DF426D8686126E0578D94D) 10.144.6.19 > -- GET > command=dedicateZone&zoneId=fdf01d6f-7a47-4bab-ba5a-d90188b83208&domainId=cfe81c1c-c9d9-11e2-b3cc-c2ae49691a00&response=json&sessionkey=DNyID50jXFt8kwajxyDfxKFOYsw%3D&_=1370254505255 > Unknown API command: dedicateZone 432 Unknown API command: dedicateZone -- 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-2818) [N-tier : Internal LB between VPC tiers] createLoadBalancer and listLoadBalancer APIs don't take "public" as a value for the parameter "scheme"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673276#comment-13673276 ] Alena Prokharchyk commented on CLOUDSTACK-2818: --- Only Internal value is supported in Campo. > [N-tier : Internal LB between VPC tiers] createLoadBalancer and > listLoadBalancer APIs don't take "public" as a value for the parameter > "scheme" > --- > > Key: CLOUDSTACK-2818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2818 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Alena Prokharchyk > Fix For: 4.2.0 > > > listLoadBalancer and createLoadBalancer APIs don't take public as a value for > parameter "scheme" , marks it as invalid value for the parameter . > http://10.102.192.175:8096/client/api?command=createLoadBalancer&name=publicLB1&displayText=PublicLb1&networkId=205&sourceIpAddressNetworkId=205&scheme=public&algorithm=roundrobin&sourceport=22&instanceport=22 > cloud-stack-version="4.2.0-SNAPSHOT">4314350Invalid > value for scheme. Supported value is > Internal > 2013-06-03 16:00:15,835 INFO [cloud.api.ApiServer] (ApiServer-4:null) > (userId=1 accountId=1 sessionId=null) /10.144.7.12 -- GET > /client/api?command=createLoadBalancer&name=publicLB1&displayText=PublicLb1&networkId=205&sourceIpAddressNetworkId=205&scheme=public&algorithm=roundrobin&sourceport=22&instanceport=22 > HTTP/1.1 431 Invalid value for scheme. Supported value is Internal > 2013-06-03 16:09:54,070 INFO [cloud.api.ApiServer] (ApiServer-5:null) > (userId=1 accountId=1 sessionId=null) /10.144.7.12 -- GET > /client/api?command=listLoadBalancers&listAll=true&scheme=public HTTP/1.1 431 > Invalid value for scheme. Supported value is Internal -- 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-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-2822: - Assignee: Alena Prokharchyk > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Alena Prokharchyk >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached logs. -- 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-2818) [N-tier : Internal LB between VPC tiers] createLoadBalancer and listLoadBalancer APIs don't take "public" as a value for the parameter "scheme"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-2818. --- Resolution: Won't Fix > [N-tier : Internal LB between VPC tiers] createLoadBalancer and > listLoadBalancer APIs don't take "public" as a value for the parameter > "scheme" > --- > > Key: CLOUDSTACK-2818 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2818 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Alena Prokharchyk > Fix For: 4.2.0 > > > listLoadBalancer and createLoadBalancer APIs don't take public as a value for > parameter "scheme" , marks it as invalid value for the parameter . > http://10.102.192.175:8096/client/api?command=createLoadBalancer&name=publicLB1&displayText=PublicLb1&networkId=205&sourceIpAddressNetworkId=205&scheme=public&algorithm=roundrobin&sourceport=22&instanceport=22 > cloud-stack-version="4.2.0-SNAPSHOT">4314350Invalid > value for scheme. Supported value is > Internal > 2013-06-03 16:00:15,835 INFO [cloud.api.ApiServer] (ApiServer-4:null) > (userId=1 accountId=1 sessionId=null) /10.144.7.12 -- GET > /client/api?command=createLoadBalancer&name=publicLB1&displayText=PublicLb1&networkId=205&sourceIpAddressNetworkId=205&scheme=public&algorithm=roundrobin&sourceport=22&instanceport=22 > HTTP/1.1 431 Invalid value for scheme. Supported value is Internal > 2013-06-03 16:09:54,070 INFO [cloud.api.ApiServer] (ApiServer-5:null) > (userId=1 accountId=1 sessionId=null) /10.144.7.12 -- GET > /client/api?command=listLoadBalancers&listAll=true&scheme=public HTTP/1.1 431 > Invalid value for scheme. Supported value is Internal -- 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-2815) Dedicated Resources API's are failing with Unknown API command with the enviornement created using RPM's (ex: listDedicatedZones )
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673273#comment-13673273 ] ASF subversion and git services commented on CLOUDSTACK-2815: - Commit 767ed065c500b6e73451135d538ebe999f0d17f1 in branch refs/heads/master from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=767ed06 ] CLOUDSTACK-2815: Include dedication in simulator context SimulatoComponentContext need sto include the dedicated resource manager to see the commands/apis exposed by it. Signed-off-by: Prasanna Santhanam > Dedicated Resources API's are failing with Unknown API command with the > enviornement created using RPM's (ex: listDedicatedZones ) > -- > > Key: CLOUDSTACK-2815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2815 > 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 >Priority: Critical > Attachments: apilog.log, management-server.log > > > Setup: > 1. Advanced Networking Zone with VMWARE > Observation: > This is regarding the feature that is committed to the master recently > (CLOUDSTACK-681: Dedicated Resources - Explicit Dedication, Private zone, > pod, cluster or host) . > I have created the setup using latest 4.2 RPM’s . In my setup all the API > calls related to this feature are failing saying “Unknown API commands” > Is there any issue with the packaging ?? > 1) Same behavior observed with UI/API. > 2 ) Dedicated resources jar's are present in my setup: > [root@asf41 management]# find / -name cloud-plugin-dedicated-resources* > -print > /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-dedicated-resources-4.2.0-SNAPSHOT.jar > 2013-06-03 15:40:50,092 INFO [cloud.api.ApiServer] (catalina-exec-11:null) > (userId=2 accountId=2 sessionId=1168F5DF82DF426D8686126E0578D94D) 10.144.6.19 > -- GET > command=listDedicatedZones&zoneid=fdf01d6f-7a47-4bab-ba5a-d90188b83208&response=json&sessionkey=DNyID50jXFt8kwajxyDfxKFOYsw%3D&_=1370254416347 > Unknown API command: listDedicatedZones 432 Unknown API command: > listDedicatedZones > 2013-06-03 15:42:19,136 INFO [cloud.api.ApiServer] (catalina-exec-21:null) > (userId=2 accountId=2 sessionId=1168F5DF82DF426D8686126E0578D94D) 10.144.6.19 > -- GET > command=dedicateZone&zoneId=fdf01d6f-7a47-4bab-ba5a-d90188b83208&domainId=cfe81c1c-c9d9-11e2-b3cc-c2ae49691a00&response=json&sessionkey=DNyID50jXFt8kwajxyDfxKFOYsw%3D&_=1370254505255 > Unknown API command: dedicateZone 432 Unknown API command: dedicateZone -- 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-2815) Dedicated Resources API's are failing with Unknown API command with the enviornement created using RPM's (ex: listDedicatedZones )
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam reassigned CLOUDSTACK-2815: -- Assignee: (was: Prasanna Santhanam) unassign while i hit the bed > Dedicated Resources API's are failing with Unknown API command with the > enviornement created using RPM's (ex: listDedicatedZones ) > -- > > Key: CLOUDSTACK-2815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2815 > 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 >Priority: Critical > Attachments: apilog.log, management-server.log > > > Setup: > 1. Advanced Networking Zone with VMWARE > Observation: > This is regarding the feature that is committed to the master recently > (CLOUDSTACK-681: Dedicated Resources - Explicit Dedication, Private zone, > pod, cluster or host) . > I have created the setup using latest 4.2 RPM’s . In my setup all the API > calls related to this feature are failing saying “Unknown API commands” > Is there any issue with the packaging ?? > 1) Same behavior observed with UI/API. > 2 ) Dedicated resources jar's are present in my setup: > [root@asf41 management]# find / -name cloud-plugin-dedicated-resources* > -print > /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-dedicated-resources-4.2.0-SNAPSHOT.jar > 2013-06-03 15:40:50,092 INFO [cloud.api.ApiServer] (catalina-exec-11:null) > (userId=2 accountId=2 sessionId=1168F5DF82DF426D8686126E0578D94D) 10.144.6.19 > -- GET > command=listDedicatedZones&zoneid=fdf01d6f-7a47-4bab-ba5a-d90188b83208&response=json&sessionkey=DNyID50jXFt8kwajxyDfxKFOYsw%3D&_=1370254416347 > Unknown API command: listDedicatedZones 432 Unknown API command: > listDedicatedZones > 2013-06-03 15:42:19,136 INFO [cloud.api.ApiServer] (catalina-exec-21:null) > (userId=2 accountId=2 sessionId=1168F5DF82DF426D8686126E0578D94D) 10.144.6.19 > -- GET > command=dedicateZone&zoneId=fdf01d6f-7a47-4bab-ba5a-d90188b83208&domainId=cfe81c1c-c9d9-11e2-b3cc-c2ae49691a00&response=json&sessionkey=DNyID50jXFt8kwajxyDfxKFOYsw%3D&_=1370254505255 > Unknown API command: dedicateZone 432 Unknown API command: dedicateZone -- 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-2782) UI Support to add/remove VMware DC to CloudStack zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-2782: Priority: Blocker (was: Major) > UI Support to add/remove VMware DC to CloudStack zone. > -- > > Key: CLOUDSTACK-2782 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Need to modify zone wizard to allow adding VMware DC to Cloudstack zone. > We allow adding/removing cluster to/from zone outside of zone creation > wizard. Similarly need means to add/remove VMware DC to CloudStack zone. > API commands are - > To remove VMware DC from cloudstack zone :- > http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json > To add VMware DC to cloudstack zone :- > http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=keys&url=http%3A%2F%2FVCENTER%2Fdc%2Fc2&response=json -- 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-105) /tmp/stream-unix.####.###### stale sockets causing inodes to run out on Xenserver
[
https://issues.apache.org/jira/browse/CLOUDSTACK-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673217#comment-13673217
]
Caleb Call commented on CLOUDSTACK-105:
---
Sorry for the delayed response. I just checked this morning and I don't have
any of these files hanging around. I'd say this likely fixed the issue.
> /tmp/stream-unix..## stale sockets causing inodes to run out on
> Xenserver
> -
>
> Key: CLOUDSTACK-105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-105
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Third-Party Bugs
>Affects Versions: pre-4.0.0
> Environment: Xenserver 6.0.2
> Cloudstack 3.0.2
>Reporter: Caleb Call
>Assignee: Devdeep Singh
> Fix For: 4.1.0
>
> Attachments: messages
>
>
> We came across an interesting issue in one of our clusters. We ran out of
> inodes on all of our cluster members (since when does this happen in 2012?).
> When this happened, it in turn made the / filesystem a read-only filesystem
> which in turn made all the hosts go in to emergency maintenance mode and as a
> result get marked down by Cloudstack. We found that it was caused by
> hundreds of thousands of stale socket files in /tmp named
> "stream-unix..##". To resolve the issue, we had to delete those
> stale socket files (find /tmp -name "*stream*" -mtime +7 -exec rm -v {} \;),
> then kill and restart xapi, then correct the emergency maintenance mode.
> These hosts had only been up for 45 days before this issue occurred.
> In our scouring of the interwebs, the only other instance we've been able to
> find of this (or similar) happening is in the same setup we are currently
> running. Xenserver 6.0.2 with CS 3.0.2. Do these stream-unix sockets have
> anything to do with Cloudstack? I would think if this was a Xenserver issue
> (bug), there would be a lot more on the internet about this happening. For a
> temporary workaround, we've added a cronjob to cleanup these files but we'd
> really like to address the actual issue that's causing these sockets to
> become stale and not get cleaned-up.
--
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-2823) SystemVMs start fail and have no HA
Wei Zhou created CLOUDSTACK-2823: Summary: SystemVMs start fail and have no HA Key: CLOUDSTACK-2823 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Environment: CentOS 6.4, KVM CloudStack master Reporter: Wei Zhou Host: [root@cs-kvm015 ~]# virsh version Compiled against library: libvirt 0.10.2 Using library: libvirt 0.10.2 Using API: QEMU 0.10.2 Running hypervisor: QEMU 0.12.1 Network: em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 (Can not connect outside) em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.* Issue descripion (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, management) (2) After I destroyed SystemVM, no new SystemVM will be created automatically. This issue only exists on master branch Deploy 4.1 successfully, and SystemVms work 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-1578) Egress Firewall Rules - Ability to change the default
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy updated CLOUDSTACK-1578: -- Issue Type: Bug (was: Improvement) > Egress Firewall Rules - Ability to change the default > - > > Key: CLOUDSTACK-1578 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1578 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Manan Shah >Assignee: Jayapal Reddy > Fix For: 4.2.0 > > > With the addition of Egress Firewall rules, all of the networks that have a > network offering with FW service enabled using VR would block the outgoing > traffic by default. This would work for a lot of customers who require > additional security. > But there might be a whole lot of customers who would want to keep the > functionality like Amazon and not have all of the Egress traffic being > blocked by default. > This ticket is to provide an improvement to have the default behavior > controlled by a flag. -- 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-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673144#comment-13673144 ] Nicolas Lamirault commented on CLOUDSTACK-2822: --- i try both systemvm-vmware-3.0.5 and systemvm-vmware-4.0 . > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached logs. -- 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-2029) zone wide primary storage support for cloudstack over vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673139#comment-13673139 ] Wei Zhou commented on CLOUDSTACK-2029: -- add primary storage verified ok. There is still an issue in the "add primary storage" process of "Add zone" wizard. > zone wide primary storage support for cloudstack over vmware deployments > > > Key: CLOUDSTACK-2029 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > > Support for primary storage that span across clusters in CloudStack zone. > Similar to Amazon's EBS. > This is to facilitate virtual disk availability across clusters. > Functional Specification: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target > > A dedicated section is being added to the above FS with specifics around > VMware resource support. > Code for this feature can be found in branch > refs/heads/zone-primarystorage-vmware -- 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-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673130#comment-13673130 ] Wei Zhou commented on CLOUDSTACK-2822: -- try systemvm-vmware-4.0 ? It broke the upgrade from 2.2.14 to 3.0.X before, but has been fixed. > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached logs. -- 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-2648) [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises created on VR in case of multiple subnets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673131#comment-13673131 ] ASF subversion and git services commented on CLOUDSTACK-2648: - Commit 48913679e80e50228b1bd4b3d17fe5245461626a in branch refs/heads/master from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4891367 ] CLOUDSTACK-2648 [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises created on VR in case of multiple subnets Signed-off-by: Abhinandan Prateek > [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises > created on VR in case of multiple subnets > --- > > Key: CLOUDSTACK-2648 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2648 > 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 on master: > CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz >Reporter: Sanjeev N >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.rar, SMlog > > > Reboot or start/stop router vm deletes the ip alises created on VR in case of > multiple subnets > Steps to Reproduce: > = > 1.Bring up CS in basic zone with xenserver6.1 > 2.Exhaust all the guest IP addresses in primary ip range by deploying guest > vms > 3.Add new guest IP range in new subnet > 4.Deploy guest vms using the ip addresses from the new range > 5.Reboot or stop/start VR > Observations: > > After step4 ip alias gets created on VR with IP address from the new subnet. > After reboot or stop/start of the VR ip alias is getting removed from the VR. > Verified the SMlog and found the following command getting executed with the > VR is rebooted related to ip alias: > [22250] 2013-05-23 11:13:30.654474 VMOPS enter deleteipAlias > [22250] 2013-05-23 11:13:30.654559 ['bin/bash', > '/opt/xensource/bin/deleteipAlias.sh', '169.254.3.21', '', > '18:10.147.43.132:255.255.255.192-21:10.147.43.195:255.255.255.192-'] > [22250] 2013-05-23 11:13:31.338199pread SUCCESS > [22250] 2013-05-23 11:13:31.338311 VMOPS exit deleteipAlias > IP aliases information is being passed to deleteipAlias.sh and due to which > ip alias are getting removed. -- 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-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673116#comment-13673116 ] Nicolas Lamirault commented on CLOUDSTACK-2822: --- The SQL request comes from file : ./server/src/com/cloud/upgrade/dao/Upgrade30xBase.java > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached logs. -- 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-2620) [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address in case of multiple subnets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673109#comment-13673109 ] ASF subversion and git services commented on CLOUDSTACK-2620: - Commit 0a69b828993088487876ce859e6c00e96e4b545c in branch refs/heads/master from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a69b82 ] CLOUDSTACK-2620 [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address in case of multiple subnets Signed-off-by: Abhinandan Prateek > [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address > in case of multiple subnets > - > > Key: CLOUDSTACK-2620 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2620 > 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: Build from master branch: > CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz >Reporter: Sanjeev N >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > > [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address > in case of multiple subnets > Steps to Reproduce: > > 1.Bring up CS in basic zone with Xen61 server > 2.Consume all the guest IP ranges in the existing subnet > 3.Add guest ip range in new CIDR > 4.Deploy guest vm > 5.Verify the nameserver in /etc/resolve.conf in guest vm > Expected Behaviour: > = > nameserver on guest vm should be set to ip alias address on VR > Actual Behaviour: > == > nameserver on guest vm was set to zone level internal DNS ip address instead > of VR's ip alias address. > Observations: > === > Primary ip range: 10.147.43.3-10.147.43.7 GW:10.147.43.1 Netmask: > 255.255.255.128 > New IP Range : 10.147.43.130-10.147.43.133 GW: 10.147.43.129 Netmask: > 255.255.255.192 > When the vm is deployed with IP address from the new CIDR , ip alis on VR got > created with ip address from new CIDR. > ip alias on the VR was set to 10.147.43.132 > root@r-4-VM:/etc# ifconfig > eth0 Link encap:Ethernet HWaddr 06:ba:90:00:00:0e > inet addr:10.147.43.6 Bcast:10.147.43.127 Mask:255.255.255.128 > inet6 addr: fe80::4ba:90ff:fe00:e/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:36018 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1007 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1919944 (1.8 MiB) TX bytes:46214 (45.1 KiB) > Interrupt:24 > eth0:18 Link encap:Ethernet HWaddr 06:ba:90:00:00:0e > inet addr:10.147.43.132 Bcast:10.147.43.191 Mask:255.255.255.192 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:24 > During ip alias creation process dnsmasq.conf was re-generated with new ip > range and dhcp-option was set as following: > dhcp-option=6,10.103.128.16,10.103.128.16 > dnsmasq.conf regeneration process is taking DNS values set at zone level and > replacing with the exiting values in the file. Hence guest vms are getting > internal DNS ip address as nemeserver. > Impact: > == > Since guest vms nameserver is set to an IP address other than VR's , vm to vm > communication using domain names will fail. -- 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-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2822: -- Attachment: output.log > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached logs. -- 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-2620) [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address in case of multiple subnets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673109#comment-13673109 ] ASF subversion and git services commented on CLOUDSTACK-2620: - Commit 0a69b828993088487876ce859e6c00e96e4b545c in branch refs/heads/master from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a69b82 ] CLOUDSTACK-2620 [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address in case of multiple subnets Signed-off-by: Abhinandan Prateek > [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address > in case of multiple subnets > - > > Key: CLOUDSTACK-2620 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2620 > 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: Build from master branch: > CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz >Reporter: Sanjeev N >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > > [Multiple_IP_Ranges] Guest vm's nameserver is not set to VRs guest IP address > in case of multiple subnets > Steps to Reproduce: > > 1.Bring up CS in basic zone with Xen61 server > 2.Consume all the guest IP ranges in the existing subnet > 3.Add guest ip range in new CIDR > 4.Deploy guest vm > 5.Verify the nameserver in /etc/resolve.conf in guest vm > Expected Behaviour: > = > nameserver on guest vm should be set to ip alias address on VR > Actual Behaviour: > == > nameserver on guest vm was set to zone level internal DNS ip address instead > of VR's ip alias address. > Observations: > === > Primary ip range: 10.147.43.3-10.147.43.7 GW:10.147.43.1 Netmask: > 255.255.255.128 > New IP Range : 10.147.43.130-10.147.43.133 GW: 10.147.43.129 Netmask: > 255.255.255.192 > When the vm is deployed with IP address from the new CIDR , ip alis on VR got > created with ip address from new CIDR. > ip alias on the VR was set to 10.147.43.132 > root@r-4-VM:/etc# ifconfig > eth0 Link encap:Ethernet HWaddr 06:ba:90:00:00:0e > inet addr:10.147.43.6 Bcast:10.147.43.127 Mask:255.255.255.128 > inet6 addr: fe80::4ba:90ff:fe00:e/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:36018 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1007 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1919944 (1.8 MiB) TX bytes:46214 (45.1 KiB) > Interrupt:24 > eth0:18 Link encap:Ethernet HWaddr 06:ba:90:00:00:0e > inet addr:10.147.43.132 Bcast:10.147.43.191 Mask:255.255.255.192 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:24 > During ip alias creation process dnsmasq.conf was re-generated with new ip > range and dhcp-option was set as following: > dhcp-option=6,10.103.128.16,10.103.128.16 > dnsmasq.conf regeneration process is taking DNS values set at zone level and > replacing with the exiting values in the file. Hence guest vms are getting > internal DNS ip address as nemeserver. > Impact: > == > Since guest vms nameserver is set to an IP address other than VR's , vm to vm > communication using domain names will fail. -- 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-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
Nicolas Lamirault created CLOUDSTACK-2822: - Summary: Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade Key: CLOUDSTACK-2822 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Priority: Blocker Fix For: 4.1.0 We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. See attached logs. -- 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-2820) Global parameter "network.throttling.rate" is not controlling data transfer rate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673083#comment-13673083 ] Wei Zhou commented on CLOUDSTACK-2820: -- Hi, I do not know how you set transfer rate on VR interface, so I do not know whether it is a Xenserver issue. AFAK, KVM supports setting parameters of network interfaces on a running VMs. However, CloudStack only changes the XML definition of the VMs. So you need to restart cloudstack-management server, and stop/start (not reboot) the virtual router or restart network to take changes into effective. -Wei > Global parameter "network.throttling.rate" is not controlling data transfer > rate > > > Key: CLOUDSTACK-2820 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2820 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, XenServer >Affects Versions: 4.2.0 > Environment: Hypervisor XS 6.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar > > > Virtual router's interfaces are getting QOS based on GP > "network.throttling.rate" value but in actual there is no control on data > transfer rate. > Steps to rep > --- > 1-Set GP "network.throttling.rate" to some value say 3 Mb/s;restart MS > 2-down load a file in VR > 3-copy file from vm to some location using rsunc/scp > expected > - > Transfer rate should not be more that 3Mb/s > Actual > - > i see transfer rate 15.50 MB/sec > My observation > - > I manually set transfer rate to 100KB/s on VR interface ,saw same > issue.Looks like Xenserver issue > Details > --- > root@r-3858-VM:~# rsync -avzSP acton-systemvm-02062012.vhd.bz2 > 10.147.59.200:/root/ > The authenticity of host '10.147.59.200 (10.147.59.200)' can't be established. > RSA key fingerprint is a8:2a:cb:0f:f9:3f:41:eb:b1:b5:a6:4b:59:0c:df:39. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '10.147.59.200' (RSA) to the list of known hosts. > root@10.147.59.200's password: > sending incremental file list > acton-systemvm-02062012.vhd.bz2 >140616708 100% 15.50MB/s0:00:08 (xfer#1, to-check=0/1) > sent 140664010 bytes received 31 bytes 9075099.42 bytes/sec > total size is 140616708 speedup is 1.00 -- 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-2821) [XenServer] ModifyStoragePoolCommand fails with error "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e6216
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru updated CLOUDSTACK-2821:
---
Attachment: logs.tgz
> [XenServer] ModifyStoragePoolCommand fails with error
> "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool:
> a1a1a150-6709-3d81-a414-4cee93e62168 from on
> host:0afd552a-6c99-4c50-aa58-47b817786793"
> -
>
> Key: CLOUDSTACK-2821
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2821
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: XenServer
>Affects Versions: 4.2.0
> Environment: commit # b4969c4af5264879ccbec01b65b6c94886fc79d4
>Reporter: venkata swamybabu budumuru
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have the latest CloudStack setup with at least 1 adv zone (1 cluster with
> XenServer 6.1 with all latest patches) and only system VMs in running state.
> 2. Make sure that all the system vms are in "Stopped" state and no user vms
> are created and the zone is in disabled state.
> 3. Push the XenServer host into Maintenance mode
> 4. After the host is successfully placed in maintenance, remove the host.
> 5. Add a totally different freshly installed host to the same cluster.
> Observations:-
> (i) It failed with the following error.
> 2013-06-03 13:06:00,403 DEBUG [agent.transport.Request]
> (AgentTaskPool-2:null) Seq 8-690552836: Sending { Cmd , MgmtId:
> 7280707764394, via: 8, Ver: v1, Flags: 100011,
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"a1a1a150-6709-3d81-a414-4cee93e62168","host":"10.147.28.7","path":"/export/home/swamy/primary.campo.xen.1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//a1a1a150-6709-3d81-a414-4cee93e62168","wait":0}}]
> }
> 2013-06-03 13:06:00,407 DEBUG [agent.transport.Request]
> (AgentTaskPool-2:null) Seq 8-690552836: Executing: { Cmd , MgmtId:
> 7280707764394, via: 8, Ver: v1, Flags: 100011,
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"a1a1a150-6709-3d81-a414-4cee93e62168","host":"10.147.28.7","path":"/export/home/swamy/primary.campo.xen.1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//a1a1a150-6709-3d81-a414-4cee93e62168","wait":0}}]
> }
> 2013-06-03 13:06:00,407 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-2:null) Seq 8-690552836: Executing request
> 2013-06-03 13:06:00,489 WARN [xen.resource.CitrixResourceBase]
> (DirectAgent-2:null) ModifyStoragePoolCommand add XenAPIException:Can not see
> storage pool: a1a1a150-6709-3d81-a414-4cee93e62168 from on
> host:0afd552a-6c99-4c50-aa58-47b817786793
> host:0afd552a-6c99-4c50-aa58-47b817786793 pool:
> 10.147.28.7/export/home/swamy/primary.campo.xen.1
> com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool:
> a1a1a150-6709-3d81-a414-4cee93e62168 from on
> host:0afd552a-6c99-4c50-aa58-47b817786793
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getStorageRepository(CitrixResourceBase.java:7548)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5568)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:510)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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)
> (ii) CS sent "modifyStoragePoolCmd" and it didn't fine any SR with the UUID
> of primary and it resulted in failure.
> (iii) Due to the above mentioned error, Primary s
[jira] [Created] (CLOUDSTACK-2821) [XenServer] ModifyStoragePoolCommand fails with error "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e6216
venkata swamybabu budumuru created CLOUDSTACK-2821:
--
Summary: [XenServer] ModifyStoragePoolCommand fails with error
"com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool:
a1a1a150-6709-3d81-a414-4cee93e62168 from on
host:0afd552a-6c99-4c50-aa58-47b817786793"
Key: CLOUDSTACK-2821
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2821
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: XenServer
Affects Versions: 4.2.0
Environment: commit # b4969c4af5264879ccbec01b65b6c94886fc79d4
Reporter: venkata swamybabu budumuru
Priority: Critical
Fix For: 4.2.0
Steps to reproduce:
1. Have the latest CloudStack setup with at least 1 adv zone (1 cluster with
XenServer 6.1 with all latest patches) and only system VMs in running state.
2. Make sure that all the system vms are in "Stopped" state and no user vms are
created and the zone is in disabled state.
3. Push the XenServer host into Maintenance mode
4. After the host is successfully placed in maintenance, remove the host.
5. Add a totally different freshly installed host to the same cluster.
Observations:-
(i) It failed with the following error.
2013-06-03 13:06:00,403 DEBUG [agent.transport.Request] (AgentTaskPool-2:null)
Seq 8-690552836: Sending { Cmd , MgmtId: 7280707764394, via: 8, Ver: v1,
Flags: 100011,
[{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"a1a1a150-6709-3d81-a414-4cee93e62168","host":"10.147.28.7","path":"/export/home/swamy/primary.campo.xen.1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//a1a1a150-6709-3d81-a414-4cee93e62168","wait":0}}]
}
2013-06-03 13:06:00,407 DEBUG [agent.transport.Request] (AgentTaskPool-2:null)
Seq 8-690552836: Executing: { Cmd , MgmtId: 7280707764394, via: 8, Ver: v1,
Flags: 100011,
[{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"a1a1a150-6709-3d81-a414-4cee93e62168","host":"10.147.28.7","path":"/export/home/swamy/primary.campo.xen.1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//a1a1a150-6709-3d81-a414-4cee93e62168","wait":0}}]
}
2013-06-03 13:06:00,407 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-2:null) Seq 8-690552836: Executing request
2013-06-03 13:06:00,489 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-2:null) ModifyStoragePoolCommand add XenAPIException:Can not see
storage pool: a1a1a150-6709-3d81-a414-4cee93e62168 from on
host:0afd552a-6c99-4c50-aa58-47b817786793
host:0afd552a-6c99-4c50-aa58-47b817786793 pool:
10.147.28.7/export/home/swamy/primary.campo.xen.1
com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool:
a1a1a150-6709-3d81-a414-4cee93e62168 from on
host:0afd552a-6c99-4c50-aa58-47b817786793
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getStorageRepository(CitrixResourceBase.java:7548)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5568)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:510)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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)
(ii) CS sent "modifyStoragePoolCmd" and it didn't fine any SR with the UUID of
primary and it resulted in failure.
(iii) Due to the above mentioned error, Primary storage never gets mounted and
no VMs can be started until the primary storage is completely removed from CS
and added newly.
Attaching all the required logs along with db dump to the bug.
--
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-2820) Global parameter "network.throttling.rate" is not controlling data transfer rate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2820: -- Attachment: logs.rar > Global parameter "network.throttling.rate" is not controlling data transfer > rate > > > Key: CLOUDSTACK-2820 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2820 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, XenServer >Affects Versions: 4.2.0 > Environment: Hypervisor XS 6.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar > > > Virtual router's interfaces are getting QOS based on GP > "network.throttling.rate" value but in actual there is no control on data > transfer rate. > Steps to rep > --- > 1-Set GP "network.throttling.rate" to some value say 3 Mb/s;restart MS > 2-down load a file in VR > 3-copy file from vm to some location using rsunc/scp > expected > - > Transfer rate should not be more that 3Mb/s > Actual > - > i see transfer rate 15.50 MB/sec > My observation > - > I manually set transfer rate to 100KB/s on VR interface ,saw same > issue.Looks like Xenserver issue > Details > --- > root@r-3858-VM:~# rsync -avzSP acton-systemvm-02062012.vhd.bz2 > 10.147.59.200:/root/ > The authenticity of host '10.147.59.200 (10.147.59.200)' can't be established. > RSA key fingerprint is a8:2a:cb:0f:f9:3f:41:eb:b1:b5:a6:4b:59:0c:df:39. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '10.147.59.200' (RSA) to the list of known hosts. > root@10.147.59.200's password: > sending incremental file list > acton-systemvm-02062012.vhd.bz2 >140616708 100% 15.50MB/s0:00:08 (xfer#1, to-check=0/1) > sent 140664010 bytes received 31 bytes 9075099.42 bytes/sec > total size is 140616708 speedup is 1.00 -- 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-2780) primary storage is already mounted but not found in pool-list
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou resolved CLOUDSTACK-2780.
--
Resolution: Won't Fix
This issue relates to a known issue of libvirt which has been fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=878400
> primary storage is already mounted but not found in pool-list
> -
>
> Key: CLOUDSTACK-2780
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2780
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.0.1
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>Priority: Critical
>
> This issue appeared on our testing enviroment with cloudstack 4.0.1 (Ubuntu
> 12.04) , and product platform as well.
> (only on few hosts, most of hosts work well)
> We got the message "Unable to create volume" when deploy a VM.
> (1) In management-server.log
> 2013-05-30 14:36:20,090 DEBUG [agent.transport.Request]
> (AgentManager-Handler-11:null) Seq 3-2021457981: Processing: { Ans: ,
> MgmtId: 345051509349, via: 3, Ver: v1, Flags: 110,
> [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
> com.cloud.utils.exception.CloudRuntimeException\nMessage:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\nStack: com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:394)\n\tat
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:48)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1212)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1031)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:518)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:831)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
> java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
> 2013-05-30 14:36:20,090 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-11:null) Seq 3-2021457981: No more commands found
> 2013-05-30 14:36:20,090 DEBUG [agent.transport.Request]
> (Job-Executor-5:job-2563) Seq 3-2021457981: Received: { Ans: , MgmtId:
> 345051509349, via: 3, Ver: v1, Flags: 110, { CreateAnswer } }
> 2013-05-30 14:36:20,090 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-5:job-2563) Unable to create volume Vol[750|vm=550|ROOT]
> 2013-05-30 14:36:20,095 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-5:job-2563) Unable to contact resource.
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200]
> is unreachable: Unable to create Vol[750|vm=550|ROOT]
> (2) In the host Primary storage is already mounted (just an example):
> [root@cs-kvm015 /]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/mapper/vg0-root 461410320 2592404 435379580 1% /
> tmpfs 8160712 0 8160712 0% /dev/shm
> /dev/sda1 198337 52765135332 29% /boot
> /dev/mapper/vg0-tmp2064208 68648 1890704 4% /tmp
> 192.168.103.1:/storage/cs4x-primary
> 7811748864 466487296 7345261568 6%
> /mnt/7b88eced-fc54-3c9f-808a-a697d6be667c
> But not in libvirt pool list
> [root@cs-kvm015 ~]# virsh pool-list
> Name State Autostart
> -
> 513ae20a-61f9-4f7a-b485-23ddb29e59ae active no
> 7b88eced-fc54-3c9f-808a-a697d6be667c active no
> (should have this line, but have not)
> (3) Workaround:
> Enable Maintenance Mode
> umount /mnt/7b88eced-fc54-3c9f-808a-a697d6be667c
> service cloud-agent restart
--
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-2820) Global parameter "network.throttling.rate" is not controlling data transfer rate
prashant kumar mishra created CLOUDSTACK-2820: - Summary: Global parameter "network.throttling.rate" is not controlling data transfer rate Key: CLOUDSTACK-2820 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2820 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.2.0 Environment: Hypervisor XS 6.1 Reporter: prashant kumar mishra Fix For: 4.2.0 Virtual router's interfaces are getting QOS based on GP "network.throttling.rate" value but in actual there is no control on data transfer rate. Steps to rep --- 1-Set GP "network.throttling.rate" to some value say 3 Mb/s;restart MS 2-down load a file in VR 3-copy file from vm to some location using rsunc/scp expected - Transfer rate should not be more that 3Mb/s Actual - i see transfer rate 15.50 MB/sec My observation - I manually set transfer rate to 100KB/s on VR interface ,saw same issue.Looks like Xenserver issue Details --- root@r-3858-VM:~# rsync -avzSP acton-systemvm-02062012.vhd.bz2 10.147.59.200:/root/ The authenticity of host '10.147.59.200 (10.147.59.200)' can't be established. RSA key fingerprint is a8:2a:cb:0f:f9:3f:41:eb:b1:b5:a6:4b:59:0c:df:39. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.147.59.200' (RSA) to the list of known hosts. root@10.147.59.200's password: sending incremental file list acton-systemvm-02062012.vhd.bz2 140616708 100% 15.50MB/s0:00:08 (xfer#1, to-check=0/1) sent 140664010 bytes received 31 bytes 9075099.42 bytes/sec total size is 140616708 speedup is 1.00 -- 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
