[jira] [Commented] (CLOUDSTACK-3204) Dashboard deleted alert remains and causes popup error on quickview hover.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693687#comment-13693687 ] Thomas O'Dowd commented on CLOUDSTACK-3204: --- I tried to repeat this again (without restarting anything or updating anything) and the issue didn't happen this time... The alerts were deleted. Just checked terminal of management server... I'm not sure if its related or not but am seeing: ERROR [cloud.server.StatsCollector] (StatsCollector-3:) Error trying to retrieve storage stats java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:691) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) at java.util.concurrent.ThreadPoolExecutor.ensurePrestart(ThreadPoolExecutor.java:1590) at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:333) at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:530) at java.util.concurrent.ScheduledThreadPoolExecutor.execute(ScheduledThreadPoolExecutor.java:619) at com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:97) at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:364) at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:388) at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:483) at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:436) at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:965) at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:432) at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:446) at com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:559) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Exception in thread "DirectAgent-249" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:691) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) at java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1017) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1163) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) ERROR [cloud.server.StatsCollector] (StatsCollector-3:) Error trying to retrieve storage stats java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:691) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) at java.util.concurrent.ThreadPoolExecutor.ensurePrestart(ThreadPoolExecutor.java:1590) at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:333) at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:530) at java.util.concurrent.ScheduledThreadPoolExecutor.execute(ScheduledThreadPoolExecutor.java:619) at com.cloud.agent.manager.DirectAgentAttache.send(DirectAgentAttache.java:97) at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:364) at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:388) at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:483) at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:436) at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:965) at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:432) at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:446) at com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:559) at java.util.concurrent.E
[jira] [Created] (CLOUDSTACK-3204) Dashboard deleted alert remains and causes popup error on quickview hover.
Thomas O'Dowd created CLOUDSTACK-3204: - Summary: Dashboard deleted alert remains and causes popup error on quickview hover. Key: CLOUDSTACK-3204 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3204 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Environment: Chrome on Linux Reporter: Thomas O'Dowd Latest master branch developer build when running devcloud. 1. Browse to dashboard. 2. View Alerts 3. select quickview on an alert (I did this on usage server not running alert). 4. select delete on that alert from the quickview popup. 5. alert remains on list 6. hover over that alerts quickview again. result is a popup error. "Unable to execute API command listalerts due to invalid value. Invalid parameter id value=f878d88c-8ac0-4c99-b54f-90d4e9809958 due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class." Expected result would be that after step 4, the alert is removed from the alert 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] [Closed] (CLOUDSTACK-2974) Exception org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] terryye closed CLOUDSTACK-2974. --- Resolution: Won't Fix > Exception org.libvirt.LibvirtException: internal error unknown timer name > 'kvmclock' > -- > > Key: CLOUDSTACK-2974 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2974 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM >Affects Versions: 4.1.0 > Environment: Ubuntu 12.04 >Reporter: terryye > Labels: agent, deb, error, kvm, kvmclock > Original Estimate: 72h > Remaining Estimate: 72h > > 2013-06-13 10:03:02,538 INFO [cloud.agent.Agent] > (agentRequest-Handler-2:null) Ready command is processed: agent id = 5 > 2013-06-13 10:03:19,519 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-1:null) Exception > org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock' > at org.libvirt.ErrorHandler.processError(Unknown Source) > at org.libvirt.Connect.processError(Unknown Source) > at org.libvirt.Connect.domainCreateXML(Unknown Source) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:986) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3114) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1102) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-06-13 10:03:30,947 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) Exception > org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock' > at org.libvirt.ErrorHandler.processError(Unknown Source) > at org.libvirt.Connect.processError(Unknown Source) > at org.libvirt.Connect.domainCreateXML(Unknown Source) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:986) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3114) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1102) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-06-13 10:03:49,387 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) Exception > org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock' > at org.libvirt.ErrorHandler.processError(Unknown Source) > at org.libvirt.Connect.processError(Unknown Source) > at org.libvirt.Connect.domainCreateXML(Unknown Source) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:986) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3114) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1102) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-06-13 10:04:00,759 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Exception > org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock' > at org.libvirt.ErrorHandler.processError(Unknown Source) > at org.libvirt.Connect.processError(Unknown Source) > at org.libvirt.Con
[jira] [Updated] (CLOUDSTACK-2980) Adding a VLAN range that overlaps with two existing ranges results in inconsistent DB entries
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-2980: - Assignee: Bharat Kumar > Adding a VLAN range that overlaps with two existing ranges results in > inconsistent DB entries > - > > Key: CLOUDSTACK-2980 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2980 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > Under PhysicalNetwork - Guest, Add 2 VLAN ranges - 360-369;380-385 > Then adding one new VLAN range, 367-383 results in the following 2 issues, > 1. The new range displayed in the UI is 360-383;380-385 > 2. In the DB 'op_dc_vnet_alloc' table every VLAN in the range 370-379 is > missing. This is because we are trying to add VLANs from 370-383 and since > the entries 380-383 are duplicates the DB insert throws an exception. -- 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-3109) NPE while deleting the vlan IP Range of the shared network.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar updated CLOUDSTACK-3109:
-
Assignee: Bharat Kumar
> NPE while deleting the vlan IP Range of the shared network.
> ---
>
> Key: CLOUDSTACK-3109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3109
> 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
>Assignee: Bharat Kumar
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps:
> 1.Have a CS with advanced zone.
> 2.Create a Shared guest network.(Infrastructure->Zone->physical
> N/W->Guest N/w->add N/w)
> 3.Assign the shared network to some VM.
> 4.Now try to delete the vlan IP range of the shared network.
> (Infrastructure->Zone->physical N/W->Guest N/w-> ->view
> Ip range).
> Observation:
> Observed NPE while deleting the Vlan IP range.Observed this only when the
> created shared network is assigned to some VM.
> User should be prompted that the IP range is in use and cannot be deleted.
> 2013-06-21 16:54:10,390 ERROR [cloud.api.ApiServer] (catalina-exec-6:null)
> unhandled exception executing api command: deleteVlanIpRange
> java.lang.NullPointerException
> at
> com.cloud.configuration.ConfigurationManagerImpl.deleteVlanAndPublicIpRange(ConfigurationManagerImpl.java:3008)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.configuration.ConfigurationManagerImpl.deleteVlanIpRange(ConfigurationManagerImpl.java:3533)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.vlan.DeleteVlanIpRangeCmd.execute(DeleteVlanIpRangeCmd.java:69)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-06-21 16:54:10,394 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null)
> ===END=== 10.252.192.69 -- GET
> command=deleteVlanIpRange&id=39b0cd6d-b2e6-4518-9a6b-11d9188de0ff&response=json&sessionkey=fEUYFA7%2B5eZOpYyC0OVDvHQ%2FjlE%3D&_=1371794398171
> 2013-06-21 16:54:11,004 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-5:null) SeqA 3-19101: Processing Seq 3-19101: { Cmd ,
> MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
--
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-3186) Duplicate entries in /etc/hosts file on VR after reboot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3186: - Assignee: Bharat Kumar > Duplicate entries in /etc/hosts file on VR after reboot > --- > > Key: CLOUDSTACK-3186 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3186 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 > Environment: Latest build from master6-17-statble branch >Reporter: Sanjeev N >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > /etc/hosts file on VR contains the IP address to Host Name mappings. > In 4.2 we have introduced a new entry called "data-server" and mapped to > Router VMs eth0 interface ip address. This is for the guest vms to access > user-data and ssh-keys from the Router VM. > Please refer to bug https://issues.apache.org/jira/browse/CLOUDSTACK-2644 for > more info. > Making this entry in the hosts file is part of cloud-early-config file and > every time a router is rebooted new entry would be made to the hosts file. > If the router reboots multiple times for some reason, we see lot of duplicate > entries in the hosts file. > Following is the contents from /etc/hosts file from VR which was rebooted for > multiple times: > 127.0.0.1 localhost > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > 10.147.43.6 data-server > 10.147.43.6 r-4-VM > 10.147.43.6 data-server > 10.147.43.6 r-4-VM > 10.147.43.6 data-server > 10.147.43.6 r-4-VM > 10.147.43.5 s1 > 10.147.43.7 s1-passwd > 10.147.43.10 addaf9b0-bdbc-4c4a-80ed-67664ad781e0 > 10.147.43.8 3b2804dd-225d-4cf3-bcdc-fed468c61192 > 10.147.43.130 s2 > 10.147.43.132 0e0df8e6-2c0f-455b-8571-b5f6a0dbd44e > 10.147.43.133 s2-passwd > 10.147.43.134 bf2e0e55-a2c9-4d26-a489-b8d8aa596350 > It would be good to check for the entries present in the file before > appending to it and avoid duplicate entries. -- 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-3192) [Dedicated Resources][Public IP addresses per tenant] Usage Event : NET.IPRELEASE is generated even for IPs which are in use
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-3192. Resolution: Fixed > [Dedicated Resources][Public IP addresses per tenant] Usage Event : > NET.IPRELEASE is generated even for IPs which are in use > > > Key: CLOUDSTACK-3192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3192 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Steps : > == > 1. Add an IP range IP1 to IP10 in Public IP range. > 2. Dedicated this range to an account. > 3. Create a network in that account and acquire IPs. > 4. Suppose IPs acquired are IP1, IP2 and IP3 then create a LB rule on IP1 and > leave the other two as it is > 5. Release the IP range from dedication to that account > Expected Behaviour : > == > 1. After step 3 a usage event NET.IPASSIGN should be generated for IP1, IP2, > IP3 > 2. After step 5 a usage event NET.IPRELEASE should be generated only for IP2 > and IP3, not for IP1 as it is still in use. > Observed Behaviour: > = > After step 5 a usage event NET.IPRELEASE is generated for IP1 also, which is > not the expected behaviour. -- 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-3192) [Dedicated Resources][Public IP addresses per tenant] Usage Event : NET.IPRELEASE is generated even for IPs which are in use
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693655#comment-13693655 ] ASF subversion and git services commented on CLOUDSTACK-3192: - Commit bc8cd34662dee1902c1be5afdc63704a7ef01195 in branch refs/heads/master-6-17-stable from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bc8cd34 ] CLOUDSTACK-3192. When a dedicated public ip range is released, don't generate usage event EVENT_NET_IP_RELEASE for ips in the range that are in use becauase these ips are not disassociated from the account. > [Dedicated Resources][Public IP addresses per tenant] Usage Event : > NET.IPRELEASE is generated even for IPs which are in use > > > Key: CLOUDSTACK-3192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3192 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Steps : > == > 1. Add an IP range IP1 to IP10 in Public IP range. > 2. Dedicated this range to an account. > 3. Create a network in that account and acquire IPs. > 4. Suppose IPs acquired are IP1, IP2 and IP3 then create a LB rule on IP1 and > leave the other two as it is > 5. Release the IP range from dedication to that account > Expected Behaviour : > == > 1. After step 3 a usage event NET.IPASSIGN should be generated for IP1, IP2, > IP3 > 2. After step 5 a usage event NET.IPRELEASE should be generated only for IP2 > and IP3, not for IP1 as it is still in use. > Observed Behaviour: > = > After step 5 a usage event NET.IPRELEASE is generated for IP1 also, which is > not the expected behaviour. -- 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-2561) add new tier dialog in VPC network does not show networkofferings for which specify vlan=true is set
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal closed CLOUDSTACK-2561. -- Closing it as it is fixed now > add new tier dialog in VPC network does not show networkofferings for which > specify vlan=true is set > > > Key: CLOUDSTACK-2561 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2561 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: build: > CloudStack-non-OSS-MASTER-329-rhel6.3 >Reporter: shweta agarwal > Fix For: 4.2.0 > > > Repro steps > 1.Create a VPC network offering whose specify VLAN=true set > 2. Create a VPC network > 3. Goto VPC network and configure it by creating its on tier > Notice network offeirng dropdown is not displaying network offering created > in step 1 > Currently there is only one api call with specifyVlan=false > http://10.147.59.212:8080/client/api?command=listNetworkOfferings&response=json&sessionkey=wAjvas%2BNOtp9t4Nx6QCK8DqZGcE%3D&forvpc=true&guestiptype=Isolated&supportedServices=SourceNat&specifyvlan=false&state=Enabled&_=1368788839564 > We need to have one more api call with specifyVlan=true. > And if user selects this network offerings we need to even show vlanid text > field for user to specify the vlanid for the network -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2561) add new tier dialog in VPC network does not show networkofferings for which specify vlan=true is set
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal resolved CLOUDSTACK-2561. Resolution: Fixed fixed with other UI fixes > add new tier dialog in VPC network does not show networkofferings for which > specify vlan=true is set > > > Key: CLOUDSTACK-2561 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2561 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: build: > CloudStack-non-OSS-MASTER-329-rhel6.3 >Reporter: shweta agarwal > Fix For: 4.2.0 > > > Repro steps > 1.Create a VPC network offering whose specify VLAN=true set > 2. Create a VPC network > 3. Goto VPC network and configure it by creating its on tier > Notice network offeirng dropdown is not displaying network offering created > in step 1 > Currently there is only one api call with specifyVlan=false > http://10.147.59.212:8080/client/api?command=listNetworkOfferings&response=json&sessionkey=wAjvas%2BNOtp9t4Nx6QCK8DqZGcE%3D&forvpc=true&guestiptype=Isolated&supportedServices=SourceNat&specifyvlan=false&state=Enabled&_=1368788839564 > We need to have one more api call with specifyVlan=true. > And if user selects this network offerings we need to even show vlanid text > field for user to specify the vlanid for the network -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3192) [Dedicated Resources][Public IP addresses per tenant] Usage Event : NET.IPRELEASE is generated even for IPs which are in use
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693653#comment-13693653 ] ASF subversion and git services commented on CLOUDSTACK-3192: - Commit 8a1fefc7aa9290c654859b58f85682126eb7c36a in branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8a1fefc ] CLOUDSTACK-3192. When a dedicated public ip range is released, don't generate usage event EVENT_NET_IP_RELEASE for ips in the range that are in use becauase these ips are not disassociated from the account. > [Dedicated Resources][Public IP addresses per tenant] Usage Event : > NET.IPRELEASE is generated even for IPs which are in use > > > Key: CLOUDSTACK-3192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3192 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Steps : > == > 1. Add an IP range IP1 to IP10 in Public IP range. > 2. Dedicated this range to an account. > 3. Create a network in that account and acquire IPs. > 4. Suppose IPs acquired are IP1, IP2 and IP3 then create a LB rule on IP1 and > leave the other two as it is > 5. Release the IP range from dedication to that account > Expected Behaviour : > == > 1. After step 3 a usage event NET.IPASSIGN should be generated for IP1, IP2, > IP3 > 2. After step 5 a usage event NET.IPRELEASE should be generated only for IP2 > and IP3, not for IP1 as it is still in use. > Observed Behaviour: > = > After step 5 a usage event NET.IPRELEASE is generated for IP1 also, which is > not the expected behaviour. -- 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-3003) [VPC][VMware]Unexpected exception while applying a static route in vpc.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-3003. --- Resolution: Fixed > [VPC][VMware]Unexpected exception while applying a static route in vpc. > --- > > Key: CLOUDSTACK-3003 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3003 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: latest master build >Reporter: manasaveloori >Assignee: Jayapal Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Steps: > 1.Have a CS with advanced zone. > 2.Create a VPC. > 3.Create a private gateway to VPC . > 4.Apply a static route for private gateway . > Observation: > Applying the static route in vpc is failing with following exception: > 2013-06-14 18:16:21,883 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-33:job-29) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to apply static > routes in vpc [VPC [1-vpc1] > at > com.cloud.network.element.VpcVirtualRouterElement.applyStaticRoutes(VpcVirtualRouterElement.java:441) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1655) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1618) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1603) > at > com.cloud.network.vpc.VpcManagerImpl.revokeStaticRoute(VpcManagerImpl.java:1680) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd.execute(CreateStaticRouteCmd.java:108) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-14 18:16:21,885 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-33:job-29) Complete async job-29, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Failed to apply static routes in vpc > [VPC [1-vpc1] > Attached is the management server log. -- 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-3137) systemvms HA fails on latest master (4591f94)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693634#comment-13693634
]
Hiroaki Kawai commented on CLOUDSTACK-3137:
---
Ah, ok. CheckOnAgentInvestigator#isVmAlive is failing because XenServer is
"Disconnected" because of management server restart. I don't have an idea of
good solution for this right now.
> systemvms HA fails on latest master (4591f94)
> -
>
> Key: CLOUDSTACK-3137
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3137
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Prasanna Santhanam
>Priority: Blocker
> Attachments: logs.tar.bz2
>
>
> SystemVMs fail to start during HA on latest master
> (4591f94a0bb69875dca769c9738998d3b5b96106)
> It looks like the HA of system VMs is failing. On our automated test
> environment we reboot the management server before the systemVMs spin up to
> ensure that the global settings are affected and the configuration for the
> secstorage.internal.sites is rightly set in the secondary storage VM. The
> management server upon reboot discovers that SSVM was put to perform HA in
> the op_ha_work table and starts to re-spin the SSVM. At this time the CPVM is
> also booting up. No further activity is observed after two HA attempts.
> SystemVM start before Management server start:
> Jun 24 22:30:49 cloudstack-centos63 local0: 2013-06-25 05:30:49,738 DEBUG
> [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Allocating entries
> for VM: VM[SecondaryStorageVm|s-1-VM]
> Jun 24 22:30:49 cloudstack-centos63 local0: 2013-06-25 05:30:49,771 DEBUG
> [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Allocating nics for
> VM[SecondaryStorageVm|s-1-VM]
> Jun 24 22:30:49 cloudstack-centos63 local0: 2013-06-25 05:30:49,774 DEBUG
> [cloud.network.NetworkManagerImpl] (secstorage-1:null) Allocating nic for vm
> VM[SecondaryStorageVm|s-1-VM] in network Ntwk[200|Public|1] with requested
> profile NicProfile[0-0-null-null-null
> Jun 24 22:30:49 cloudstack-centos63 local0: 2013-06-25 05:30:49,843 DEBUG
> [cloud.network.NetworkManagerImpl] (secstorage-1:null) Allocating nic for vm
> VM[SecondaryStorageVm|s-1-VM] in network Ntwk[202|Control|3] with requested
> profile null
> Jun 24 22:30:49 cloudstack-centos63 local0: 2013-06-25 05:30:49,870 DEBUG
> [cloud.network.NetworkManagerImpl] (secstorage-1:null) Allocating nic for vm
> VM[SecondaryStorageVm|s-1-VM] in network Ntwk[201|Management|2] with
> requested profile null
> Jun 24 22:30:49 cloudstack-centos63 local0: 2013-06-25 05:30:49,916 DEBUG
> [cloud.network.NetworkManagerImpl] (secstorage-1:null) Allocating nic for vm
> VM[SecondaryStorageVm|s-1-VM] in network Ntwk[203|Storage|4] with requested
> profile null
> ...
> ...
> Jun 24 22:30:52 cloudstack-centos63 local0: 2013-06-25 05:30:52,552 DEBUG
> [agent.transport.Request] (consoleproxy-1:null) Seq 3-2067660811: Sending {
> Cmd , MgmtId: 200973787296321, via: 3, Ver: v1, Flags: 100111,
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/1/","origUrl":"http://nfs/templates/acton/acton-systemvm-02062012.vhd.bz2","uuid":"1","id":1,"format":"VHD","accountId":1,"checksum":"f613f38c96bf039f2e5cbf92fa8ad4f8","hvm":false,"displayText":"SystemVM
> Template
> (XenServer)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://nfs.fmt.vmops.com:/expo...
> Jun 24 22:31:01 cloudstack-centos63 local0: 2013-06-25 05:31:01,824 INFO
> [context.support.XmlWebApplicationContext] (Thread-26:null) Closing Root
> WebApplicationContext: startup date [Mon Jun 24 23:25:50 UTC 2013]; root of
> context hierarchy
> ^^ Management Server Restarts ^^
> After restart SSVM scheduled for HA
> Jun 24 22:32:52 cloudstack-centos63 local0: 2013-06-25 05:32:52,394 INFO
> [cloud.ha.HighAvailabilityManagerImpl] (Timer-1:null) Schedule vm for HA:
> VM[SecondaryStorageVm|s-1-VM]
> Jun 24 22:32:52 cloudstack-centos63 local0: 2013-06-25 05:32:52,455 INFO
> [cloud.vm.VirtualMachineManagerImpl] (Timer-1:null) Handling unfinished work
> item: ItWork[1805a89b-d03a-4f1f-b717-ac9f5da6edea-Starting-2-Prepare]
> Jun 24 22:32:52 cloudstack-centos63 local0: 2013-06-25 05:32:52,504 INFO
> [cloud.ha.HighAvailabilityManagerImpl] (Timer-1:null) Schedule vm for HA:
> VM[ConsoleProxy|v-2-VM]
> ...
> Jun 24 22:32:52 cloudstack-centos63 local0: 2013-06-25 05:32:52,540 INFO
> [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:null) Starting work
> Jun 24 22:32:52 cloudstack-centos63 local0: 2013-06-25 05:32:52,547 INFO
> [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-1:null) Starting wo
[jira] [Assigned] (CLOUDSTACK-2141) During HA process , dead lock is detected - Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when trying to get lock; t
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-2141:
--
Assignee: Koushik Das
> During HA process , dead lock is detected - Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock
> found when trying to get lock; try restarting transaction"
> --
>
> Key: CLOUDSTACK-2141
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2141
> 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
>Reporter: Sangeetha Hariharan
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> During HA process , dead lock is detected - Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock
> found when trying to get lock; try restarting transaction"
> Following are the steps that was followed:
> Set up - Advanced zone with 3 hosts in a cluster.
> One of the host is already shutdown.
> Shutdown another Host that has Vms that is ha enabled ( vm in my case
> "anan-ha1")
> As part of performing HA on this Vm , I see couple of exceptions being thrown:
> 2013-04-22 14:59:05,738 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (HA-Worker-0:work-52) Failed to start instance VM[User|anan-ha1]
> com.cloud.exception.ConcurrentOperationException: Work steps have been
> changed: ItWork[69587fc9-2bd1-4183-b89c-216ecdf3be5a-Starting-54-Done]
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:770)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:592)
> at
> com.cloud.ha.HighAvailabilityManagerImpl.restart(HighAvailabilityManagerImpl.java:533)
> at
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:831)
> 2013-04-22 14:59:05,743 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (HA-Worker-0:work-52) Cleaning up resources for the vm VM[User|anan-ha1] in
> Starting state
>
> 2013-04-22 15:00:15,615 WARN [agent.manager.DirectAgentAttache]
> (DirectAgent-317:null) Seq 8-1217527861: Exception Caught while executing
> command
> com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
> slave 10.223.59.3 to 10.223.59.2 due to
> com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
> slave 10.223.59.3 to 10.223.59.2after 30 retry
> at
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
> at
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2286)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:518)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> 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:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-22 15:00:15,616 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-317:null) Seq 8-1217527861: Response Received:
> 2013-04-22 15:00:15,616 DEBUG [agent.transport.Request]
> (DirectAgent-317:null) Seq 8-1217527861: Processing: { Ans: , MgmtId:
> 7508777239729, via: 8, Ver: v1, Flags: 10,
> [{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> Unable to reset master of slave 10.223.5
[jira] [Created] (CLOUDSTACK-3203) Server-side cloudformation service
Dharmesh Kakadia created CLOUDSTACK-3203: Summary: Server-side cloudformation service Key: CLOUDSTACK-3203 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3203 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Dharmesh Kakadia Assignee: Dharmesh Kakadia -- 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-3201) Mesos bash script to install and configure mesos cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dharmesh Kakadia reassigned CLOUDSTACK-3201: Assignee: Dharmesh Kakadia > Mesos bash script to install and configure mesos cluster > > > Key: CLOUDSTACK-3201 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3201 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Dharmesh Kakadia >Assignee: Dharmesh Kakadia > -- 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-3202) Mesos cloudformation template to work with stackmate
Dharmesh Kakadia created CLOUDSTACK-3202: Summary: Mesos cloudformation template to work with stackmate Key: CLOUDSTACK-3202 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3202 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Dharmesh Kakadia -- 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-3202) Mesos cloudformation template to work with stackmate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dharmesh Kakadia reassigned CLOUDSTACK-3202: Assignee: Dharmesh Kakadia > Mesos cloudformation template to work with stackmate > > > Key: CLOUDSTACK-3202 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3202 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Dharmesh Kakadia >Assignee: Dharmesh Kakadia > -- 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-3201) Mesos bash script to install and configure mesos cluster
Dharmesh Kakadia created CLOUDSTACK-3201: Summary: Mesos bash script to install and configure mesos cluster Key: CLOUDSTACK-3201 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3201 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Dharmesh Kakadia -- 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-212) Switch java package structure from com.cloud to org.apache
[ https://issues.apache.org/jira/browse/CLOUDSTACK-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693611#comment-13693611 ] Dharmesh Kakadia commented on CLOUDSTACK-212: - [~animeshc] Yes. I am waiting for code freeze, otherwise merging the new code might be difficult. Suggestions ? > Switch java package structure from com.cloud to org.apache > -- > > Key: CLOUDSTACK-212 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-212 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: pre-4.0.0 >Reporter: Chip Childers >Assignee: Dharmesh Kakadia >Priority: Minor > Fix For: 4.2.0 > > > Since the project has moved over to ASF, I'd like to suggest that we move > from com.cloud to org.apache for the java package structure of our modules. > If there is agreement, we can take this up after 4.0 is out the door. -- 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-3194) Management server startup fails with SSPCredentialDao Injection
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693605#comment-13693605 ] ASF subversion and git services commented on CLOUDSTACK-3194: - Commit 39ef9240e87234afc2d4ddb37beaa63fe3240e4a in branch refs/heads/master from [~kawai] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=39ef924 ] CLOUDSTACK-3194 fix stratosphere ssp plugin packaging stratosphere-ssp plugin maven pom.xml has some bad settings and client pom.xml requred dependency for it. > Management server startup fails with SSPCredentialDao Injection > --- > > Key: CLOUDSTACK-3194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Prasanna Santhanam >Priority: Blocker > > com.cloud.network.dao.SspCredentialDaoImpl > rocessor,affinityProcessors,DedicatedResourceManagerImpl,ExplicitDedicationProcessor,org.springframework.context.annotation.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0]; > root of factory hierarchy > 2013-06-25 13:27:34,157 ERROR [web.context.ContextLoader] (main:null) Context > initialization failed > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'actionEventUtils': Injection of autowired dependencies failed; > nested exception is org.springframework.beans.factory.BeanCreationException: > Could no > t autowire field: com.cloud.event.dao.EventDao > com.cloud.event.ActionEventUtils.eventDao; nested exception is > org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find > class [com.cloud.network.dao.SspCredentialDaoImpl] > for bean with name 'sspCredentialDaoImpl' defined in class path resource > [componentContext.xml]; nested exception is java.lang.ClassNotFoundException: > com.cloud.network.dao.SspCredentialDaoImpl > at > org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:287) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1106) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469) > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383) > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4467) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) > at > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) > at > org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) > at
[jira] [Created] (CLOUDSTACK-3200) HA tag can not work on the basic network
terryye created CLOUDSTACK-3200: --- Summary: HA tag can not work on the basic network Key: CLOUDSTACK-3200 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3200 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM, Management Server, Network Controller Affects Versions: 4.1.0 Environment: Ubuntu1204 nfs Reporter: terryye I am set the ha.tag. All hosttag and computer offerings 'tag be set the ha.tag. cpvm\ssvm and v-route be created with this tag. one network offering was created using to create basic network zone. When i created zone. the cpvm and ssvm can change service and start. but the Virtual Routers can not start. because using the system default network offering. and can not changed. -- 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-3199) NTier: Adding New Network ACL Rule Items in a Network ACL Container doesnt apply the rules to the Private Gateway on the VPC Virtual Router
Chandan Purushothama created CLOUDSTACK-3199: Summary: NTier: Adding New Network ACL Rule Items in a Network ACL Container doesnt apply the rules to the Private Gateway on the VPC Virtual Router Key: CLOUDSTACK-3199 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3199 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: Chandan Purushothama Priority: Blocker Fix For: 4.2.0 Observe from the Information given below that the Newly added Network ACL Items are getting applied to the Guest Network Tier but are not applied to the Private Gateway present on the Virtual Router. Both the network tier and the private gateway use the same Network ACL Container. == On VPC Virtual Router: == root@r-3-NTIERAGN:~# iptables-save | grep ACL :ACL_OUTBOUND_eth2 - [0:0] :ACL_OUTBOUND_eth3 - [0:0] -A PREROUTING -i eth3 -m state --state NEW -j ACL_OUTBOUND_eth3 -A PREROUTING -s 192.168.11.0/24 ! -d 192.168.11.1/32 -i eth2 -m state --state NEW -j ACL_OUTBOUND_eth2 -A ACL_OUTBOUND_eth2 -j ACCEPT -A ACL_OUTBOUND_eth3 -j ACCEPT :ACL_INBOUND_eth2 - [0:0] :ACL_INBOUND_eth3 - [0:0] -A FORWARD -o eth3 -j ACL_INBOUND_eth3 -A FORWARD -d 192.168.11.0/24 -o eth2 -j ACL_INBOUND_eth2 -A ACL_INBOUND_eth2 -s 10.223.131.172/32 -p tcp -m tcp --dport 20:40 -j ACCEPT -A ACL_INBOUND_eth2 -s 10.223.131.172/32 -p tcp -m tcp --dport 20:40 -j DROP -A ACL_INBOUND_eth2 -s 10.223.131.0/24 -p tcp -m tcp --dport 45:85 -j ACCEPT -A ACL_INBOUND_eth2 -s 10.223.195.103/32 -p tcp -m tcp --dport 21:51 -j DROP -A ACL_INBOUND_eth2 -s 10.216.133.50/32 -p tcp -m tcp --dport 50:99 -j ACCEPT -A ACL_INBOUND_eth2 -s 10.223.131.192/26 -p tcp -m tcp --dport 105:145 -j DROP -A ACL_INBOUND_eth2 -j DROP -A ACL_INBOUND_eth3 -s 10.223.131.172/32 -p tcp -m tcp --dport 20:40 -j ACCEPT -A ACL_INBOUND_eth3 -s 10.223.195.103/32 -p tcp -m tcp --dport 21:51 -j DROP -A ACL_INBOUND_eth3 -j DROP root@r-3-NTIERAGN:~# root@r-3-NTIERAGN:~# ifconfig eth2 | grep Bcast inet addr:192.168.11.1 Bcast:192.168.11.255 Mask:255.255.255.0 root@r-3-NTIERAGN:~# ifconfig eth3 | grep Bcast inet addr:10.223.57.160 Bcast:10.223.57.191 Mask:255.255.255.192 == On the Database: == mysql> select * from vpc_gateways where id=2 \G *** 1. row *** id: 2 uuid: cf8e69db-620c-4b61-a1d3-4f595b6c6050 ip4_address: 10.223.57.160 netmask: 255.255.255.192 gateway: 10.223.57.129 vlan_tag: 572 type: Private network_id: 210 vpc_id: 1 zone_id: 1 created: 2013-06-24 23:06:20 account_id: 3 domain_id: 1 state: Ready removed: NULL source_nat: 1 network_acl_id: 4 1 row in set (0.00 sec) mysql> select * from networks where id in (208,210); +-++--++--+---+---+---+--++-+-++--+-+-+---++--+--+---++--++--++--+-+-+---++-+--+--+-++ | id | name | uuid | display_text | traffic_type | broadcast_domain_type | broadcast_uri | gateway | cidr | mode | network_offering_id | physical_network_id | data_center_id | guru_name| state | related | domain_id | account_id | dns1 | dns2 | guru_data | set_fields | acl_type | network_domain | reservation_id | guest_type | restart_required | created | removed | specify_ip_ranges | vpc_id | ip6_gateway | ip6_cidr | network_cidr | display_network | network_acl_id | +-++--++--+---+---+---+--++-+-++--+-+-+---++--+--+---++--++--++--+-+-+---++-+--+--+
[jira] [Assigned] (CLOUDSTACK-3127) UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is repeating twice
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-3127: Assignee: Jessica Wang > UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is > repeating twice > - > > Key: CLOUDSTACK-3127 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3127 > 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: Chandan Purushothama >Assignee: Jessica Wang > Fix For: 4.2.0 > > Attachments: UICapture15.PNG, unable_to_reproduce_on_FireFox.jpg, > unable_to_reproduce_on_IE.jpg > > > Attached the corresponding Screenshot to the bug report -- 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-3127) UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is repeating twice
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-3127: - Attachment: unable_to_reproduce_on_FireFox.jpg > UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is > repeating twice > - > > Key: CLOUDSTACK-3127 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3127 > 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: Chandan Purushothama > Fix For: 4.2.0 > > Attachments: UICapture15.PNG, unable_to_reproduce_on_FireFox.jpg, > unable_to_reproduce_on_IE.jpg > > > Attached the corresponding Screenshot to the bug report -- 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-3127) UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is repeating twice
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-3127: - Attachment: unable_to_reproduce_on_IE.jpg > UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is > repeating twice > - > > Key: CLOUDSTACK-3127 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3127 > 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: Chandan Purushothama > Fix For: 4.2.0 > > Attachments: UICapture15.PNG, unable_to_reproduce_on_FireFox.jpg, > unable_to_reproduce_on_IE.jpg > > > Attached the corresponding Screenshot to the bug report -- 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-3127) UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is repeating twice
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-3127.
--
Resolution: Invalid
Unable to reproduce this bug on IE, FireFox.
Please see my 2 attachments ("unable_to_reproduce_xxx")
> UI: NTier: Label of Affinity Group Selection in "Add Instance" Box is
> repeating twice
> -
>
> Key: CLOUDSTACK-3127
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3127
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
> Attachments: UICapture15.PNG, unable_to_reproduce_on_FireFox.jpg,
> unable_to_reproduce_on_IE.jpg
>
>
> Attached the corresponding Screenshot to the bug report
--
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-3121) UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite of the existence of a private gateway
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693505#comment-13693505
]
ASF subversion and git services commented on CLOUDSTACK-3121:
-
Commit 85e55136c3a9ff6c9ac5fefe6f05044bd8175334 in branch
refs/heads/master-6-17-stable from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=85e5513 ]
CLOUDSTACK-3121: UI > VPC dashboard - fix a bug that showed wrong count number
of private gateways.
> UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite
> of the existence of a private gateway
> --
>
> Key: CLOUDSTACK-3121
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3121
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
> Attachments: UICapture14.PNG
>
>
> The corresponding Screenshot has been attached to the bug report where the
> private gateways count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371838007187
> { "listprivategatewaysresponse" : { } }
> On Clicking on the "Private Gateways" button on the Router box on the Screen.
> I see the private gateway listed.
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&listAll=true&_=1371838431113
> { "listprivategatewaysresponse" : { "count":1 ,"privategateway" : [
> {"id":"c9a04a7a-1881-4aaa-a7fc-222c9b95c602","gateway":"10.223.60.1","netmask":"255.255.255.192","ipaddress":"10.223.60.30","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","vlan":"600","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","state":"Ready","sourcenatsupported":true,"aclid":"14877d25-a7cb-46b9-84de-1d6fa06b0b9c"}
> ] } }
--
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-3198) NTier: Network ACL Rules Sequence on the Virtual Router does not match the Rule Priority mentioned on CloudStack
Chandan Purushothama created CLOUDSTACK-3198:
Summary: NTier: Network ACL Rules Sequence on the Virtual Router
does not match the Rule Priority mentioned on CloudStack
Key: CLOUDSTACK-3198
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3198
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: Chandan Purushothama
Fix For: 4.2.0
==
On VPC Virtual Router:
==
:ACL_INBOUND_eth2 - [0:0]
-A FORWARD -d 192.168.11.0/24 -o eth2 -j ACL_INBOUND_eth2
-A ACL_INBOUND_eth2 -s 10.223.131.172/32 -p tcp -m tcp --dport 20:40 -j ACCEPT
-A ACL_INBOUND_eth2 -s 10.223.131.172/32 -p tcp -m tcp --dport 20:40 -j DROP
-A ACL_INBOUND_eth2 -s 10.223.131.0/24 -p tcp -m tcp --dport 45:85 -j ACCEPT
-A ACL_INBOUND_eth2 -s 10.223.195.103/32 -p tcp -m tcp --dport 21:51 -j DROP
-A ACL_INBOUND_eth2 -s 10.216.133.50/32 -p tcp -m tcp --dport 50:99 -j ACCEPT
-A ACL_INBOUND_eth2 -s 10.223.131.192/26 -p tcp -m tcp --dport 105:145 -j DROP
-A ACL_INBOUND_eth2 -j DROP
==
On the Database:
==
mysql> select
id,acl_id,start_port,end_port,state,protocol,created,traffic_type,cidr,number
from network_acl_item where acl_id=4;
++++--++--+-+--+---++
| id | acl_id | start_port | end_port | state | protocol | created
| traffic_type | cidr | number |
++++--++--+-+--+---++
| 11 | 4 | 20 | 40 | Active | tcp | 2013-06-24 21:54:51
| Ingress | 10.223.131.172/32 | 1 |
| 12 | 4 | 21 | 51 | Active | tcp | 2013-06-24 21:57:20
| Ingress | 10.223.195.103/32 | 2 |
| 13 | 4 | 20 | 40 | Active | tcp | 2013-06-25 23:22:12
| Ingress | 10.223.131.172/32 | 3 |
| 14 | 4 | 50 | 99 | Active | tcp | 2013-06-25 23:24:19
| Ingress | 10.216.133.50/32 | 4 |
| 15 | 4 | 45 | 85 | Active | tcp | 2013-06-25 23:36:05
| Ingress | 10.223.131.193/24 | 5 |
| 17 | 4 |105 | 145 | Active | tcp | 2013-06-25 23:39:40
| Ingress | 10.223.131.193/26 | 6 |
++++--++--+-+--+---++
6 rows in set (0.00 sec)
=
On the Management Server:
=
2013-06-25 16:39:40,957 DEBUG [agent.transport.Request]
(Job-Executor-30:job-89) Seq 1-1278678427: Executing: { Cmd , MgmtId:
7471666038533, via: 1, Ver: v1, Flags: 11,
[{"routing.SetNetworkACLCommand":{"rules":[{"id":0,"vlanTag":"2580","protocol":"tcp","portRange":[20,40],"revoked":false,"alreadyAdded":true,"cidrList":["10.223.131.172/32"],"trafficType":"Ingress","action":"ACCEPT","number":1},{"id":0,"vlanTag":"2580","protocol":"tcp","portRange":[21,51],"revoked":false,"alreadyAdded":true,"cidrList":["10.223.195.103/32"],"trafficType":"Ingress","action":"DROP","number":2},{"id":0,"vlanTag":"2580","protocol":"tcp","portRange":[20,40],"revoked":false,"alreadyAdded":true,"cidrList":["10.223.131.172/32"],"trafficType":"Ingress","action":"DROP","number":3},{"id":0,"vlanTag":"2580","protocol":"tcp","portRange":[50,99],"revoked":false,"alreadyAdded":true,"cidrList":["10.216.133.50/32"],"trafficType":"Ingress","action":"ACCEPT","number":4},{"id":0,"vlanTag":"2580","protocol":"tcp","portRange":[45,85],"revoked":false,"alreadyAdded":true,"cidrList":["10.223.131.193/24"],"trafficType":"Ingress","action":"ACCEPT","number":5},{"id":0,"vlanTag":"2580","protocol":"tcp","portRange":[105,145],"revoked":false,"alreadyAdded":false,"cidrList":["10.223.131.193/26"],"trafficType":"Ingress","action":"DROP","number":6}],"nic":{"deviceId":3,"networkRateMbps":200,"defaultNic":false,"uuid":"6b89e7c9-6eb1-4598-8a6d-66f37980f321","ip":"192.168.11.1","netmask":"255.255.255.0","gateway":"192.168.11.1","mac":"02:00:51:de:00:02","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://2580","isolationUri":"vlan://2580","isSecurityGroupEnabled":false},"accessDetails":{"router.guest.ip":"192.168.11.1","guest.vlan.tag":"2580","zone.network.type":"Advanced","router.ip":"169.254.0.161","router.name":"r-3-NTIERAGN"},"wait":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-3121) UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite of the existence of a private gateway
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-3121.
--
Resolution: Fixed
> UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite
> of the existence of a private gateway
> --
>
> Key: CLOUDSTACK-3121
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3121
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
> Attachments: UICapture14.PNG
>
>
> The corresponding Screenshot has been attached to the bug report where the
> private gateways count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371838007187
> { "listprivategatewaysresponse" : { } }
> On Clicking on the "Private Gateways" button on the Router box on the Screen.
> I see the private gateway listed.
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&listAll=true&_=1371838431113
> { "listprivategatewaysresponse" : { "count":1 ,"privategateway" : [
> {"id":"c9a04a7a-1881-4aaa-a7fc-222c9b95c602","gateway":"10.223.60.1","netmask":"255.255.255.192","ipaddress":"10.223.60.30","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","vlan":"600","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","state":"Ready","sourcenatsupported":true,"aclid":"14877d25-a7cb-46b9-84de-1d6fa06b0b9c"}
> ] } }
--
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-3121) UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite of the existence of a private gateway
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693504#comment-13693504
]
ASF subversion and git services commented on CLOUDSTACK-3121:
-
Commit 6fdd0eea1b85642833d0f32dab11aa0518a43e31 in branch refs/heads/master
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6fdd0ee ]
CLOUDSTACK-3121: UI > VPC dashboard - fix a bug that showed wrong count number
of private gateways.
> UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite
> of the existence of a private gateway
> --
>
> Key: CLOUDSTACK-3121
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3121
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
> Attachments: UICapture14.PNG
>
>
> The corresponding Screenshot has been attached to the bug report where the
> private gateways count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371838007187
> { "listprivategatewaysresponse" : { } }
> On Clicking on the "Private Gateways" button on the Router box on the Screen.
> I see the private gateway listed.
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&listAll=true&_=1371838431113
> { "listprivategatewaysresponse" : { "count":1 ,"privategateway" : [
> {"id":"c9a04a7a-1881-4aaa-a7fc-222c9b95c602","gateway":"10.223.60.1","netmask":"255.255.255.192","ipaddress":"10.223.60.30","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","vlan":"600","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","state":"Ready","sourcenatsupported":true,"aclid":"14877d25-a7cb-46b9-84de-1d6fa06b0b9c"}
> ] } }
--
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-3121) UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite of the existence of a private gateway
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-3121:
Assignee: Jessica Wang
> UI: NTier: VPC Dashboard shows the count of the private gateway as 0 inspite
> of the existence of a private gateway
> --
>
> Key: CLOUDSTACK-3121
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3121
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
> Attachments: UICapture14.PNG
>
>
> The corresponding Screenshot has been attached to the bug report where the
> private gateways count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371838007187
> { "listprivategatewaysresponse" : { } }
> On Clicking on the "Private Gateways" button on the Router box on the Screen.
> I see the private gateway listed.
> http://10.223.195.103:8080/client/api?command=listPrivateGateways&response=json&sessionkey=bZH7EsX8%2Bsgv3TYtFphzZ2vwgEg%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&listAll=true&_=1371838431113
> { "listprivategatewaysresponse" : { "count":1 ,"privategateway" : [
> {"id":"c9a04a7a-1881-4aaa-a7fc-222c9b95c602","gateway":"10.223.60.1","netmask":"255.255.255.192","ipaddress":"10.223.60.30","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","vlan":"600","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","state":"Ready","sourcenatsupported":true,"aclid":"14877d25-a7cb-46b9-84de-1d6fa06b0b9c"}
> ] } }
--
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-3130) UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the selection of the Network Tier
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-3130.
--
Resolution: Fixed
> UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the
> selection of the Network Tier
> -
>
> Key: CLOUDSTACK-3130
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3130
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: UICapture16.PNG
>
>
> The VM is displayed in the "Select VM for Static NAT" Box even before the
> User selects the Network Tier. Clicking on "Apply" is such case, throws an
> Error message to the User prompting for Network Tier Selection.
> Attached the Corresponding UI Screenshot to the Bug Report.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listVirtualMachines&response=json&sessionkey=QnlNB43RJEe5xRXQf%2FW391j4hzg%3D&page=1&pageSize=20&listAll=true&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&account=atoms&domainid=597abf5c-d907-11e2-b5ac-06cba2000705&_=1371855032115
> { "listvirtualmachinesresponse" : { "count":1 ,"virtualmachine" : [
> {"id":"e5bd914e-985a-4496-b57e-be827a37343d","name":"Atoms-VPC1-Net2-VM-1","displayname":"Atoms-VPC1-Net2-VM-1","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","created":"2013-06-21T15:16:01-0700","state":"Running","haenable":false,"groupid":"2d2e6b1e-1029-4f9d-81f0-1e8213a595c4","group":"Atoms-VPC1-Net2-VM-1","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","zonetype":"Advanced","hostid":"7cdff16f-623e-40df-98f5-393d223fec52","hostname":"Rack3Host23.lab.vmops.com","templateid":"59846444-d907-11e2-b5ac-06cba2000705","templatename":"CentOS
> 5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no
> GUI
> (XenServer)","passwordenabled":false,"serviceofferingid":"998df06e-695e-4ccb-b885-0ce0276eec47","serviceofferingname":"Small
>
> Instance","cpunumber":1,"cpuspeed":500,"memory":512,"cpuused":"0.01%","networkkbsread":2,"networkkbswrite":2,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"599099f8-d907-11e2-b5ac-06cba2000705","rootdeviceid":0,"rootdevicetype":"ROOT","securitygroup":[],"nic":[{"id":"7d851d19-d194-4799-80b5-2733c1fcab5d","networkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","networkname":"Atoms-VPC-Net-2","netmask":"255.255.255.0","gateway":"192.168.11.1","ipaddress":"192.168.11.9","isolationuri":"vlan://2580","broadcasturi":"vlan://2580","traffictype":"Guest","type":"Isolated","isdefault":true,"macaddress":"02:00:2d:2b:00:01"}],"hypervisor":"XenServer","instancename":"i-3-12-NTIERAGN","tags":[],"affinitygroup":[],"displayvm":true}
> ] } }
--
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-3130) UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the selection of the Network Tier
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693500#comment-13693500
]
ASF subversion and git services commented on CLOUDSTACK-3130:
-
Commit 40bc81c363c418e985c78fae0c34d1f7ca54e105 in branch
refs/heads/master-6-17-stable from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=40bc81c ]
CLOUDSTACK-3130: UI > VPC section - Enable Static NAT - Select VM for static
NAT- show no VMs when no tier is selected.
> UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the
> selection of the Network Tier
> -
>
> Key: CLOUDSTACK-3130
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3130
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: UICapture16.PNG
>
>
> The VM is displayed in the "Select VM for Static NAT" Box even before the
> User selects the Network Tier. Clicking on "Apply" is such case, throws an
> Error message to the User prompting for Network Tier Selection.
> Attached the Corresponding UI Screenshot to the Bug Report.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listVirtualMachines&response=json&sessionkey=QnlNB43RJEe5xRXQf%2FW391j4hzg%3D&page=1&pageSize=20&listAll=true&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&account=atoms&domainid=597abf5c-d907-11e2-b5ac-06cba2000705&_=1371855032115
> { "listvirtualmachinesresponse" : { "count":1 ,"virtualmachine" : [
> {"id":"e5bd914e-985a-4496-b57e-be827a37343d","name":"Atoms-VPC1-Net2-VM-1","displayname":"Atoms-VPC1-Net2-VM-1","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","created":"2013-06-21T15:16:01-0700","state":"Running","haenable":false,"groupid":"2d2e6b1e-1029-4f9d-81f0-1e8213a595c4","group":"Atoms-VPC1-Net2-VM-1","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","zonetype":"Advanced","hostid":"7cdff16f-623e-40df-98f5-393d223fec52","hostname":"Rack3Host23.lab.vmops.com","templateid":"59846444-d907-11e2-b5ac-06cba2000705","templatename":"CentOS
> 5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no
> GUI
> (XenServer)","passwordenabled":false,"serviceofferingid":"998df06e-695e-4ccb-b885-0ce0276eec47","serviceofferingname":"Small
>
> Instance","cpunumber":1,"cpuspeed":500,"memory":512,"cpuused":"0.01%","networkkbsread":2,"networkkbswrite":2,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"599099f8-d907-11e2-b5ac-06cba2000705","rootdeviceid":0,"rootdevicetype":"ROOT","securitygroup":[],"nic":[{"id":"7d851d19-d194-4799-80b5-2733c1fcab5d","networkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","networkname":"Atoms-VPC-Net-2","netmask":"255.255.255.0","gateway":"192.168.11.1","ipaddress":"192.168.11.9","isolationuri":"vlan://2580","broadcasturi":"vlan://2580","traffictype":"Guest","type":"Isolated","isdefault":true,"macaddress":"02:00:2d:2b:00:01"}],"hypervisor":"XenServer","instancename":"i-3-12-NTIERAGN","tags":[],"affinitygroup":[],"displayvm":true}
> ] } }
--
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-3130) UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the selection of the Network Tier
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693498#comment-13693498
]
ASF subversion and git services commented on CLOUDSTACK-3130:
-
Commit 774141a9dcdec7af7fde7114d4a78404d20f416f in branch refs/heads/master
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=774141a ]
CLOUDSTACK-3130: UI > VPC section - Enable Static NAT - Select VM for static
NAT- show no VMs when no tier is selected.
> UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the
> selection of the Network Tier
> -
>
> Key: CLOUDSTACK-3130
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3130
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: UICapture16.PNG
>
>
> The VM is displayed in the "Select VM for Static NAT" Box even before the
> User selects the Network Tier. Clicking on "Apply" is such case, throws an
> Error message to the User prompting for Network Tier Selection.
> Attached the Corresponding UI Screenshot to the Bug Report.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listVirtualMachines&response=json&sessionkey=QnlNB43RJEe5xRXQf%2FW391j4hzg%3D&page=1&pageSize=20&listAll=true&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&account=atoms&domainid=597abf5c-d907-11e2-b5ac-06cba2000705&_=1371855032115
> { "listvirtualmachinesresponse" : { "count":1 ,"virtualmachine" : [
> {"id":"e5bd914e-985a-4496-b57e-be827a37343d","name":"Atoms-VPC1-Net2-VM-1","displayname":"Atoms-VPC1-Net2-VM-1","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","created":"2013-06-21T15:16:01-0700","state":"Running","haenable":false,"groupid":"2d2e6b1e-1029-4f9d-81f0-1e8213a595c4","group":"Atoms-VPC1-Net2-VM-1","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","zonetype":"Advanced","hostid":"7cdff16f-623e-40df-98f5-393d223fec52","hostname":"Rack3Host23.lab.vmops.com","templateid":"59846444-d907-11e2-b5ac-06cba2000705","templatename":"CentOS
> 5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no
> GUI
> (XenServer)","passwordenabled":false,"serviceofferingid":"998df06e-695e-4ccb-b885-0ce0276eec47","serviceofferingname":"Small
>
> Instance","cpunumber":1,"cpuspeed":500,"memory":512,"cpuused":"0.01%","networkkbsread":2,"networkkbswrite":2,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"599099f8-d907-11e2-b5ac-06cba2000705","rootdeviceid":0,"rootdevicetype":"ROOT","securitygroup":[],"nic":[{"id":"7d851d19-d194-4799-80b5-2733c1fcab5d","networkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","networkname":"Atoms-VPC-Net-2","netmask":"255.255.255.0","gateway":"192.168.11.1","ipaddress":"192.168.11.9","isolationuri":"vlan://2580","broadcasturi":"vlan://2580","traffictype":"Guest","type":"Isolated","isdefault":true,"macaddress":"02:00:2d:2b:00:01"}],"hypervisor":"XenServer","instancename":"i-3-12-NTIERAGN","tags":[],"affinitygroup":[],"displayvm":true}
> ] } }
--
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-3170) UI: NTier: There is no option/ button made available to update different parameters of a Network ACL Item
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-3170: Assignee: Pranav Saxena > UI: NTier: There is no option/ button made available to update different > parameters of a Network ACL Item > - > > Key: CLOUDSTACK-3170 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3170 > 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: Chandan Purushothama >Assignee: Pranav Saxena >Priority: Blocker > Fix For: 4.2.0 > > > Currently there is only provision to update the rule priority number on the > UI by moving the rules up and down. There is no provision/button made > available to update other parameters using the updateNetworkACL API. > = > As per FS at > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+ACL+deny+rules: > = > updateNetworkACLItem (aliased to updateNetworkACL) - async > Updates an existing NetworkACLItem > Parameters: > id (required) - Id of the network ACL Item > trafficType (optional) - can be ingress/egress (defaulted to ingress if > not specified) > cidrlist (optional) - List of the coma separated CIDRs for the rule. If > not specified, defaulted to 0.0.0.0/0 > startPort (optional) > endPort (optional) > protocol (optional). TCP/UDP/ICMP protocol types are supported > icmpType (optional) - type of the icmp message being sent > icmpCode (optional) - error code for this icmp message > action (optional) - allow/deny > number (optional) - rule number -- 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-2057) Developer's Guide incorrectly describes API signature as hash of base URL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693462#comment-13693462 ] Matty Courtney commented on CLOUDSTACK-2057: Hi! Thanks for your email. I am currently in the Pacific timezone (GMT-7) so responses may be delayed due to time differences. > Developer's Guide incorrectly describes API signature as hash of base URL > - > > Key: CLOUDSTACK-2057 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2057 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.1.0, 4.2.0 >Reporter: Jessica Tomechak >Assignee: sebastien goasguen > > This affects the "Signing API Requests" section in the Developer's Guide. The > source file is signing-api-requests.xml. > The docs define the Base URL as http://hostname:port and then go on to say > "Signature: This is the hashed signature of the Base URL". But when > describing how to generate the signature, the Base URL isn't used. The > Command String is used. > Need to determine which description is correct. The current info is > self-contradictory. > (Requested by Matty Courtney) -- 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-3171) UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another account as options to select for ACL List
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693460#comment-13693460
]
ASF subversion and git services commented on CLOUDSTACK-3171:
-
Commit 258fc140f5656f64169a3cb27cf2dd5d527e549a in branch
refs/heads/master-6-17-stable from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=258fc14 ]
CLOUDSTACK-3171: UI > VPC > add private gateway dialog - fix ACL dropdown to
only show ACL that belong to the VPC.
> UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another
> account as options to select for ACL List
> -
>
> Key: CLOUDSTACK-3171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3171
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqlcloudstackdumps.zip, UICapture19.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Create an account say atoms
> 2. Login to the atoms account and create an ACL in the account.
> 3. Create another account say protons
> 4. Login to as admin account and try to create a Private Gateway on the
> Protons account's VPC.
> 5. Observe the atoms account ACLs listed for ACL selection in the add private
> gateway box.
>
> Fire Bug Information:
>
> http://10.223.195.103:8080/client/api?command=listNetworkACLLists&response=json&sessionkey=4RM%2BxPGbpzXpriofP06GtnGJCSM%3D&_=1372115923846
> { "listnetworkacllistsresponse" : { "count":4 ,"networkacllist" : [
> {"id":"36f1981b-2899-4c7d-8129-78c814d0ac82","name":"Atoms-VPC-ACL-2","description":"Atoms-VPC-ACL-2","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"aa1e1724-a886-4749-af96-c04d8dda64b3","name":"Atoms-VPC-ACL-1","description":"Atoms-VPC-ACL-1","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"7bffad44-d907-11e2-b5ac-06cba2000705","name":"default_allow","description":"Default
> Network ACL Allow All"},
> {"id":"7bff8cd8-d907-11e2-b5ac-06cba2000705","name":"default_deny","description":"Default
> Network ACL Deny All"} ] } }
> Add Private Gateway box screenshot has been attached to the bug report.
--
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-3171) UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another account as options to select for ACL List
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693461#comment-13693461
]
ASF subversion and git services commented on CLOUDSTACK-3171:
-
Commit fc93b68738919b6784521f5346dbc4b1c3d4c86d in branch refs/heads/master
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fc93b68 ]
CLOUDSTACK-3171: UI > VPC > add private gateway dialog - fix ACL dropdown to
only show ACL that belong to the VPC.
> UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another
> account as options to select for ACL List
> -
>
> Key: CLOUDSTACK-3171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3171
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqlcloudstackdumps.zip, UICapture19.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Create an account say atoms
> 2. Login to the atoms account and create an ACL in the account.
> 3. Create another account say protons
> 4. Login to as admin account and try to create a Private Gateway on the
> Protons account's VPC.
> 5. Observe the atoms account ACLs listed for ACL selection in the add private
> gateway box.
>
> Fire Bug Information:
>
> http://10.223.195.103:8080/client/api?command=listNetworkACLLists&response=json&sessionkey=4RM%2BxPGbpzXpriofP06GtnGJCSM%3D&_=1372115923846
> { "listnetworkacllistsresponse" : { "count":4 ,"networkacllist" : [
> {"id":"36f1981b-2899-4c7d-8129-78c814d0ac82","name":"Atoms-VPC-ACL-2","description":"Atoms-VPC-ACL-2","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"aa1e1724-a886-4749-af96-c04d8dda64b3","name":"Atoms-VPC-ACL-1","description":"Atoms-VPC-ACL-1","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"7bffad44-d907-11e2-b5ac-06cba2000705","name":"default_allow","description":"Default
> Network ACL Allow All"},
> {"id":"7bff8cd8-d907-11e2-b5ac-06cba2000705","name":"default_deny","description":"Default
> Network ACL Deny All"} ] } }
> Add Private Gateway box screenshot has been attached to the bug report.
--
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-3171) UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another account as options to select for ACL List
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-3171.
--
Resolution: Fixed
> UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another
> account as options to select for ACL List
> -
>
> Key: CLOUDSTACK-3171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3171
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqlcloudstackdumps.zip, UICapture19.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Create an account say atoms
> 2. Login to the atoms account and create an ACL in the account.
> 3. Create another account say protons
> 4. Login to as admin account and try to create a Private Gateway on the
> Protons account's VPC.
> 5. Observe the atoms account ACLs listed for ACL selection in the add private
> gateway box.
>
> Fire Bug Information:
>
> http://10.223.195.103:8080/client/api?command=listNetworkACLLists&response=json&sessionkey=4RM%2BxPGbpzXpriofP06GtnGJCSM%3D&_=1372115923846
> { "listnetworkacllistsresponse" : { "count":4 ,"networkacllist" : [
> {"id":"36f1981b-2899-4c7d-8129-78c814d0ac82","name":"Atoms-VPC-ACL-2","description":"Atoms-VPC-ACL-2","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"aa1e1724-a886-4749-af96-c04d8dda64b3","name":"Atoms-VPC-ACL-1","description":"Atoms-VPC-ACL-1","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"7bffad44-d907-11e2-b5ac-06cba2000705","name":"default_allow","description":"Default
> Network ACL Allow All"},
> {"id":"7bff8cd8-d907-11e2-b5ac-06cba2000705","name":"default_deny","description":"Default
> Network ACL Deny All"} ] } }
> Add Private Gateway box screenshot has been attached to the bug report.
--
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-2057) Developer's Guide incorrectly describes API signature as hash of base URL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-2057: -- Assignee: sebastien goasguen > Developer's Guide incorrectly describes API signature as hash of base URL > - > > Key: CLOUDSTACK-2057 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2057 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.1.0, 4.2.0 >Reporter: Jessica Tomechak >Assignee: sebastien goasguen > > This affects the "Signing API Requests" section in the Developer's Guide. The > source file is signing-api-requests.xml. > The docs define the Base URL as http://hostname:port and then go on to say > "Signature: This is the hashed signature of the Base URL". But when > describing how to generate the signature, the Base URL isn't used. The > Command String is used. > Need to determine which description is correct. The current info is > self-contradictory. > (Requested by Matty Courtney) -- 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-3125) UI: NTier: VPC Dashboard shows the count of the Public IP Addresses as 0 inspite of the existence of an Acquired Public IP Address
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-3125.
--
Resolution: Fixed
Author: Jessica Wang
#mailto:jessicaw...@apache.org
Author date:22 hours ago (Mon Jun 24 16:33:56 2013)
Commit date:22 hours ago (Mon Jun 24 16:35:49 2013)
Commit hash:4e80c3dbb4eab4e0f59efeac433f7e30059b96d8
CLOUDSTACK-3166: UI - VPC section - configure VPC - tier - STATIC NATS - fix a
bug that listView showed nothing.
Contained in no branch
Contained in no tag
> UI: NTier: VPC Dashboard shows the count of the Public IP Addresses as 0
> inspite of the existence of an Acquired Public IP Address
> --
>
> Key: CLOUDSTACK-3125
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3125
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
>
> The corresponding Screenshot has been attached to the bug report where the
> Public IP Addresses count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&response=json&sessionkey=6OYYp9wxb8AfNebJcg3U8PsCmvI%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371843540390
> { "listpublicipaddressesresponse" : { } }
> On Clicking on the "Public IP Addresses" button on the Router box on the
> Screen. I see the acquired public IP Address listed.
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&response=json&sessionkey=6OYYp9wxb8AfNebJcg3U8PsCmvI%3D&listAll=true&page=1&pagesize=20&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371844297202
> { "listpublicipaddressesresponse" : { "count":2 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":false,"issystem":false,"networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false},
>
> {"id":"dbd6ae93-2192-42d2-a076-a7f1f907cc73","ipaddress":"10.223.139.68","allocated":"2013-06-19T11:43:10-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":true,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":false,"issystem":false,"networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3125) UI: NTier: VPC Dashboard shows the count of the Public IP Addresses as 0 inspite of the existence of an Acquired Public IP Address
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-3125:
Assignee: Jessica Wang
> UI: NTier: VPC Dashboard shows the count of the Public IP Addresses as 0
> inspite of the existence of an Acquired Public IP Address
> --
>
> Key: CLOUDSTACK-3125
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3125
> 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: Chandan Purushothama
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
>
> The corresponding Screenshot has been attached to the bug report where the
> Public IP Addresses count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&response=json&sessionkey=6OYYp9wxb8AfNebJcg3U8PsCmvI%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371843540390
> { "listpublicipaddressesresponse" : { } }
> On Clicking on the "Public IP Addresses" button on the Router box on the
> Screen. I see the acquired public IP Address listed.
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&response=json&sessionkey=6OYYp9wxb8AfNebJcg3U8PsCmvI%3D&listAll=true&page=1&pagesize=20&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371844297202
> { "listpublicipaddressesresponse" : { "count":2 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":false,"issystem":false,"networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false},
>
> {"id":"dbd6ae93-2192-42d2-a076-a7f1f907cc73","ipaddress":"10.223.139.68","allocated":"2013-06-19T11:43:10-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":true,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":false,"issystem":false,"networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3171) UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another account as options to select for ACL List
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-3171:
-
Attachment: mysqlcloudstackdumps.zip
> UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another
> account as options to select for ACL List
> -
>
> Key: CLOUDSTACK-3171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3171
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqlcloudstackdumps.zip, UICapture19.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Create an account say atoms
> 2. Login to the atoms account and create an ACL in the account.
> 3. Create another account say protons
> 4. Login to as admin account and try to create a Private Gateway on the
> Protons account's VPC.
> 5. Observe the atoms account ACLs listed for ACL selection in the add private
> gateway box.
>
> Fire Bug Information:
>
> http://10.223.195.103:8080/client/api?command=listNetworkACLLists&response=json&sessionkey=4RM%2BxPGbpzXpriofP06GtnGJCSM%3D&_=1372115923846
> { "listnetworkacllistsresponse" : { "count":4 ,"networkacllist" : [
> {"id":"36f1981b-2899-4c7d-8129-78c814d0ac82","name":"Atoms-VPC-ACL-2","description":"Atoms-VPC-ACL-2","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"aa1e1724-a886-4749-af96-c04d8dda64b3","name":"Atoms-VPC-ACL-1","description":"Atoms-VPC-ACL-1","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"7bffad44-d907-11e2-b5ac-06cba2000705","name":"default_allow","description":"Default
> Network ACL Allow All"},
> {"id":"7bff8cd8-d907-11e2-b5ac-06cba2000705","name":"default_deny","description":"Default
> Network ACL Deny All"} ] } }
> Add Private Gateway box screenshot has been attached to the bug report.
--
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-3130) UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the selection of the Network Tier
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-3130:
Assignee: Jessica Wang
> UI: NTier: VMs are listed in "Select VM for Static NAT" Box even before the
> selection of the Network Tier
> -
>
> Key: CLOUDSTACK-3130
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3130
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: UICapture16.PNG
>
>
> The VM is displayed in the "Select VM for Static NAT" Box even before the
> User selects the Network Tier. Clicking on "Apply" is such case, throws an
> Error message to the User prompting for Network Tier Selection.
> Attached the Corresponding UI Screenshot to the Bug Report.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listVirtualMachines&response=json&sessionkey=QnlNB43RJEe5xRXQf%2FW391j4hzg%3D&page=1&pageSize=20&listAll=true&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&account=atoms&domainid=597abf5c-d907-11e2-b5ac-06cba2000705&_=1371855032115
> { "listvirtualmachinesresponse" : { "count":1 ,"virtualmachine" : [
> {"id":"e5bd914e-985a-4496-b57e-be827a37343d","name":"Atoms-VPC1-Net2-VM-1","displayname":"Atoms-VPC1-Net2-VM-1","account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","created":"2013-06-21T15:16:01-0700","state":"Running","haenable":false,"groupid":"2d2e6b1e-1029-4f9d-81f0-1e8213a595c4","group":"Atoms-VPC1-Net2-VM-1","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","zonetype":"Advanced","hostid":"7cdff16f-623e-40df-98f5-393d223fec52","hostname":"Rack3Host23.lab.vmops.com","templateid":"59846444-d907-11e2-b5ac-06cba2000705","templatename":"CentOS
> 5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no
> GUI
> (XenServer)","passwordenabled":false,"serviceofferingid":"998df06e-695e-4ccb-b885-0ce0276eec47","serviceofferingname":"Small
>
> Instance","cpunumber":1,"cpuspeed":500,"memory":512,"cpuused":"0.01%","networkkbsread":2,"networkkbswrite":2,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"599099f8-d907-11e2-b5ac-06cba2000705","rootdeviceid":0,"rootdevicetype":"ROOT","securitygroup":[],"nic":[{"id":"7d851d19-d194-4799-80b5-2733c1fcab5d","networkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","networkname":"Atoms-VPC-Net-2","netmask":"255.255.255.0","gateway":"192.168.11.1","ipaddress":"192.168.11.9","isolationuri":"vlan://2580","broadcasturi":"vlan://2580","traffictype":"Guest","type":"Isolated","isdefault":true,"macaddress":"02:00:2d:2b:00:01"}],"hypervisor":"XenServer","instancename":"i-3-12-NTIERAGN","tags":[],"affinitygroup":[],"displayvm":true}
> ] } }
--
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-3171) UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another account as options to select for ACL List
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-3171:
Assignee: Jessica Wang
> UI: NTier: Add Private Gateway Box lists ACL Lists belonging to another
> account as options to select for ACL List
> -
>
> Key: CLOUDSTACK-3171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3171
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: UICapture19.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Create an account say atoms
> 2. Login to the atoms account and create an ACL in the account.
> 3. Create another account say protons
> 4. Login to as admin account and try to create a Private Gateway on the
> Protons account's VPC.
> 5. Observe the atoms account ACLs listed for ACL selection in the add private
> gateway box.
>
> Fire Bug Information:
>
> http://10.223.195.103:8080/client/api?command=listNetworkACLLists&response=json&sessionkey=4RM%2BxPGbpzXpriofP06GtnGJCSM%3D&_=1372115923846
> { "listnetworkacllistsresponse" : { "count":4 ,"networkacllist" : [
> {"id":"36f1981b-2899-4c7d-8129-78c814d0ac82","name":"Atoms-VPC-ACL-2","description":"Atoms-VPC-ACL-2","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"aa1e1724-a886-4749-af96-c04d8dda64b3","name":"Atoms-VPC-ACL-1","description":"Atoms-VPC-ACL-1","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713"},
>
> {"id":"7bffad44-d907-11e2-b5ac-06cba2000705","name":"default_allow","description":"Default
> Network ACL Allow All"},
> {"id":"7bff8cd8-d907-11e2-b5ac-06cba2000705","name":"default_deny","description":"Default
> Network ACL Deny All"} ] } }
> Add Private Gateway box screenshot has been attached to the bug report.
--
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-3197) UI: NTier: User is required to scroll down every single time to "Create Network" after creation of 3 Network Tiers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-3197: - Assignee: Sonny Chhen Environment: Chandan talked to Sonny about this bug and Sonny said he will move the "Create Network" icon to the top. > UI: NTier: User is required to scroll down every single time to "Create > Network" after creation of 3 Network Tiers > -- > > Key: CLOUDSTACK-3197 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3197 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Chandan talked to Sonny about this bug and Sonny said he > will move the "Create Network" icon to the top. >Reporter: Chandan Purushothama >Assignee: Sonny Chhen > Fix For: 4.2.0 > > Attachments: UICapture21.PNG > > > Users are required to scroll down to see the "Create Network" Box on the Main > VPC page after creation of three network tiers. To search for an option > presented below the list of network tiers is not user friendly. > Attached the corresponding Screenshot to the bug report. -- 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-3196) UI: NTier: "Edit" and "Dedicate Host" on the Host Details page have the same Icons
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-3196: Assignee: Brian Federle > UI: NTier: "Edit" and "Dedicate Host" on the Host Details page have the same > Icons > -- > > Key: CLOUDSTACK-3196 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3196 > 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: Chandan Purushothama >Assignee: Brian Federle > Fix For: 4.2.0 > > Attachments: UICapture20.PNG > > > Attached the corresponding Screenshot to the Bug Report -- 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-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693404#comment-13693404
]
Alena Prokharchyk commented on CLOUDSTACK-3195:
---
All PF rules (as well as all other networking rules) assigned to the VM, stay
with the VM till its Expunged. Its per original design. So the VM in the
Destroyed state will have PF rules, and if Admin decides to recover it, the vm
will be recovered along with all the networking rules.
The fix to this bug would be - display all the networking rules to the end
user, disgregading the vm status. And let him remove the rule.
Its a UI bug that the rules are not being displayed; Api returns everything.
But then the UI makes subsequent call for the vm in Destroyed state, and the vm
is not returned to the end user:
http://10.223.195.103:8080/client/api?command=listPortForwardingRules&response=json&sessionkey=3w1EfGy7voGxuvTPz%2FLfopctLOg%3D&ipaddressid=c9ccf05a-42ff-4d5b-bcb3-95d30a139e6a&listAll=true&_=1372196380545
{ "listportforwardingrulesresponse" : { "count":1 ,"portforwardingrule" : [
{"id":"3a6e33ad-9541-44ce-9b88-a5fe7dc31f1f","privateport":"22","privateendport":"22","protocol":"tcp","publicport":"22","publicendport":"22","virtualmachineid":"1f8942cc-4c2f-428f-b967-196d92f40d94","virtualmachinename":"1f8942cc-4c2f-428f-b967-196d92f40d94","virtualmachinedisplayname":"1f8942cc-4c2f-428f-b967-196d92f40d94","ipaddressid":"c9ccf05a-42ff-4d5b-bcb3-95d30a139e6a","ipaddress":"10.223.139.73","state":"Active","cidrlist":"","tags":[],"vmguestip":"10.1.1.149"}
] } }
http://10.223.195.103:8080/client/api?command=listVirtualMachines&response=json&sessionkey=3w1EfGy7voGxuvTPz%2FLfopctLOg%3D&listAll=true&id=1f8942cc-4c2f-428f-b967-196d92f40d94&_=1372196380617
{ "listvirtualmachinesresponse" : { } }
So the UI doesn't display the rule. The fix would be - display the rule as
long as its returned with listPortForwarding call.
> cannot view/delete forward rules if underlying/target VM is destroyed first
> ---
>
> Key: CLOUDSTACK-3195
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.1.0
> Environment: CentOS 6.4+latest patches with official 4.1.0 RPM
> release from Apache
>Reporter: Bryan Whitehead
>Assignee: Alena Prokharchyk
>
> As a non-admin user, create a new Isolated network with SNAT. Build a VM
> using this network.
> After VM is up, In the new isolated network add a firewall rule (port 22 as
> example). Next add a forward for private range 22-22 and public 22-22, choose
> the VM in network.
> Verify the forward and firewall rule work (ssh SNAT-IP etc).
> KEY BUG: Delete the VM in the isolated network. After the delete there will
> be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN
> user)
> Create a new VM using the same isolated network. When attempting to setup a
> new forward to this VM you'll get an error about a rule already existing as a
> conflict - however you won't be able to delete it.
> The admin user can see the bogus rule and delete it. Then everything works as
> expected.
--
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-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-3195: -- Component/s: (was: Network Controller) UI Assignee: Sonny Chhen (was: Alena Prokharchyk) > cannot view/delete forward rules if underlying/target VM is destroyed first > --- > > Key: CLOUDSTACK-3195 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: CentOS 6.4+latest patches with official 4.1.0 RPM > release from Apache >Reporter: Bryan Whitehead >Assignee: Sonny Chhen > > As a non-admin user, create a new Isolated network with SNAT. Build a VM > using this network. > After VM is up, In the new isolated network add a firewall rule (port 22 as > example). Next add a forward for private range 22-22 and public 22-22, choose > the VM in network. > Verify the forward and firewall rule work (ssh SNAT-IP etc). > KEY BUG: Delete the VM in the isolated network. After the delete there will > be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN > user) > Create a new VM using the same isolated network. When attempting to setup a > new forward to this VM you'll get an error about a rule already existing as a > conflict - however you won't be able to delete it. > The admin user can see the bogus rule and delete it. Then everything works as > expected. -- 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-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-3195: - Assignee: Alena Prokharchyk > cannot view/delete forward rules if underlying/target VM is destroyed first > --- > > Key: CLOUDSTACK-3195 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.1.0 > Environment: CentOS 6.4+latest patches with official 4.1.0 RPM > release from Apache >Reporter: Bryan Whitehead >Assignee: Alena Prokharchyk > > As a non-admin user, create a new Isolated network with SNAT. Build a VM > using this network. > After VM is up, In the new isolated network add a firewall rule (port 22 as > example). Next add a forward for private range 22-22 and public 22-22, choose > the VM in network. > Verify the forward and firewall rule work (ssh SNAT-IP etc). > KEY BUG: Delete the VM in the isolated network. After the delete there will > be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN > user) > Create a new VM using the same isolated network. When attempting to setup a > new forward to this VM you'll get an error about a rule already existing as a > conflict - however you won't be able to delete it. > The admin user can see the bogus rule and delete it. Then everything works as > expected. -- 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-3126) NTier: vpc.max.networks includes all the User Tier Networks and Private Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-3126. --- Resolution: Cannot Reproduce Can't reproduce the bug in the latest build 1eacd7872e3749eaa470c9fbf6c419b58e121513. Steps taken: 1) set max.project.networks=2 2) Being a regular user, created a vpc. 3) Added 1 private gateway to the vpc. 4) Was able to create 2 tiers - the max the global config allows - after that. > NTier: vpc.max.networks includes all the User Tier Networks and Private > Networks > > > Key: CLOUDSTACK-3126 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3126 > 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: Chandan Purushothama >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.2.0 > > > A New User to CloudStack might assume that the vpc.max.networks includes only > the guest networks in a VPC. But the global parameter includes all the VPC > private networks including private gateway networks and site2site vpn gateway > networks too. Currently, the User might gets confused to understand why is > he/she is able to create User networks lesser than the vpc.max.networks > limit. Either we need to report the message with more information or release > note this observation. -- 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-3125) UI: NTier: VPC Dashboard shows the count of the Public IP Addresses as 0 inspite of the existence of an Acquired Public IP Address
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693349#comment-13693349
]
Alena Prokharchyk commented on CLOUDSTACK-3125:
---
The only difference between 2 commands - listAll=true is not being sent with
the first command. UI folks, please add it to the first call.
> UI: NTier: VPC Dashboard shows the count of the Public IP Addresses as 0
> inspite of the existence of an Acquired Public IP Address
> --
>
> Key: CLOUDSTACK-3125
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3125
> 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: Chandan Purushothama
> Fix For: 4.2.0
>
>
> The corresponding Screenshot has been attached to the bug report where the
> Public IP Addresses count is shown as 0.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&response=json&sessionkey=6OYYp9wxb8AfNebJcg3U8PsCmvI%3D&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371843540390
> { "listpublicipaddressesresponse" : { } }
> On Clicking on the "Public IP Addresses" button on the Router box on the
> Screen. I see the acquired public IP Address listed.
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&response=json&sessionkey=6OYYp9wxb8AfNebJcg3U8PsCmvI%3D&listAll=true&page=1&pagesize=20&vpcid=9d5fb2f4-7957-4848-947e-84450469f713&_=1371844297202
> { "listpublicipaddressesresponse" : { "count":2 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":false,"issystem":false,"networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false},
>
> {"id":"dbd6ae93-2192-42d2-a076-a7f1f907cc73","ipaddress":"10.223.139.68","allocated":"2013-06-19T11:43:10-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":true,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":false,"issystem":false,"networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3194) Management server startup fails with SSPCredentialDao Injection
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693347#comment-13693347 ] syed ahmed commented on CLOUDSTACK-3194: I get the same error when trying to start the management server. > Management server startup fails with SSPCredentialDao Injection > --- > > Key: CLOUDSTACK-3194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Prasanna Santhanam >Priority: Blocker > > com.cloud.network.dao.SspCredentialDaoImpl > rocessor,affinityProcessors,DedicatedResourceManagerImpl,ExplicitDedicationProcessor,org.springframework.context.annotation.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0]; > root of factory hierarchy > 2013-06-25 13:27:34,157 ERROR [web.context.ContextLoader] (main:null) Context > initialization failed > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'actionEventUtils': Injection of autowired dependencies failed; > nested exception is org.springframework.beans.factory.BeanCreationException: > Could no > t autowire field: com.cloud.event.dao.EventDao > com.cloud.event.ActionEventUtils.eventDao; nested exception is > org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find > class [com.cloud.network.dao.SspCredentialDaoImpl] > for bean with name 'sspCredentialDaoImpl' defined in class path resource > [componentContext.xml]; nested exception is java.lang.ClassNotFoundException: > com.cloud.network.dao.SspCredentialDaoImpl > at > org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:287) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1106) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469) > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383) > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4467) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) > at > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) > at > org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) > at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) > at > org.apache.catalina.core.Conta
[jira] [Created] (CLOUDSTACK-3197) UI: NTier: User is required to scroll down every single time to "Create Network" after creation of 3 Network Tiers
Chandan Purushothama created CLOUDSTACK-3197: Summary: UI: NTier: User is required to scroll down every single time to "Create Network" after creation of 3 Network Tiers Key: CLOUDSTACK-3197 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3197 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: Chandan Purushothama Fix For: 4.2.0 Attachments: UICapture21.PNG Users are required to scroll down to see the "Create Network" Box on the Main VPC page after creation of three network tiers. To search for an option presented below the list of network tiers is not user friendly. Attached the corresponding Screenshot to the bug report. -- 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-3197) UI: NTier: User is required to scroll down every single time to "Create Network" after creation of 3 Network Tiers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-3197: - Attachment: UICapture21.PNG > UI: NTier: User is required to scroll down every single time to "Create > Network" after creation of 3 Network Tiers > -- > > Key: CLOUDSTACK-3197 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3197 > 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: Chandan Purushothama > Fix For: 4.2.0 > > Attachments: UICapture21.PNG > > > Users are required to scroll down to see the "Create Network" Box on the Main > VPC page after creation of three network tiers. To search for an option > presented below the list of network tiers is not user friendly. > Attached the corresponding Screenshot to the bug report. -- 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-3196) UI: NTier: "Edit" and "Dedicate Host" on the Host Details page have the same Icons
Chandan Purushothama created CLOUDSTACK-3196: Summary: UI: NTier: "Edit" and "Dedicate Host" on the Host Details page have the same Icons Key: CLOUDSTACK-3196 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3196 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: Chandan Purushothama Fix For: 4.2.0 Attachments: UICapture20.PNG Attached the corresponding Screenshot to the Bug Report -- 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-3196) UI: NTier: "Edit" and "Dedicate Host" on the Host Details page have the same Icons
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-3196: - Attachment: UICapture20.PNG > UI: NTier: "Edit" and "Dedicate Host" on the Host Details page have the same > Icons > -- > > Key: CLOUDSTACK-3196 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3196 > 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: Chandan Purushothama > Fix For: 4.2.0 > > Attachments: UICapture20.PNG > > > Attached the corresponding Screenshot to the Bug Report -- 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-2901) Ubuntu 13.04 - Migrate guest VM fail - async jobs not completed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti resolved CLOUDSTACK-2901.
--
Resolution: Incomplete
Pl provide log files
> Ubuntu 13.04 - Migrate guest VM fail - async jobs not completed
>
>
> Key: CLOUDSTACK-2901
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2901
> 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 ASF 4.2 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> hosts ubuntu 13.04CloudStack-non-OSS-master-22-ubuntu13.04.tar.gz
>Reporter: angeline shen
>Assignee: angeline shen
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz
>
>
> 1. zone with two PVLAN networks
> 2. deploy VMs in both PVLANs.
> Confirm VMs in same PVLAN cannot connect to each other.
> confirm VMs in 1 PVLAN can reach VMs in other PVLAN. VMs can reach
> outside world
> 3. Migrate guest VMs async jobs not completed even after 45 minutes, still
> waiting .
> 2013-06-07 12:48:59,329 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-12:null) submit async job-44, details: AsyncJobVO {id:44,
> userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
> null, cmd: org.ap
> ache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null,
> cmdInfo:
> {"response":"json","sessionkey":"ZD1MBAdDE0LXFWamvA7uLghcE7g\u003d","virtualmachineid":"ce363fbf-3ae5-4917-a0da-4254892e48af","hostid":"85e6649c-6b8
> 7-49e0-a9be-33552d515182","ctxUserId":"2","httpmethod":"GET","_":"1370634858107","ctxAccountId":"2","ctxStartEventId":"159"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, resu
> lt: null, initMsid: 206915885084099, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-06-07 12:48:59,329 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-21:job-44) Executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-44
> 2013-06-07 12:48:59,330 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
> ===END=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&hostid=85e6649c-6b87-49e0-a9be-33552d515182&virtualmachineid=ce363fbf-3ae5-4917-a0da-4254
> 892e48af&response=json&sessionkey=ZD1MBAdDE0LXFWamvA7uLg
> 4. after 45 minutes
> 2013-06-07 13:18:59,377 DEBUG [agent.manager.AgentAttache]
> (Job-Executor-21:job-44) Seq 5-1461193119: Waiting some more time because
> this is the current command
> 5. migrate guest VM:
> 2013-06-07 12:42:41,015 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-24:null) submit async job-43, details: AsyncJobVO {id:43,
> userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
> null, cmd: org.ap
> ache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null,
> cmdInfo:
> {"response":"json","sessionkey":"ZD1MBAdDE0LXFWamvA7uLghcE7g\u003d","virtualmachineid":"5cb7f1e1-6f9c-45ce-a840-512b09c0fbbb","hostid":"08912eba-92d
> a-4495-9566-3a021d29b399","ctxUserId":"2","httpmethod":"GET","_":"1370634479806","ctxAccountId":"2","ctxStartEventId":"157"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, resu
> lt: null, initMsid: 206915885084099, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-06-07 12:42:41,015 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-20:job-43) Executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-43
> 2013-06-07 12:42:41,016 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
> ===END=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&hostid=08912eba-92da-4495-9566-3a021d29b399&virtualmachineid=5cb7f1e1-6f9c-45ce-a840-512b
> 09c0fbbb&response=json&sessionkey=ZD1MBAdDE0LXFWamvA7uLghcE7g%3D&_=1370634479806
> 6. after 45 minutes
> 2013-06-07 13:12:41,067 DEBUG [agent.manager.AgentAttache]
> (Job-Executor-20:job-43) Seq 1-198249334: Waiting some more time because this
> is the current command
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3165) UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows count as 1 on all Network Tiers
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-3165.
--
Resolution: Fixed
> UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows
> count as 1 on all Network Tiers
> --
>
> Key: CLOUDSTACK-3165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3165
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqldbsdumps.zip, UICapture17.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Acquire a Public IP Address onto the VPC.
> 2. Enable Static NAT on the Public IP Address to a VM in a Network Tier of
> the VPC.
> 3. Observe that the Static NAT count on all the Network Tiers is updated to 1.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&listAll=true&response=json&sessionkey=3fTWK8oTGNJ0VWqL4jx07%2BSsgd8%3D&networkid=c81066f7-f3ed-4aab-8f86-be8d3bab32ed&isstaticnat=true&_=1372108552240
> { "listpublicipaddressesresponse" : { "count":1 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":true,"issystem":false,"virtualmachineid":"e5bd914e-985a-4496-b57e-be827a37343d","vmipaddress":"192.168.11.9","virtualmachinename":"Atoms-VPC1-Net2-VM-1","virtualmachinedisplayname":"Atoms-VPC1-Net2-VM-1","associatednetworkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","associatednetworkname":"Atoms-VPC-Net-2","networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3165) UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows count as 1 on all Network Tiers
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693263#comment-13693263
]
ASF subversion and git services commented on CLOUDSTACK-3165:
-
Commit 3778ae1012de63fea40e764e89f905567f1305ad in branch
refs/heads/master-6-17-stable from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3778ae1 ]
CLOUDSTACK-3165: UI > VPC page - Configure VPC chart - pass associatednetworkid
instead of networkid to listPublicIpAddresses API.
> UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows
> count as 1 on all Network Tiers
> --
>
> Key: CLOUDSTACK-3165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3165
> 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: Chandan Purushothama
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqldbsdumps.zip, UICapture17.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Acquire a Public IP Address onto the VPC.
> 2. Enable Static NAT on the Public IP Address to a VM in a Network Tier of
> the VPC.
> 3. Observe that the Static NAT count on all the Network Tiers is updated to 1.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&listAll=true&response=json&sessionkey=3fTWK8oTGNJ0VWqL4jx07%2BSsgd8%3D&networkid=c81066f7-f3ed-4aab-8f86-be8d3bab32ed&isstaticnat=true&_=1372108552240
> { "listpublicipaddressesresponse" : { "count":1 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":true,"issystem":false,"virtualmachineid":"e5bd914e-985a-4496-b57e-be827a37343d","vmipaddress":"192.168.11.9","virtualmachinename":"Atoms-VPC1-Net2-VM-1","virtualmachinedisplayname":"Atoms-VPC1-Net2-VM-1","associatednetworkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","associatednetworkname":"Atoms-VPC-Net-2","networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3165) UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows count as 1 on all Network Tiers
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-3165:
Assignee: Jessica Wang
> UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows
> count as 1 on all Network Tiers
> --
>
> Key: CLOUDSTACK-3165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3165
> 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: Chandan Purushothama
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqldbsdumps.zip, UICapture17.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Acquire a Public IP Address onto the VPC.
> 2. Enable Static NAT on the Public IP Address to a VM in a Network Tier of
> the VPC.
> 3. Observe that the Static NAT count on all the Network Tiers is updated to 1.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&listAll=true&response=json&sessionkey=3fTWK8oTGNJ0VWqL4jx07%2BSsgd8%3D&networkid=c81066f7-f3ed-4aab-8f86-be8d3bab32ed&isstaticnat=true&_=1372108552240
> { "listpublicipaddressesresponse" : { "count":1 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":true,"issystem":false,"virtualmachineid":"e5bd914e-985a-4496-b57e-be827a37343d","vmipaddress":"192.168.11.9","virtualmachinename":"Atoms-VPC1-Net2-VM-1","virtualmachinedisplayname":"Atoms-VPC1-Net2-VM-1","associatednetworkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","associatednetworkname":"Atoms-VPC-Net-2","networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3165) UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows count as 1 on all Network Tiers
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693260#comment-13693260
]
ASF subversion and git services commented on CLOUDSTACK-3165:
-
Commit 6a711fc682754b18092d3f7ecde66695d565c7b5 in branch refs/heads/master
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6a711fc ]
CLOUDSTACK-3165: UI > VPC page - Configure VPC chart - pass associatednetworkid
instead of networkid to listPublicIpAddresses API.
> UI: NTier: On Creating a Static NAT Rule, Static NATs button on the VPC shows
> count as 1 on all Network Tiers
> --
>
> Key: CLOUDSTACK-3165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3165
> 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: Chandan Purushothama
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mysqldbsdumps.zip, UICapture17.PNG
>
>
>
> Steps to Reproduce:
>
> 1. Acquire a Public IP Address onto the VPC.
> 2. Enable Static NAT on the Public IP Address to a VM in a Network Tier of
> the VPC.
> 3. Observe that the Static NAT count on all the Network Tiers is updated to 1.
> ===
> Firebug Information:
> ===
> http://10.223.195.103:8080/client/api?command=listPublicIpAddresses&listAll=true&response=json&sessionkey=3fTWK8oTGNJ0VWqL4jx07%2BSsgd8%3D&networkid=c81066f7-f3ed-4aab-8f86-be8d3bab32ed&isstaticnat=true&_=1372108552240
> { "listpublicipaddressesresponse" : { "count":1 ,"publicipaddress" : [
> {"id":"7dad9df2-a583-4619-9023-caff753f6f36","ipaddress":"10.223.139.71","allocated":"2013-06-21T12:37:56-0700","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","issourcenat":false,"account":"atoms","domainid":"597abf5c-d907-11e2-b5ac-06cba2000705","domain":"ROOT","forvirtualnetwork":true,"vlanid":"c7975fa6-22d0-463f-a083-75bac4cc9f8b","vlanname":"1391","isstaticnat":true,"issystem":false,"virtualmachineid":"e5bd914e-985a-4496-b57e-be827a37343d","vmipaddress":"192.168.11.9","virtualmachinename":"Atoms-VPC1-Net2-VM-1","virtualmachinedisplayname":"Atoms-VPC1-Net2-VM-1","associatednetworkid":"c81066f7-f3ed-4aab-8f86-be8d3bab32ed","associatednetworkname":"Atoms-VPC-Net-2","networkid":"3e90b6dd-5ef3-48cf-a409-8d7ae4d4f4a7","state":"Allocated","physicalnetworkid":"58c17654-dabc-4bf5-b18f-c2f5355c4537","vpcid":"9d5fb2f4-7957-4848-947e-84450469f713","tags":[],"isportable":false}
> ] } }
--
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-3163) KVM Virtual Router startup time is painfully long
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Bayer updated CLOUDSTACK-3163: - Component/s: KVM Summary: KVM Virtual Router startup time is painfully long (was: Virtual Router startup time is painfully long) After some further digging, it looks like this may be KVM-specific - at least it's not the case for xen or vmware hypervisors. VmwareResource and in CitrixResourceBase both implement "execute(VmDataCommand cmd)" themselves, and their implementations handle all the aspects of a single instance in one operation, rather than iterating over each file as VirtualRoutingResource.execute(VmDataCommand cmd) does. So far as I can tell, with KVM, VirtualRoutingResource.execute(VmDataCommand cmd) is what's used. Any chance that method can be modernized like the VmwareResource one to use userdata.py and have one SCP and one SSH call rather than ~20 total? > KVM Virtual Router startup time is painfully long > - > > Key: CLOUDSTACK-3163 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3163 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: pre-4.0.0 > Environment: CloudPlatform 3.0.3, but I don't see any changes to the > relevant code (I think) on master >Reporter: Andrew Bayer >Priority: Critical > > When you've got a couple thousand instances, spread across 10 or so pods, > virtual router startup time is near crippling - actually, if you don't enable > the option to have virtual routers only populated with instances in their > pod, it *is* crippling, in that the virtual routers don't finish starting > before the management server decides they've timed out and tries to start a > new one. > This seems to be the result of a few painful inefficiencies: > - The same codepath is followed whether you're adding a new instance to an > already running VR, or adding two hundred already running instances to a new > VR. So each ssh/scp/sed/cp/chmod/etc command is replicated for each instance, > rather than finding efficiencies by doing things across the whole set of > instances. > - But what really eats up the time is the population of vm data - for each > piece of vm data (which, from a rough look at the code, seems to be something > like 10 or 11 data files), there are something like 7 ssh calls and an scp > call. So that means that per instance, we have somewhere around 80 to 90 > ssh/scp calls, plus the single ssh call for dhcp_entry.sh. So with 200 > instances, that's 1600 to 1800 ssh/scp calls on a single VR, with all the > overhead entailed in opening that many ssh connections, starting bash, etc, > etc... Given that in my experience, a VR with ~200 instances takes ~90 > minutes to start up (I may be misremembering slightly - it could be ~200 > instances takes closer to 60 minutes, and ~300 takes closer to 90), that > works out to 3 seconds or so per ssh/scp, which doesn't seem implausible to > me. > So, this shouldn't be this way. At a minimum, there's no reason not to > offload the whole process from a script run on the host making repeated ssh > calls to the VR to a script on the VR that gets called from the host, albeit > possibly a temporary one that's generated on the fly and copied over to the > VR. That alone would probably save most of the VR startup time, just by > dropping the number of ssh/scp connections per instance from 80-90 to 3 > (dhcp_entry.sh call, scp of temporary script, execution of temporary 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] [Created] (CLOUDSTACK-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
Bryan Whitehead created CLOUDSTACK-3195: --- Summary: cannot view/delete forward rules if underlying/target VM is destroyed first Key: CLOUDSTACK-3195 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Environment: CentOS 6.4+latest patches with official 4.1.0 RPM release from Apache Reporter: Bryan Whitehead As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network. After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network. Verify the forward and firewall rule work (ssh SNAT-IP etc). KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it. The admin user can see the bogus rule and delete it. Then everything works as expected. -- 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-3195) cannot view/delete forward rules if underlying/target VM is destroyed first
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Whitehead updated CLOUDSTACK-3195: Description: As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network. After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network. Verify the forward and firewall rule work (ssh SNAT-IP etc). KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN user) Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it. The admin user can see the bogus rule and delete it. Then everything works as expected. was: As a non-admin user, create a new Isolated network with SNAT. Build a VM using this network. After VM is up, In the new isolated network add a firewall rule (port 22 as example). Next add a forward for private range 22-22 and public 22-22, choose the VM in network. Verify the forward and firewall rule work (ssh SNAT-IP etc). KEY BUG: Delete the VM in the isolated network. After the delete there will be no way to delete or see the rule to remove the forward. Create a new VM using the same isolated network. When attempting to setup a new forward to this VM you'll get an error about a rule already existing as a conflict - however you won't be able to delete it. The admin user can see the bogus rule and delete it. Then everything works as expected. > cannot view/delete forward rules if underlying/target VM is destroyed first > --- > > Key: CLOUDSTACK-3195 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3195 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.1.0 > Environment: CentOS 6.4+latest patches with official 4.1.0 RPM > release from Apache >Reporter: Bryan Whitehead > > As a non-admin user, create a new Isolated network with SNAT. Build a VM > using this network. > After VM is up, In the new isolated network add a firewall rule (port 22 as > example). Next add a forward for private range 22-22 and public 22-22, choose > the VM in network. > Verify the forward and firewall rule work (ssh SNAT-IP etc). > KEY BUG: Delete the VM in the isolated network. After the delete there will > be no way to delete or see the rule to remove the forward. (AS a NON-ADMIN > user) > Create a new VM using the same isolated network. When attempting to setup a > new forward to this VM you'll get an error about a rule already existing as a > conflict - however you won't be able to delete it. > The admin user can see the bogus rule and delete it. Then everything works as > expected. -- 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-3069) [UI]Quickview of POD is not displaying any info in UI.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranav Saxena resolved CLOUDSTACK-3069. --- Resolution: Fixed Cherry picked to master-6-17-stable. Thanks ! > [UI]Quickview of POD is not displaying any info in UI. > -- > > Key: CLOUDSTACK-3069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3069 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: CloudPlatform-4.0-91-rhel6.3. >Reporter: manasaveloori >Assignee: Isaac Chiang >Priority: Minor > Fix For: 4.2.0 > > Attachments: pod.jpg > > > 1.Have a CS with any zone. > 2.Go to Infrastructure->Pods->Quickview > Observation: > Quickview option of the POD not displaying any information. > API is working fine. > Attached is the SC for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3069) [UI]Quickview of POD is not displaying any info in UI.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693157#comment-13693157 ] ASF subversion and git services commented on CLOUDSTACK-3069: - Commit 12d7a3dfb8e427da38eb804a9353b9fb2d09128e in branch refs/heads/master-6-17-stable from [~isaacchi...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=12d7a3d ] CLOUDSTACK-3069: [UI]Quickview of POD is not displaying any info in UI > [UI]Quickview of POD is not displaying any info in UI. > -- > > Key: CLOUDSTACK-3069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3069 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: CloudPlatform-4.0-91-rhel6.3. >Reporter: manasaveloori >Assignee: Isaac Chiang >Priority: Minor > Fix For: 4.2.0 > > Attachments: pod.jpg > > > 1.Have a CS with any zone. > 2.Go to Infrastructure->Pods->Quickview > Observation: > Quickview option of the POD not displaying any information. > API is working fine. > Attached is the SC for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3150) [Dedicated_Resources] Host is going to avoid set while deploying a VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranav Saxena resolved CLOUDSTACK-3150.
---
Resolution: Fixed
Bug is fixed now in both master and master-6-17-stable . Please verify in the
latest build.
Thanks!
> [Dedicated_Resources] Host is going to avoid set while deploying a VM
> --
>
> Key: CLOUDSTACK-3150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3150
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup, UI
>Affects Versions: 4.2.0
> Environment: Latest build from master-6-17-stable branch
>Reporter: Sanjeev N
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Host is going to avoid set while deploying a VM
> Steps to Reproduce:
>
> 1.Bring up CS with only one host and one cluster in the zone
> 2.Wait for the system vms to come up
> 3.After the default CentOS template is in Ready state try to deploy guest vm
> with default Compute Offering(Small)
> Expected Result:
> ==
> VM deployment should succeed.
> Actual Result:
> ===
> VM deployment failed
> Observations:
> ===
> After the system vms are up host automatically went into to Dedicated state.
> So the FirstFitAllocator is not finding any suitable host to deploy the vm
> since this is host is in avoid set.
> Following is the log snippet:
> 2013-06-24 11:05:34,664 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-21:null) submit async job-23, details: AsyncJobVO {id:23,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 9, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"BUwec1jIHiTD3QZHDFe8xdXLerc\u003d","ctxUserId":"2","serviceOfferingId":"2e01eb93-32b9-4006-819d-5ec0fbb56010","httpmethod":"GET","securitygroupids":"a05e80b0-daa2-11e2-bb94-06ab465f","zoneId":"9633b3cf-ee80-415c-8e66-0dd1ab70d466","templateId":"3b266e5f-339a-4c65-b704-d10211f736e8","response":"json","id":"9","hypervisor":"XenServer","name":"s1","_":"1372066621056","ctxAccountId":"2","ctxStartEventId":"101","displayname":"s1"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-24 11:05:34,667 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===END=== 10.146.0.20 -- GET
> command=deployVirtualMachine&zoneId=9633b3cf-ee80-415c-8e66-0dd1ab70d466&templateId=3b266e5f-339a-4c65-b704-d10211f736e8&hypervisor=XenServer&serviceOfferingId=2e01eb93-32b9-4006-819d-5ec0fbb56010&securitygroupids=a05e80b0-daa2-11e2-bb94-06ab465f&displayname=s1&name=s1&response=json&sessionkey=BUwec1jIHiTD3QZHDFe8xdXLerc%3D&_=1372066621056
> 2013-06-24 11:05:34,677 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-17:job-23) Executing
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-23
> 2013-06-24 11:05:34,686 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) InfrastructureEntity name
> is:com.cloud.offering.ServiceOffering
> 2013-06-24 11:05:34,690 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.template.VirtualMachineTemplate
> 2013-06-24 11:05:34,693 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.network.security.SecurityGroup
> 2013-06-24 11:05:34,795 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Cannot use this dedicated host Rack1Pod1Host13.
> 2013-06-24 11:05:34,796 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Deploy avoids pods: null, clusters: null, hosts: [5]
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) DeploymentPlanner allocation algorithm:
> com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_691b6f1d@354c0a31
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Trying to allocate a host and storage pools from
> dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Is ROOT volume READY (pool already allocated)?: No
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-17:job-23) Searching all possible resources under this Zone: 1
> 2013-06-24 11:05:34,801 DEBUG [cloud.deploy.FirstFitP
[jira] [Assigned] (CLOUDSTACK-3150) [Dedicated_Resources] Host is going to avoid set while deploying a VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranav Saxena reassigned CLOUDSTACK-3150:
-
Assignee: Pranav Saxena
> [Dedicated_Resources] Host is going to avoid set while deploying a VM
> --
>
> Key: CLOUDSTACK-3150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3150
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup, UI
>Affects Versions: 4.2.0
> Environment: Latest build from master-6-17-stable branch
>Reporter: Sanjeev N
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Host is going to avoid set while deploying a VM
> Steps to Reproduce:
>
> 1.Bring up CS with only one host and one cluster in the zone
> 2.Wait for the system vms to come up
> 3.After the default CentOS template is in Ready state try to deploy guest vm
> with default Compute Offering(Small)
> Expected Result:
> ==
> VM deployment should succeed.
> Actual Result:
> ===
> VM deployment failed
> Observations:
> ===
> After the system vms are up host automatically went into to Dedicated state.
> So the FirstFitAllocator is not finding any suitable host to deploy the vm
> since this is host is in avoid set.
> Following is the log snippet:
> 2013-06-24 11:05:34,664 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-21:null) submit async job-23, details: AsyncJobVO {id:23,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 9, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"BUwec1jIHiTD3QZHDFe8xdXLerc\u003d","ctxUserId":"2","serviceOfferingId":"2e01eb93-32b9-4006-819d-5ec0fbb56010","httpmethod":"GET","securitygroupids":"a05e80b0-daa2-11e2-bb94-06ab465f","zoneId":"9633b3cf-ee80-415c-8e66-0dd1ab70d466","templateId":"3b266e5f-339a-4c65-b704-d10211f736e8","response":"json","id":"9","hypervisor":"XenServer","name":"s1","_":"1372066621056","ctxAccountId":"2","ctxStartEventId":"101","displayname":"s1"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-24 11:05:34,667 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===END=== 10.146.0.20 -- GET
> command=deployVirtualMachine&zoneId=9633b3cf-ee80-415c-8e66-0dd1ab70d466&templateId=3b266e5f-339a-4c65-b704-d10211f736e8&hypervisor=XenServer&serviceOfferingId=2e01eb93-32b9-4006-819d-5ec0fbb56010&securitygroupids=a05e80b0-daa2-11e2-bb94-06ab465f&displayname=s1&name=s1&response=json&sessionkey=BUwec1jIHiTD3QZHDFe8xdXLerc%3D&_=1372066621056
> 2013-06-24 11:05:34,677 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-17:job-23) Executing
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-23
> 2013-06-24 11:05:34,686 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) InfrastructureEntity name
> is:com.cloud.offering.ServiceOffering
> 2013-06-24 11:05:34,690 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.template.VirtualMachineTemplate
> 2013-06-24 11:05:34,693 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.network.security.SecurityGroup
> 2013-06-24 11:05:34,795 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Cannot use this dedicated host Rack1Pod1Host13.
> 2013-06-24 11:05:34,796 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Deploy avoids pods: null, clusters: null, hosts: [5]
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) DeploymentPlanner allocation algorithm:
> com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_691b6f1d@354c0a31
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Trying to allocate a host and storage pools from
> dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Is ROOT volume READY (pool already allocated)?: No
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-17:job-23) Searching all possible resources under this Zone: 1
> 2013-06-24 11:05:34,801 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-17:job-23) Listing clusters in order of aggregate capacity,
> that have (atleast
[jira] [Commented] (CLOUDSTACK-3155) [VMware] Deletion of zone should not be allowed if VMware DC is still associated with that zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693093#comment-13693093 ] ASF subversion and git services commented on CLOUDSTACK-3155: - Commit 34bdd1e1b3e94d7afff3f9a5b865065a5157158f in branch refs/heads/master-6-17-stable from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=34bdd1e ] CLOUDSTACK-3155 [VMware] Deletion of zone should not be allowed if VMware DC is still associated with that zone. Check if there exists any VMware DC already associated with this zone. Deny zone deletion if true. Signed-off-by: Sateesh Chodapuneedi > [VMware] Deletion of zone should not be allowed if VMware DC is still > associated with that zone. > > > Key: CLOUDSTACK-3155 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3155 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Labels: vmware > > Deletion of zone should not be allowed if VMware DC is still associated with > that zone. > Let user go back and remove VMware DC from cloudstack zone and re-try > deletion of zone. > This is inline with the way deletion of zone is handled if there are > pods/physical networks etc. that are part of zone already. -- 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-3151) [VMware] CloudStack does case sensitive processing of names of VMware objects.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693094#comment-13693094 ] ASF subversion and git services commented on CLOUDSTACK-3151: - Commit 9deefc2121995040930e1b87bf83f378f7c3743c in branch refs/heads/master-6-17-stable from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9deefc2 ] CLOUDSTACK-3151 [VMware] CloudStack does case sensitive processing of names of VMware objects. Signed-off-by: Sateesh Chodapuneedi > [VMware] CloudStack does case sensitive processing of names of VMware objects. > -- > > Key: CLOUDSTACK-3151 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3151 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi >Priority: Critical > Fix For: 4.2.0 > > > Case of name of VMware datacenter / cluster etc. matters to CloudStack, which > should not be the case. -- 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-1766) VmWare DVS vmware.ports.per.dvportgroup setting not used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693092#comment-13693092 ] ASF subversion and git services commented on CLOUDSTACK-1766: - Commit a7637cb615c05f26a6104f21b785132165b2eb25 in branch refs/heads/master-6-17-stable from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a7637cb ] CLOUDSTACK-1766 VmWare DVS vmware.ports.per.dvportgroup setting not used Read the global configuration setting while configuring VmwareManager. Also enabling autoExpand feature for supported distributed virtual switch versions. Signed-off-by: Sateesh Chodapuneedi > VmWare DVS vmware.ports.per.dvportgroup setting not used > - > > Key: CLOUDSTACK-1766 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1766 > 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: 4.2 Master >Reporter: ilya musayev >Assignee: Sateesh Chodapuneedi >Priority: Critical > Labels: CLOUDSTACK, DVS, VMWARE > Fix For: 4.2.0 > > > 1) vmware.ports.per.dvportgroup setting is not read or used. In my case, i > set it to 512, while it fails back to 256 - no matter what i tried. > * The 512 value stays set in CloudStack, however in vmware dvs under > portgroup number of ports, it does not change and uses default 256. > I made a test and set a static variable of numPorts = 512 in > vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java and > it took the static entry without issues. > Please double check this part. -- 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-1767) VMWare DVS - cannot use untagged portgroups
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693091#comment-13693091
]
ASF subversion and git services commented on CLOUDSTACK-1767:
-
Commit 348f0ab029b8515e40004deccd1045bc0983d41d in branch
refs/heads/master-6-17-stable from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=348f0ab ]
CLOUDSTACK-1767 VMWare DVS - cannot use untagged portgroups
Signed-off-by: Sateesh Chodapuneedi
> VMWare DVS - cannot use untagged portgroups
> ---
>
> Key: CLOUDSTACK-1767
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1767
> 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: 4.2 Master
>Reporter: ilya musayev
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Labels: CLOUDSTACK, DVS, VMWARE
> Fix For: 4.2.0
>
>
> Please revise this portion of the code in
> vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java
> if (vid != null) {
> vlanSpec = createDVPortVlanIdSpec(vid);
> } else {
> vlanSpec = createDVPortVlanSpec();
> }
> This code does not take into account PortGroups on DVS that are untagged.
> This issue was particularly hard to identify as stack trace would only show
> up on the hypervisor hostd.log and VC error is was vary vague. the hostd.log
> on hypervisor indicate that vlanSpec is invalid for PortGroups that are
> untagged (or the ID is left blank).
> 2013-03-14T20:32:12.351Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Throw
> vim.fault.DvsApplyOperationFault
> 2013-03-14T20:32:12.352Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Result:
> --> (vim.fault.DvsApplyOperationFault) {
> --> dynamicType = ,
> --> faultCause = (vmodl.MethodFault) null,
> --> objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [
> --> (vim.fault.DvsApplyOperationFault.FaultOnObject) {
> --> dynamicType = ,
> --> objectId = "2442",
> --> type = "vim.dvs.DistributedVirtualPort",
> --> fault = (vmodl.fault.InvalidArgument) {
> --> dynamicType = ,
> --> faultCause = (vmodl.MethodFault) null,
> --> invalidProperty = "vlanSpec",
> --> msg = "",
> --> },
> --> }
> --> ],
> --> msg = "",
> --> }
--
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-3194) Management server startup fails with SSPCredentialDao Injection
Prasanna Santhanam created CLOUDSTACK-3194: -- Summary: Management server startup fails with SSPCredentialDao Injection Key: CLOUDSTACK-3194 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3194 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Prasanna Santhanam Priority: Blocker com.cloud.network.dao.SspCredentialDaoImpl rocessor,affinityProcessors,DedicatedResourceManagerImpl,ExplicitDedicationProcessor,org.springframework.context.annotation.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0]; root of factory hierarchy 2013-06-25 13:27:34,157 ERROR [web.context.ContextLoader] (main:null) Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actionEventUtils': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could no t autowire field: com.cloud.event.dao.EventDao com.cloud.event.ActionEventUtils.eventDao; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.cloud.network.dao.SspCredentialDaoImpl] for bean with name 'sspCredentialDaoImpl' defined in class path resource [componentContext.xml]; nested exception is java.lang.ClassNotFoundException: com.cloud.network.dao.SspCredentialDaoImpl at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:287) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1106) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469) at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.r
[jira] [Commented] (CLOUDSTACK-1767) VMWare DVS - cannot use untagged portgroups
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693061#comment-13693061
]
ASF subversion and git services commented on CLOUDSTACK-1767:
-
Commit c36a952f159fccb899409a8eca97e0f7621905e3 in branch refs/heads/master
from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c36a952 ]
CLOUDSTACK-1767 VMWare DVS - cannot use untagged portgroups
Signed-off-by: Sateesh Chodapuneedi
> VMWare DVS - cannot use untagged portgroups
> ---
>
> Key: CLOUDSTACK-1767
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1767
> 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: 4.2 Master
>Reporter: ilya musayev
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Labels: CLOUDSTACK, DVS, VMWARE
> Fix For: 4.2.0
>
>
> Please revise this portion of the code in
> vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java
> if (vid != null) {
> vlanSpec = createDVPortVlanIdSpec(vid);
> } else {
> vlanSpec = createDVPortVlanSpec();
> }
> This code does not take into account PortGroups on DVS that are untagged.
> This issue was particularly hard to identify as stack trace would only show
> up on the hypervisor hostd.log and VC error is was vary vague. the hostd.log
> on hypervisor indicate that vlanSpec is invalid for PortGroups that are
> untagged (or the ID is left blank).
> 2013-03-14T20:32:12.351Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Throw
> vim.fault.DvsApplyOperationFault
> 2013-03-14T20:32:12.352Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Result:
> --> (vim.fault.DvsApplyOperationFault) {
> --> dynamicType = ,
> --> faultCause = (vmodl.MethodFault) null,
> --> objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [
> --> (vim.fault.DvsApplyOperationFault.FaultOnObject) {
> --> dynamicType = ,
> --> objectId = "2442",
> --> type = "vim.dvs.DistributedVirtualPort",
> --> fault = (vmodl.fault.InvalidArgument) {
> --> dynamicType = ,
> --> faultCause = (vmodl.MethodFault) null,
> --> invalidProperty = "vlanSpec",
> --> msg = "",
> --> },
> --> }
> --> ],
> --> msg = "",
> --> }
--
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-1767) VMWare DVS - cannot use untagged portgroups
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-1767.
--
Resolution: Fixed
> VMWare DVS - cannot use untagged portgroups
> ---
>
> Key: CLOUDSTACK-1767
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1767
> 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: 4.2 Master
>Reporter: ilya musayev
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Labels: CLOUDSTACK, DVS, VMWARE
> Fix For: 4.2.0
>
>
> Please revise this portion of the code in
> vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java
> if (vid != null) {
> vlanSpec = createDVPortVlanIdSpec(vid);
> } else {
> vlanSpec = createDVPortVlanSpec();
> }
> This code does not take into account PortGroups on DVS that are untagged.
> This issue was particularly hard to identify as stack trace would only show
> up on the hypervisor hostd.log and VC error is was vary vague. the hostd.log
> on hypervisor indicate that vlanSpec is invalid for PortGroups that are
> untagged (or the ID is left blank).
> 2013-03-14T20:32:12.351Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Throw
> vim.fault.DvsApplyOperationFault
> 2013-03-14T20:32:12.352Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Result:
> --> (vim.fault.DvsApplyOperationFault) {
> --> dynamicType = ,
> --> faultCause = (vmodl.MethodFault) null,
> --> objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [
> --> (vim.fault.DvsApplyOperationFault.FaultOnObject) {
> --> dynamicType = ,
> --> objectId = "2442",
> --> type = "vim.dvs.DistributedVirtualPort",
> --> fault = (vmodl.fault.InvalidArgument) {
> --> dynamicType = ,
> --> faultCause = (vmodl.MethodFault) null,
> --> invalidProperty = "vlanSpec",
> --> msg = "",
> --> },
> --> }
> --> ],
> --> msg = "",
> --> }
--
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 ] Harikrishna Patnala updated CLOUDSTACK-2835: Status: Ready To Review (was: In Progress) > 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 >Assignee: Harikrishna Patnala > 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 netwo
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13693049#comment-13693049 ] Harikrishna Patnala commented on CLOUDSTACK-2835: - In review board https://reviews.apache.org/r/12063/ > 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 >Assignee: Harikrishna Patnala > 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.NetworkManag
[jira] [Updated] (CLOUDSTACK-3187) cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering overcommit factor;cluster is getting disable based on actual use
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-3187: Status: Ready To Review (was: In Progress) > cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering > overcommit factor;cluster is getting disable based on actual use > - > > Key: CLOUDSTACK-3187 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3187 > 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 >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.2.0 > > Attachments: DB_Logs.rar > > > Steps to reproduce > --- > 1-set "cluster.(cpu/mem).allocated.capacity.disablethreshold" to 0.75 > 2-set (memory/cpu) overcommit ratio to 2 > 3-Try to use capacity(cpu/ram) more than what actual available by deploying > some vms > Actual > - > Cluster is getting disabled after actual usage crosses(0.75) disable threshold > Expected > -- > cluster should get disabled based on over committed use not actual use > Logs > > 2013-06-25 10:11:49,573 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-7:job-19) Listing clusters in order of aggregate capacity, that > have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 > 2013-06-25 10:11:49,593 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-7:job-19) Cannot allocate cluster list [1] for vm creation > since their allocated percentage crosses the disable capacity threshold > defined at each cluster/ at global value for capacity Type : 0, skipping > these clusters > 2013-06-25 10:11:49,594 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-7:job-19) No clusters found after removing disabled clusters > and clusters in avoid list, returning. > 2013-06-25 10:11:49,601 DEBUG [cloud.vm.UserVmManagerImpl] > (Job-Executor-7:job-19) Destroying vm VM[User|mm4] as it failed to create on > Host with Id:null > 2013-06-25 10:11:49,630 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-7:job-19) VM state transitted from :Stopped to Error with > event: OperationFailedToErrorvm's original host id: null new host id: null > host id before state transition: null > 2013-06-25 10:11:49,654 WARN [apache.cloudstack.alerts] > (Job-Executor-7:job-19) alertType:: 8 // dataCenterId:: 1 // podId:: null // > clusterId:: null // message:: Failed to deploy Vm with Id: 8, on Host with > Id: null > 2013-06-25 10:11:49,726 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-19) > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|mm4]Scope=interface com.cloud.dc.DataCenter; id=1 > 2013-06-25 10:11:49,727 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-19) > Unable to create a deployment for VM[User|mm4] > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|mm4]Scope=interface com.cloud.dc.DataCenter; id=1 > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3312) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2851) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2837) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-25 10:11:49,729 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-7:job-19)
[jira] [Updated] (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:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-2794: Status: Ready To Review (was: In Progress) > 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 >Assignee: Harikrishna Patnala >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] [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=13693045#comment-13693045 ] Harikrishna Patnala commented on CLOUDSTACK-2794: - In review board https://reviews.apache.org/r/12079/ > 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 >Assignee: Harikrishna Patnala >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] [Resolved] (CLOUDSTACK-1766) VmWare DVS vmware.ports.per.dvportgroup setting not used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-1766. -- Resolution: Fixed Fix Version/s: 4.2.0 > VmWare DVS vmware.ports.per.dvportgroup setting not used > - > > Key: CLOUDSTACK-1766 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1766 > 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: 4.2 Master >Reporter: ilya musayev >Assignee: Sateesh Chodapuneedi >Priority: Critical > Labels: CLOUDSTACK, DVS, VMWARE > Fix For: 4.2.0 > > > 1) vmware.ports.per.dvportgroup setting is not read or used. In my case, i > set it to 512, while it fails back to 256 - no matter what i tried. > * The 512 value stays set in CloudStack, however in vmware dvs under > portgroup number of ports, it does not change and uses default 256. > I made a test and set a static variable of numPorts = 512 in > vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java and > it took the static entry without issues. > Please double check this part. -- 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-1766) VmWare DVS vmware.ports.per.dvportgroup setting not used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693041#comment-13693041 ] ASF subversion and git services commented on CLOUDSTACK-1766: - Commit b3927ffe966a278dd70777ddf13fa08859f5916b in branch refs/heads/master from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b3927ff ] CLOUDSTACK-1766 VmWare DVS vmware.ports.per.dvportgroup setting not used Read the global configuration setting while configuring VmwareManager. Also enabling autoExpand feature for supported distributed virtual switch versions. Signed-off-by: Sateesh Chodapuneedi > VmWare DVS vmware.ports.per.dvportgroup setting not used > - > > Key: CLOUDSTACK-1766 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1766 > 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: 4.2 Master >Reporter: ilya musayev >Assignee: Sateesh Chodapuneedi >Priority: Critical > Labels: CLOUDSTACK, DVS, VMWARE > > 1) vmware.ports.per.dvportgroup setting is not read or used. In my case, i > set it to 512, while it fails back to 256 - no matter what i tried. > * The 512 value stays set in CloudStack, however in vmware dvs under > portgroup number of ports, it does not change and uses default 256. > I made a test and set a static variable of numPorts = 512 in > vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java and > it took the static entry without issues. > Please double check this part. -- 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-3167) [Automation] List VLAN range API call failed with null pointer exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693017#comment-13693017 ] Bharat Kumar commented on CLOUDSTACK-3167: -- Saksham can you take a look at this. > [Automation] List VLAN range API call failed with null pointer exception > - > > Key: CLOUDSTACK-3167 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3167 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: Master build, >Reporter: Rayees Namathponnan >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-3167.rar > > > SSVM test cases failed from BVT > run listVLAN Range command, its fails willl null pointer exception > http://10.223.49.195:8096/?command=listVlanIpRanges&zoneid=72deef27-805a-4c6a-bf37-2b04d6c614d0&response=json > 2013-06-24 17:32:44,763 DEBUG [cloud.projects.ProjectManagerImpl] > (Job-Executor-17:job-3320) Accounts are unassign successfully from project > Project[94|name=Project-TRGJ8K|domainid=1] as a part of project cleanup... > 2013-06-24 17:32:44,795 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Complete async job-3320, jobStatus: 1, resultCode: > 0, result: org.apache.cloudstack.api.response.SuccessResponse@7c56947b > 2013-06-24 17:32:44,799 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Done executing > org.apache.cloudstack.api.command.user.project.DeleteProjectCmd for job-3320 > 2013-06-24 17:32:45,192 ERROR [cloud.api.ApiServer] (ApiServer-2:null) > unhandled exception executing api command: listVlanIpRanges > java.lang.NullPointerException > at > com.cloud.configuration.ConfigurationManagerImpl.getVlanAccount(ConfigurationManagerImpl.java:4570) > at com.cloud.api.ApiDBUtils.getVlanAccount(ApiDBUtils.java:1062) > at > com.cloud.api.ApiResponseHelper.createVlanIpRangeResponse(ApiResponseHelper.java:604) > at > org.apache.cloudstack.api.command.admin.vlan.ListVlanIpRangesCmd.execute(ListVlanIpRangesCmd.java:145) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServer.handle(ApiServer.java:302) > 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:992) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- 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-3167) [Automation] List VLAN range API call failed with null pointer exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3167: - Assignee: Saksham Srivastava (was: Bharat Kumar) > [Automation] List VLAN range API call failed with null pointer exception > - > > Key: CLOUDSTACK-3167 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3167 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: Master build, >Reporter: Rayees Namathponnan >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-3167.rar > > > SSVM test cases failed from BVT > run listVLAN Range command, its fails willl null pointer exception > http://10.223.49.195:8096/?command=listVlanIpRanges&zoneid=72deef27-805a-4c6a-bf37-2b04d6c614d0&response=json > 2013-06-24 17:32:44,763 DEBUG [cloud.projects.ProjectManagerImpl] > (Job-Executor-17:job-3320) Accounts are unassign successfully from project > Project[94|name=Project-TRGJ8K|domainid=1] as a part of project cleanup... > 2013-06-24 17:32:44,795 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Complete async job-3320, jobStatus: 1, resultCode: > 0, result: org.apache.cloudstack.api.response.SuccessResponse@7c56947b > 2013-06-24 17:32:44,799 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Done executing > org.apache.cloudstack.api.command.user.project.DeleteProjectCmd for job-3320 > 2013-06-24 17:32:45,192 ERROR [cloud.api.ApiServer] (ApiServer-2:null) > unhandled exception executing api command: listVlanIpRanges > java.lang.NullPointerException > at > com.cloud.configuration.ConfigurationManagerImpl.getVlanAccount(ConfigurationManagerImpl.java:4570) > at com.cloud.api.ApiDBUtils.getVlanAccount(ApiDBUtils.java:1062) > at > com.cloud.api.ApiResponseHelper.createVlanIpRangeResponse(ApiResponseHelper.java:604) > at > org.apache.cloudstack.api.command.admin.vlan.ListVlanIpRangesCmd.execute(ListVlanIpRangesCmd.java:145) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServer.handle(ApiServer.java:302) > 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:992) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- 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-3003) [VPC][VMware]Unexpected exception while applying a static route in vpc.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693015#comment-13693015 ] ASF subversion and git services commented on CLOUDSTACK-3003: - Commit 1ab87ef4bed8ba53eb2dd5f7aa422b2bf0c8e13c in branch refs/heads/master from [~jayapal] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1ab87ef ] CLOUDSTACK-3003 Fixed static route issue in vpc vmware > [VPC][VMware]Unexpected exception while applying a static route in vpc. > --- > > Key: CLOUDSTACK-3003 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3003 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: latest master build >Reporter: manasaveloori >Assignee: Jayapal Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Steps: > 1.Have a CS with advanced zone. > 2.Create a VPC. > 3.Create a private gateway to VPC . > 4.Apply a static route for private gateway . > Observation: > Applying the static route in vpc is failing with following exception: > 2013-06-14 18:16:21,883 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-33:job-29) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to apply static > routes in vpc [VPC [1-vpc1] > at > com.cloud.network.element.VpcVirtualRouterElement.applyStaticRoutes(VpcVirtualRouterElement.java:441) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1655) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1618) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1603) > at > com.cloud.network.vpc.VpcManagerImpl.revokeStaticRoute(VpcManagerImpl.java:1680) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd.execute(CreateStaticRouteCmd.java:108) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-14 18:16:21,885 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-33:job-29) Complete async job-29, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Failed to apply static routes in vpc > [VPC [1-vpc1] > Attached is the management server log. -- 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-3003) [VPC][VMware]Unexpected exception while applying a static route in vpc.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693012#comment-13693012 ] ASF subversion and git services commented on CLOUDSTACK-3003: - Commit 1a2b57052947cb9824a88ca5d4e9b977e188e119 in branch refs/heads/master-6-17-stable from [~jayapal] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1a2b570 ] CLOUDSTACK-3003 Fixed static route issue in vpc vmware > [VPC][VMware]Unexpected exception while applying a static route in vpc. > --- > > Key: CLOUDSTACK-3003 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3003 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: latest master build >Reporter: manasaveloori >Assignee: Jayapal Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Steps: > 1.Have a CS with advanced zone. > 2.Create a VPC. > 3.Create a private gateway to VPC . > 4.Apply a static route for private gateway . > Observation: > Applying the static route in vpc is failing with following exception: > 2013-06-14 18:16:21,883 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-33:job-29) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to apply static > routes in vpc [VPC [1-vpc1] > at > com.cloud.network.element.VpcVirtualRouterElement.applyStaticRoutes(VpcVirtualRouterElement.java:441) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1655) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1618) > at > com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1603) > at > com.cloud.network.vpc.VpcManagerImpl.revokeStaticRoute(VpcManagerImpl.java:1680) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd.execute(CreateStaticRouteCmd.java:108) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-14 18:16:21,885 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-33:job-29) Complete async job-29, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Failed to apply static routes in vpc > [VPC [1-vpc1] > Attached is the management server log. -- 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-3147) Failed to Create System VM's in the ESX 5.0 using the latest systemVM template.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-3147. -- Resolution: Fixed Removing BootOrderSection from the template resolves this. > Failed to Create System VM's in the ESX 5.0 using the latest systemVM > template. > --- > > Key: CLOUDSTACK-3147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Failed to Create System VM's in the ESX 5.0 using the latest systemVM > template with the below error messages: > 2013-06-21 16:18:20,009 DEBUG [cloud.storage.VolumeManagerImpl] > (secstorage-1:null) Checking if we need to prepare 1 volumes for > VM[SecondaryStorageVm|s-1-VM] > 2013-06-21 16:18:20,017 DEBUG [storage.image.ImageDataFactoryImpl] > (secstorage-1:null) template 8 is not in store:1, type:Image > 2013-06-21 16:18:20,096 DEBUG > [storage.datastore.ObjectInDataStoreManagerImpl] (secstorage-1:null) allow > muliple create requests > 2013-06-21 16:18:21,686 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-25:null) Ping from 4 > 2013-06-21 16:18:22,116 ERROR [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-15:10.223.250.131) Unable to execute > PrimaryStorageDownloadCommand due to exception > javax.xml.ws.soap.SOAPFaultException: > Required parameter spec is missing > while parsing call information for method ImportVApp > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method importVApp > on object of type vim.ResourcePool > at line 1, column 0 > at > com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at > com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) > Then tried to import the template trough the Vcenter 5.0 manually and found > the below error message > "The OVF package requires unsupported hardware. > Details:Line25: Unsupported hardware family 'vmx-09'." > When tried with the ESX 5.1 it works fine. > Attaching the management server 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] [Closed] (CLOUDSTACK-3176) KVM DeployVM fails with unable to get answer that is of type StartAnswer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanna Santhanam closed CLOUDSTACK-3176.
--
Assignee: Hiroaki Kawai (was: Rajesh Battala)
Fixed by [~kawai]. Latest KVM run works:
http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/527/testReport/
> KVM DeployVM fails with unable to get answer that is of type StartAnswer
>
>
> Key: CLOUDSTACK-3176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3176
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Assignee: Hiroaki Kawai
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: 434.tar.bz2
>
>
> On the latest master, deploy VM for KVM in advanced zone fails with the
> following exception:
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,596 DEBUG
> [agent.transport.Request] (Job-Executor-99:job-96) Seq 1-1350303926:
> Received: { Ans: , MgmtId: 200973787296321, via: 1, Ver: v1, Flags: 10, {
> Answer } }
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,601 ERROR
> [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-99:job-96) Failed to start
> instance VM[User|eeebdf98-5caf-4c37-a29d-65dcfab5cd1e]
> Jun 24 22:01:57 cloudstack-centos63
> com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is
> of class com.cloud.agent.api.StartAnswer
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:880)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:239)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3308)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask.run(FutureTask.java:166)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jun 24 22:01:57 cloudstack-centos63 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] [Assigned] (CLOUDSTACK-3184) updatevirtual machine api gives java NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Tripathi reassigned CLOUDSTACK-3184:
---
Assignee: Sanjay Tripathi
> updatevirtual machine api gives java NPE
>
>
> Key: CLOUDSTACK-3184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3184
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: build:
> CloudPlatform-4.2-117-rhel6.3
>Reporter: shweta agarwal
>Assignee: Sanjay Tripathi
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Repro steps:
> 1.Create a VM
> 2.Stop the VM
> 3.Call Update Virtual machine API
> Bug:
> Hitting java NPE as soon as calling update virtual machine api
> MS log snippet :
> 2013-06-25 14:19:01,179 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 10.147.59.212 -- GET
> apiKey=zU9ue1DN5vmeJW1FukFqGAXZinL5LM55YemhbQmX9dOiSf9C4nCx6nzPH7lcIIoxnqbKi7qOLU1OmcmPWTzCfw&command=updateVirtualMachine&id=9184d82e-916e-4651-b069-c2a12d757592&response=json&signature=NNrooPcd3nYvYj6Iqxz9SFLK7x4%3D
> 2013-06-25 14:19:01,223 ERROR [cloud.api.ApiServer] (catalina-exec-15:null)
> unhandled exception executing api command: updateVirtualMachine
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.updateVirtualMachine(UserVmManagerImpl.java:1776)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.UpdateVMCmd.execute(UpdateVMCmd.java:130)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
> 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:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-06-25 14:19:01,227 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===END=== 10.147.59.212 -- GET
> apiKey=zU9ue1DN5vmeJW1FukFqGAXZinL5LM55YemhbQmX9dOiSf9C4nCx6nzPH7lcIIoxnqbKi7qOLU1OmcmPWTzCfw&command=updateVirtualMachine&id=9184d82e-916e-4651-b069-c2a12d757592&response=json&signature=NNrooPcd3nYvYj6Iqxz9SFLK7x4%3D
> 2013-06-25 14:19:01,934 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-9:null) SeqA 8-51555: Processing Seq 8-51555: { Cmd ,
> MgmtId: -1, via: 8, Ver: v1, Flags: 11,
> [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":4,"_loadInfo":"{\n
> \"connections\": []\n}","wait":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-3176) KVM DeployVM fails with unable to get answer that is of type StartAnswer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala resolved CLOUDSTACK-3176.
Resolution: Fixed
verified that commit f706f6757cdfcfb3fb9a288ea88e9796bc1e82d0 done by Hiroaki
Kawai is fixing the issue
> KVM DeployVM fails with unable to get answer that is of type StartAnswer
>
>
> Key: CLOUDSTACK-3176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3176
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Assignee: Rajesh Battala
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: 434.tar.bz2
>
>
> On the latest master, deploy VM for KVM in advanced zone fails with the
> following exception:
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,596 DEBUG
> [agent.transport.Request] (Job-Executor-99:job-96) Seq 1-1350303926:
> Received: { Ans: , MgmtId: 200973787296321, via: 1, Ver: v1, Flags: 10, {
> Answer } }
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,601 ERROR
> [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-99:job-96) Failed to start
> instance VM[User|eeebdf98-5caf-4c37-a29d-65dcfab5cd1e]
> Jun 24 22:01:57 cloudstack-centos63
> com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is
> of class com.cloud.agent.api.StartAnswer
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:880)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:239)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3308)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask.run(FutureTask.java:166)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jun 24 22:01:57 cloudstack-centos63 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] [Updated] (CLOUDSTACK-3150) [Dedicated_Resources] Host is going to avoid set while deploying a VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava updated CLOUDSTACK-3150:
---
Component/s: UI
> [Dedicated_Resources] Host is going to avoid set while deploying a VM
> --
>
> Key: CLOUDSTACK-3150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3150
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup, UI
>Affects Versions: 4.2.0
> Environment: Latest build from master-6-17-stable branch
>Reporter: Sanjeev N
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Host is going to avoid set while deploying a VM
> Steps to Reproduce:
>
> 1.Bring up CS with only one host and one cluster in the zone
> 2.Wait for the system vms to come up
> 3.After the default CentOS template is in Ready state try to deploy guest vm
> with default Compute Offering(Small)
> Expected Result:
> ==
> VM deployment should succeed.
> Actual Result:
> ===
> VM deployment failed
> Observations:
> ===
> After the system vms are up host automatically went into to Dedicated state.
> So the FirstFitAllocator is not finding any suitable host to deploy the vm
> since this is host is in avoid set.
> Following is the log snippet:
> 2013-06-24 11:05:34,664 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-21:null) submit async job-23, details: AsyncJobVO {id:23,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 9, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"BUwec1jIHiTD3QZHDFe8xdXLerc\u003d","ctxUserId":"2","serviceOfferingId":"2e01eb93-32b9-4006-819d-5ec0fbb56010","httpmethod":"GET","securitygroupids":"a05e80b0-daa2-11e2-bb94-06ab465f","zoneId":"9633b3cf-ee80-415c-8e66-0dd1ab70d466","templateId":"3b266e5f-339a-4c65-b704-d10211f736e8","response":"json","id":"9","hypervisor":"XenServer","name":"s1","_":"1372066621056","ctxAccountId":"2","ctxStartEventId":"101","displayname":"s1"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-24 11:05:34,667 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===END=== 10.146.0.20 -- GET
> command=deployVirtualMachine&zoneId=9633b3cf-ee80-415c-8e66-0dd1ab70d466&templateId=3b266e5f-339a-4c65-b704-d10211f736e8&hypervisor=XenServer&serviceOfferingId=2e01eb93-32b9-4006-819d-5ec0fbb56010&securitygroupids=a05e80b0-daa2-11e2-bb94-06ab465f&displayname=s1&name=s1&response=json&sessionkey=BUwec1jIHiTD3QZHDFe8xdXLerc%3D&_=1372066621056
> 2013-06-24 11:05:34,677 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-17:job-23) Executing
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-23
> 2013-06-24 11:05:34,686 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) InfrastructureEntity name
> is:com.cloud.offering.ServiceOffering
> 2013-06-24 11:05:34,690 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.template.VirtualMachineTemplate
> 2013-06-24 11:05:34,693 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.network.security.SecurityGroup
> 2013-06-24 11:05:34,795 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Cannot use this dedicated host Rack1Pod1Host13.
> 2013-06-24 11:05:34,796 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Deploy avoids pods: null, clusters: null, hosts: [5]
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) DeploymentPlanner allocation algorithm:
> com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_691b6f1d@354c0a31
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Trying to allocate a host and storage pools from
> dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Is ROOT volume READY (pool already allocated)?: No
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-17:job-23) Searching all possible resources under this Zone: 1
> 2013-06-24 11:05:34,801 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-17:job-23) Listing clusters in order of aggregate capacity,
> that have (atleast one host with) enough CPU and RAM capaci
[jira] [Commented] (CLOUDSTACK-3150) [Dedicated_Resources] Host is going to avoid set while deploying a VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692983#comment-13692983
]
Saksham Srivastava commented on CLOUDSTACK-3150:
Currently adding host/cluster from UI to CloudStack is also calling the
dedicate API and dedicating the resource. Thus the error.
> [Dedicated_Resources] Host is going to avoid set while deploying a VM
> --
>
> Key: CLOUDSTACK-3150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3150
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.2.0
> Environment: Latest build from master-6-17-stable branch
>Reporter: Sanjeev N
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Host is going to avoid set while deploying a VM
> Steps to Reproduce:
>
> 1.Bring up CS with only one host and one cluster in the zone
> 2.Wait for the system vms to come up
> 3.After the default CentOS template is in Ready state try to deploy guest vm
> with default Compute Offering(Small)
> Expected Result:
> ==
> VM deployment should succeed.
> Actual Result:
> ===
> VM deployment failed
> Observations:
> ===
> After the system vms are up host automatically went into to Dedicated state.
> So the FirstFitAllocator is not finding any suitable host to deploy the vm
> since this is host is in avoid set.
> Following is the log snippet:
> 2013-06-24 11:05:34,664 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-21:null) submit async job-23, details: AsyncJobVO {id:23,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 9, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"BUwec1jIHiTD3QZHDFe8xdXLerc\u003d","ctxUserId":"2","serviceOfferingId":"2e01eb93-32b9-4006-819d-5ec0fbb56010","httpmethod":"GET","securitygroupids":"a05e80b0-daa2-11e2-bb94-06ab465f","zoneId":"9633b3cf-ee80-415c-8e66-0dd1ab70d466","templateId":"3b266e5f-339a-4c65-b704-d10211f736e8","response":"json","id":"9","hypervisor":"XenServer","name":"s1","_":"1372066621056","ctxAccountId":"2","ctxStartEventId":"101","displayname":"s1"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-24 11:05:34,667 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===END=== 10.146.0.20 -- GET
> command=deployVirtualMachine&zoneId=9633b3cf-ee80-415c-8e66-0dd1ab70d466&templateId=3b266e5f-339a-4c65-b704-d10211f736e8&hypervisor=XenServer&serviceOfferingId=2e01eb93-32b9-4006-819d-5ec0fbb56010&securitygroupids=a05e80b0-daa2-11e2-bb94-06ab465f&displayname=s1&name=s1&response=json&sessionkey=BUwec1jIHiTD3QZHDFe8xdXLerc%3D&_=1372066621056
> 2013-06-24 11:05:34,677 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-17:job-23) Executing
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-23
> 2013-06-24 11:05:34,686 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) InfrastructureEntity name
> is:com.cloud.offering.ServiceOffering
> 2013-06-24 11:05:34,690 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.template.VirtualMachineTemplate
> 2013-06-24 11:05:34,693 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-17:job-23) ControlledEntity name
> is:com.cloud.network.security.SecurityGroup
> 2013-06-24 11:05:34,795 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Cannot use this dedicated host Rack1Pod1Host13.
> 2013-06-24 11:05:34,796 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Deploy avoids pods: null, clusters: null, hosts: [5]
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) DeploymentPlanner allocation algorithm:
> com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_691b6f1d@354c0a31
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Trying to allocate a host and storage pools from
> dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-17:job-23) Is ROOT volume READY (pool already allocated)?: No
> 2013-06-24 11:05:34,799 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-17:job-23) Searching all possible resources under this Zone: 1
> 2013-06-24 11:05:34,801
[jira] [Commented] (CLOUDSTACK-3176) KVM DeployVM fails with unable to get answer that is of type StartAnswer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692984#comment-13692984
]
Rajesh Battala commented on CLOUDSTACK-3176:
I had reproduced the issue and replacing the latest
cloud-plugin-hypervisor-kvm-4.2.0-SNAPSHOT.jar build from master head
1fc7aeaaea80e30651a47024cf928ff11fb29e9c is resolving the issue while starting
the vm.
please feel free to open if its reproducible.
> KVM DeployVM fails with unable to get answer that is of type StartAnswer
>
>
> Key: CLOUDSTACK-3176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3176
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Assignee: Rajesh Battala
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: 434.tar.bz2
>
>
> On the latest master, deploy VM for KVM in advanced zone fails with the
> following exception:
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,596 DEBUG
> [agent.transport.Request] (Job-Executor-99:job-96) Seq 1-1350303926:
> Received: { Ans: , MgmtId: 200973787296321, via: 1, Ver: v1, Flags: 10, {
> Answer } }
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,601 ERROR
> [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-99:job-96) Failed to start
> instance VM[User|eeebdf98-5caf-4c37-a29d-65dcfab5cd1e]
> Jun 24 22:01:57 cloudstack-centos63
> com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is
> of class com.cloud.agent.api.StartAnswer
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:880)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:239)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3308)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask.run(FutureTask.java:166)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jun 24 22:01:57 cloudstack-centos63 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] [Updated] (CLOUDSTACK-3193) Remove SecondaryStorageDiscoverer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3193: --- Fix Version/s: 4.2.0 > Remove SecondaryStorageDiscoverer > - > > Key: CLOUDSTACK-3193 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3193 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > Earlier the way secondary storage was discovered was through the > SecondaryStorageDiscoverer calling on the DummySecondaryStorageResource. Right > now, with the object storage merge discovery process is delegated to the > corresponding ImageStoreDriver. > Deprecate the unused discoverer to reduce confusion. -- 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-3193) Remove SecondaryStorageDiscoverer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3193: --- Component/s: Storage Controller > Remove SecondaryStorageDiscoverer > - > > Key: CLOUDSTACK-3193 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3193 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > Earlier the way secondary storage was discovered was through the > SecondaryStorageDiscoverer calling on the DummySecondaryStorageResource. Right > now, with the object storage merge discovery process is delegated to the > corresponding ImageStoreDriver. > Deprecate the unused discoverer to reduce confusion. -- 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-3193) Remove SecondaryStorageDiscoverer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3193: --- Affects Version/s: 4.2.0 > Remove SecondaryStorageDiscoverer > - > > Key: CLOUDSTACK-3193 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3193 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > > Earlier the way secondary storage was discovered was through the > SecondaryStorageDiscoverer calling on the DummySecondaryStorageResource. Right > now, with the object storage merge discovery process is delegated to the > corresponding ImageStoreDriver. > Deprecate the unused discoverer to reduce confusion. -- 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-3193) Remove SecondaryStorageDiscoverer
Prasanna Santhanam created CLOUDSTACK-3193: -- Summary: Remove SecondaryStorageDiscoverer Key: CLOUDSTACK-3193 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3193 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Prasanna Santhanam Priority: Critical Earlier the way secondary storage was discovered was through the SecondaryStorageDiscoverer calling on the DummySecondaryStorageResource. Right now, with the object storage merge discovery process is delegated to the corresponding ImageStoreDriver. Deprecate the unused discoverer to reduce confusion. -- 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-3176) KVM DeployVM fails with unable to get answer that is of type StartAnswer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala reassigned CLOUDSTACK-3176:
--
Assignee: Rajesh Battala
> KVM DeployVM fails with unable to get answer that is of type StartAnswer
>
>
> Key: CLOUDSTACK-3176
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3176
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Assignee: Rajesh Battala
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: 434.tar.bz2
>
>
> On the latest master, deploy VM for KVM in advanced zone fails with the
> following exception:
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,596 DEBUG
> [agent.transport.Request] (Job-Executor-99:job-96) Seq 1-1350303926:
> Received: { Ans: , MgmtId: 200973787296321, via: 1, Ver: v1, Flags: 10, {
> Answer } }
> Jun 24 22:01:57 cloudstack-centos63 local0: 2013-06-25 05:01:57,601 ERROR
> [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-99:job-96) Failed to start
> instance VM[User|eeebdf98-5caf-4c37-a29d-65dcfab5cd1e]
> Jun 24 22:01:57 cloudstack-centos63
> com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that is
> of class com.cloud.agent.api.StartAnswer
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:880)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:239)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3308)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2868)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2854)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jun 24 22:01:57 cloudstack-centos63 at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> Jun 24 22:01:57 cloudstack-centos63 at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.FutureTask.run(FutureTask.java:166)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jun 24 22:01:57 cloudstack-centos63 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jun 24 22:01:57 cloudstack-centos63 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
