[jira] [Updated] (CLOUDSTACK-2823) SystemVMs start fail and have no HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou updated CLOUDSTACK-2823: - Assignee: (was: Marcus Sorensen) Priority: Blocker (was: Critical) > SystemVMs start fail and have no HA > --- > > Key: CLOUDSTACK-2823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: CentOS 6.4, KVM > CloudStack master >Reporter: Wei Zhou >Priority: Blocker > > Host: > [root@cs-kvm015 ~]# virsh version > Compiled against library: libvirt 0.10.2 > Using library: libvirt 0.10.2 > Using API: QEMU 0.10.2 > Running hypervisor: QEMU 0.12.1 > Network: > em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 > (Can not connect outside) > em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.* > Issue descripion > (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, > management) > (2) After I destroyed SystemVM, no new SystemVM will be created automatically. > This issue only exists on master branch > Deploy 4.1 successfully, and SystemVms work well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-2780) primary storage is already mounted but not found in pool-list
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou reopened CLOUDSTACK-2780:
--
> primary storage is already mounted but not found in pool-list
> -
>
> Key: CLOUDSTACK-2780
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2780
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.0.1
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>Priority: Critical
>
> This issue appeared on our testing enviroment with cloudstack 4.0.1 (Ubuntu
> 12.04) , and product platform as well.
> (only on few hosts, most of hosts work well)
> We got the message "Unable to create volume" when deploy a VM.
> (1) In management-server.log
> 2013-05-30 14:36:20,090 DEBUG [agent.transport.Request]
> (AgentManager-Handler-11:null) Seq 3-2021457981: Processing: { Ans: ,
> MgmtId: 345051509349, via: 3, Ver: v1, Flags: 110,
> [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
> com.cloud.utils.exception.CloudRuntimeException\nMessage:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\nStack: com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:394)\n\tat
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:48)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1212)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1031)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:518)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:831)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
> java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
> 2013-05-30 14:36:20,090 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-11:null) Seq 3-2021457981: No more commands found
> 2013-05-30 14:36:20,090 DEBUG [agent.transport.Request]
> (Job-Executor-5:job-2563) Seq 3-2021457981: Received: { Ans: , MgmtId:
> 345051509349, via: 3, Ver: v1, Flags: 110, { CreateAnswer } }
> 2013-05-30 14:36:20,090 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-5:job-2563) Unable to create volume Vol[750|vm=550|ROOT]
> 2013-05-30 14:36:20,095 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-5:job-2563) Unable to contact resource.
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200]
> is unreachable: Unable to create Vol[750|vm=550|ROOT]
> (2) In the host Primary storage is already mounted (just an example):
> [root@cs-kvm015 /]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/mapper/vg0-root 461410320 2592404 435379580 1% /
> tmpfs 8160712 0 8160712 0% /dev/shm
> /dev/sda1 198337 52765135332 29% /boot
> /dev/mapper/vg0-tmp2064208 68648 1890704 4% /tmp
> 192.168.103.1:/storage/cs4x-primary
> 7811748864 466487296 7345261568 6%
> /mnt/7b88eced-fc54-3c9f-808a-a697d6be667c
> But not in libvirt pool list
> [root@cs-kvm015 ~]# virsh pool-list
> Name State Autostart
> -
> 513ae20a-61f9-4f7a-b485-23ddb29e59ae active no
> 7b88eced-fc54-3c9f-808a-a697d6be667c active no
> (should have this line, but have not)
> (3) Workaround:
> Enable Maintenance Mode
> umount /mnt/7b88eced-fc54-3c9f-808a-a697d6be667c
> service cloud-agent restart
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2707) Usage server creates entries very slow for mysql performance degradation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-2707. > Usage server creates entries very slow for mysql performance degradation > > > Key: CLOUDSTACK-2707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2707 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > > As we know, the insert performance into a mysql table degrades when the > records of table reaches 1,000,000. It takes more time and more CPU > utilization. > Here is log in usage.log > 2013-05-27 09:13:24,827 INFO [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) starting usage job... > 2013-05-27 09:13:24,829 INFO [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) Parsing usage records between Mon May 27 11:10:05 CEST > 2013 and Mon May 27 11:13:24 CEST 2013 > 2013-05-27 09:13:25,534 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 1252; abs: 847 > 2013-05-27 09:13:25,534 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 1252; abs: 847; curABS: 847; curABR: 1252; ubs: 0; ubr: 0 > 2013-05-27 09:13:26,467 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 16112; abs: 16112 > 2013-05-27 09:13:26,468 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 16112; abs: 16112; curABS: 16112; curABR: 16112; ubs: 0; ubr: 0 > 2013-05-27 09:13:28,220 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 0; abs: 0 > 2013-05-27 09:13:28,220 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 0; abs: 0; curABS: 0; curABR: 0; ubs: 0; ubr: 0 > 2013-05-27 09:13:29,266 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 3648; abs: 3648 > 2013-05-27 09:13:29,266 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 3648; abs: 3648; curABS: 3648; curABR: 3648; ubs: 0; ubr: 0 > 2013-05-27 09:13:30,339 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 32984; abs: 32984 > 2013-05-27 09:13:30,339 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 32984; abs: 32984; curABS: 32984; curABR: 32984; ubs: 0; ubr: 0 > 2013-05-27 09:13:31,830 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 118636; abs: 118940 > .. > 2013-05-27 09:16:08,285 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 0; abs: 0 > 2013-05-27 09:16:08,285 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 0; abs: 0; curABS: 0; curABR: 0; ubs: 0; ubr: 0 > 2013-05-27 09:16:09,308 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) created network stats helper entries for 134 accts -- 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-685) CloudStack 4.0 Network Usage is ZERO
[
https://issues.apache.org/jira/browse/CLOUDSTACK-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou closed CLOUDSTACK-685.
---
> CloudStack 4.0 Network Usage is ZERO
>
>
> Key: CLOUDSTACK-685
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-685
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
>Affects Versions: 4.0.0
>Reporter: Wei Zhou
>Assignee: Kishan Kavala
> Fix For: 4.0.1
>
>
> Problem description:
> The usage server can give the system usage of each virtual machine (such as
> running time, ServiceOffering, IPAddress, Volume, Template, ISO, Port
> Forwarding Rule, Network offering), except the network bytes sent/received.
> This problem only exists in CloudStack 4.0. In CloudStack 3.0, the usage
> server works well.
> We looked into Iptables of VR, its working fine (look at the output of 10g
> download). This is just a sample.
> root@r-17-VM:/# iptables -nvx -L NETWORK_STATS
> Chain NETWORK_STATS (3 references)
> pkts bytes target prot opt in out source
> destination
> 246477 12943171all -- eth0 eth20.0.0.0/0
> 0.0.0.0/0
> 125789 1008395759all -- eth2 eth00.0.0.0/0
> 0.0.0.0/0
>00tcp -- !eth0 eth20.0.0.0/0
> 0.0.0.0/0
>00tcp -- eth2 !eth0 0.0.0.0/0
> 0.0.0.0/0
> We tried to debug it further & found the following:
> (1) Checked the CloudStack logs
> /var/log/cloud/management/management-server.log
> 2012-12-18 15:05:51,130 DEBUG [agent.transport.Request]
> (AgentManager-Handler-8:null) Seq 1-1158742136: Processing: { Ans: , MgmtId:
> 345051509349, via: 1, Ver: v1, Flags: 10,
> [{"NetworkUsageAnswer":{"routerName":"r-4-VM","bytesSent":5928,"bytesReceived":6188,"result":true,"details":"","wait":0}}]
> }
> 2012-12-18 15:05:51,130 DEBUG [agent.transport.Request]
> (RouterMonitor-1:null) Seq 1-1158742136: Received: { Ans: , MgmtId:
> 345051509349, via: 1, Ver: v1, Flags: 10, { NetworkUsageAnswer } }
> 2012-12-18 15:05:51,130 DEBUG [agent.manager.AgentManagerImpl]
> (RouterMonitor-1:null) Details from executing class
> com.cloud.agent.api.NetworkUsageCommand:
> 2012-12-18 15:05:51,131 WARN
> [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null)
> unable to find stats for account: 2
> We can see that AgentManager works well. It can get the network usage.
> (2) Checked the the database.
> There are 4 tables, cloud.user_statistics, cloud_usage.user_statistics,
> cloud_usage.usage_network and cloud_usage.cloud_usage which is used by API &
> we're trying to filter Network Usage using 'usage_type' 4 or 5
> As we add new network (VR), it adds a row in cloud.user_statistics &
> eventually ends up (could be because of generateUsageRecords API command) in
> other 2 tables ( cloud_usage.user_statistics, cloud_usage.usage_network )
> mysql> select * from cloud.user_statistics;
> ++++---+---+--+++++
> | id | data_center_id | account_id | public_ip_address | device_id |
> device_type | network_id | net_bytes_received | net_bytes_sent |
> current_bytes_received | current
> ++++---+---+--+++++
> | 1 | 1 | 2 | NULL | 4 |
> DomainRouter |204 | 0 | 0 |
> 0 |
> | 2 | 1 | 2 | NULL | 6 |
> DomainRouter |205 | 0 | 0 |
> 0 |
> ++++---+---+--+++++
> (3) Checked the source code.
> (a)
> /cloud-server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java
> ( I have deleted some unrelated source codes)
> public void run() {
> for (DomainRouterVO router : routers) {
> String privateIP = router.getPrivateIpAddress(); // from
> domain_router table (id=4, name=r-4-VM,
> vm_instance.private_ip_address=169.254.1.17)
> if (privateIP != null) {
> List routerNics =
> _nicDao.listByVmId(router.getId()); // from nics table (instance_id=4).
> Found 3 records. Return (networkid= 204/202/200)
> for (Nic routerNic : routerNics) {
>
[jira] [Closed] (CLOUDSTACK-1325) restoreVirtualMachine returns no password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1325. > restoreVirtualMachine returns no password > - > > Key: CLOUDSTACK-1325 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1325 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: hypervisor: Ubuntu 12.04 (64-bit) > CloudStack 4.0.1 > Guest OS: Ubuntu 10.04 (64-bit) >Reporter: Wei Zhou >Assignee: Wei Zhou > > We just had a test on restoreVirtualMachine. no password is returned. > To reproduce: > (1) run > command=restoreVirtualMachine&response=json&virtualmachineid=1a53a308-c870-452a-9eff-23975919286b > > (2) query > command=queryAsyncJobResult&response=json&jobid=77c60ca2-8b14-4a14-9449-7855c5e67fff > passwordenabled is true, but no password is returned. I can not log in the > virtual machine using the old password. > (3) workaround > command=resetPasswordForVirtualMachine&id=1a53a308-c870-452a-9eff-23975919286b > > will restart the virtual machine and set a new password. I can log in the > virtual machine using this password > Hope the guys working on CLOUDSTACK-667 (VM's base image update facility) can > consider this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1192) Add disk I/O polling to statistics accounting of Instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1192. > Add disk I/O polling to statistics accounting of Instances > -- > > Key: CLOUDSTACK-1192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1192 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, Usage >Affects Versions: 4.2.0 >Reporter: Wido den Hollander >Assignee: Wei Zhou > Labels: I/O, IOps > Fix For: 4.2.0 > > > In public clouds (and also private ones) it's important to know how much disk > I/O each Instance is consuming. > Today disk I/O is more expensive then RAM, CPU and Network bandwith, but > CloudStack has no way of accounting this. > CloudStack should collect the disk I/O statistics of all running instances so > we can present these in the UI and in the Usage server > The wiki page for this improvement: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disk+IO+statistics+for+instances -- 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-1192) Add disk I/O polling to statistics accounting of Instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-1192. -- Resolution: Implemented > Add disk I/O polling to statistics accounting of Instances > -- > > Key: CLOUDSTACK-1192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1192 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, Usage >Affects Versions: 4.2.0 >Reporter: Wido den Hollander >Assignee: Wei Zhou > Labels: I/O, IOps > Fix For: 4.2.0 > > > In public clouds (and also private ones) it's important to know how much disk > I/O each Instance is consuming. > Today disk I/O is more expensive then RAM, CPU and Network bandwith, but > CloudStack has no way of accounting this. > CloudStack should collect the disk I/O statistics of all running instances so > we can present these in the UI and in the Usage server > The wiki page for this improvement: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disk+IO+statistics+for+instances -- 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-2857) DestroyVMCmd throwing NPE when vm is in Error state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-2857. > DestroyVMCmd throwing NPE when vm is in Error state > --- > > Key: CLOUDSTACK-2857 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2857 > 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: Wei Zhou >Priority: Minor > Fix For: 4.2.0 > > Attachments: logs.rar > > > when vm is in error state DestroyVMCmd throwing NPE > Step to reproduce > -- > 1-set GP "pool.storage.allocated.capacity.disablethreshold" to some low value; > 2-Try to deploy a vm > 3-vm deploy will fail because of step 1 , and vm will go in error state > Log > --- > 2013-06-05 12:54:51,778 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-4:job-20) Executing > org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-20 > 2013-06-05 12:54:51,851 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-4:job-20) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.DestroyVMCmd > java.lang.NullPointerException > at > com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3427) > at > com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3383) > at > com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:1897) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:100) > 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-05 12:54:51,853 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-4:job-20) Complete async job-20, jobStatus: 2, resultCode: 530, > result: Error Code: 530 Error text: null -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1211) Network operations are Blocked for the Read-only file system of Virtual Router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1211. > Network operations are Blocked for the Read-only file system of Virtual Router > -- > > Key: CLOUDSTACK-1211 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1211 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.0.2 > > > Sometimes the virtual router VM has read-only file system for some reasons, > such as the Abnormal shutdown of the Host. This is not that we expected, but > really happens. > When this happens, the network operations will receive error messages and > fail. But indeed it is not. For example, > (1) Acquire IP. always in "Allocating" state. > (2) EnableStaticNat, the result is success(it is incorrect). > (3) DisableStaticNat. This is correct. > (4) Add Firewalls. always in "Adding" state. > Furthermore, The AgentManager report statistics every 60 minutes(normally it > should be router.stats.interval=5 minutes). > The agent.log show this after restart cloud-mnagement: > 2013-02-08 08:02:12,612 WARN [kvm.resource.LibvirtComputingResource] > (Script-6:null) Interrupting script. > 2013-02-08 08:02:12,614 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Timed out: > /usr/lib/cloud/common/scripts/network/domr/router_proxy.sh netusage.sh > 169.254.0.151 -g . Output is: /root/func.sh: line 44: > /tmp/biglock-31028.lock: Permission deniedls: cannot access > /tmp/biglock-*.lock: No such file or directory/root/func.sh: line 49: [: -ef: > unary operator expectedls: cannot access /tmp/biglock-*.lock: No such file or > directory/root/func.sh: line 49: [: -ef: unary operator expected > .. > 2013-02-08 10:44:18,925 INFO [cloud.agent.Agent] (Agent-Handler-3:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-02-08 10:44:18,926 INFO [cloud.agent.Agent] (Agent-Handler-3:null) > Cannot connect because we still have 3 commands in progress. > To reproduce > (1) log in the virtual router from console, or ssh from host. > (2) to generate errors, use "chattr =i -R /tmp" > (3) to remove errors, use "chattr -i -R /tmp" -- 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-2856) NPE is seen when a guest vm is stopped first and then destroyed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou closed CLOUDSTACK-2856.
> NPE is seen when a guest vm is stopped first and then destroyed
> ---
>
> Key: CLOUDSTACK-2856
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2856
> 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: Abhinav Roy
>Assignee: Wei Zhou
> Fix For: 4.2.0
>
> Attachments: apilog.log, management-server.log
>
>
> Steps :
>
> 1. Deploy a guest VM.
> 2. Stop the VM.
> 3. Destroy the VM.
> Expected behaviour :
>
> 1. The VM should be successfully destroyed.
> Observed behaviour :
> ===
> NPE is thrown when the VM is destroyed.
> 2013-06-05 17:03:49,778 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-25:null) submit async job-52, details: AsyncJobVO {id:52,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 9, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"cd351199-941e-4d66-b1c4-f31202d32b92","sessionkey":"1uDZqKxOwYgif6jtyJvQ+aQdIM0\u003d","ctxUserId":"2","httpmethod":"GET","_":"1370431837633","ctxAccountId":"2","ctxStartEventId":"194"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-05 17:03:49,780 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
> ===END=== 10.144.7.12 -- GET
> command=destroyVirtualMachine&id=cd351199-941e-4d66-b1c4-f31202d32b92&response=json&sessionkey=1uDZqKxOwYgif6jtyJvQ%2BaQdIM0%3D&_=1370431837633
> 2013-06-05 17:03:49,782 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-25:job-52) Executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-52
> 2013-06-05 17:03:49,812 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-25:job-52) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3427)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3383)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:1897)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:100)
> 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-05 17:03:49,813 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-25:job-52) Complete async job-52, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: null
> 2013-06-05 17:03:51,443 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 5 routers to update status.
> NOTE :
> ==
> This behaviour is not seen when the VM is destroyed directly without stopping
> it.
--
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-2856) NPE is seen when a guest vm is stopped first and then destroyed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou resolved CLOUDSTACK-2856.
--
Resolution: Fixed
> NPE is seen when a guest vm is stopped first and then destroyed
> ---
>
> Key: CLOUDSTACK-2856
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2856
> 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: Abhinav Roy
>Assignee: Wei Zhou
> Fix For: 4.2.0
>
> Attachments: apilog.log, management-server.log
>
>
> Steps :
>
> 1. Deploy a guest VM.
> 2. Stop the VM.
> 3. Destroy the VM.
> Expected behaviour :
>
> 1. The VM should be successfully destroyed.
> Observed behaviour :
> ===
> NPE is thrown when the VM is destroyed.
> 2013-06-05 17:03:49,778 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-25:null) submit async job-52, details: AsyncJobVO {id:52,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 9, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"cd351199-941e-4d66-b1c4-f31202d32b92","sessionkey":"1uDZqKxOwYgif6jtyJvQ+aQdIM0\u003d","ctxUserId":"2","httpmethod":"GET","_":"1370431837633","ctxAccountId":"2","ctxStartEventId":"194"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90310994128556,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-05 17:03:49,780 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
> ===END=== 10.144.7.12 -- GET
> command=destroyVirtualMachine&id=cd351199-941e-4d66-b1c4-f31202d32b92&response=json&sessionkey=1uDZqKxOwYgif6jtyJvQ%2BaQdIM0%3D&_=1370431837633
> 2013-06-05 17:03:49,782 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-25:job-52) Executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-52
> 2013-06-05 17:03:49,812 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-25:job-52) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3427)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3383)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:1897)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:100)
> 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-05 17:03:49,813 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-25:job-52) Complete async job-52, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: null
> 2013-06-05 17:03:51,443 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 5 routers to update status.
> NOTE :
> ==
> This behaviour is not seen when the VM is destroyed directly without stopping
> it.
--
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-1652) /etc/hosts error in virtual router when deploy instance with the name same to previous instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1652. > /etc/hosts error in virtual router when deploy instance with the name same to > previous instances > > > Key: CLOUDSTACK-1652 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1652 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.1 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.0.2 > > > When create the instance with the name same to previous instances, the > /etc/hosts in virtual router has an error. > For example: > 192.168.0.1 r-148-VM > 192.168.0.1 r-148-VM > 192.168.0.99 test-w006-001 > 192.168.0.138 test-w006-002 > 192.168.0.37 test-w006-003 > 192.168.0.33 test-w006-004 > 192.168.0.1 r-148-VM > 192.168.0.235 test-w006-001 > 192.168.0.17 test-w006-002 > It should be: > 192.168.0.37 test-w006-003 > 192.168.0.33 test-w006-004 > 192.168.0.1 r-148-VM > 192.168.0.235 test-w006-001 > 192.168.0.17 test-w006-002 -- 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-1683) two ExpungeTask are running
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1683. > two ExpungeTask are running > --- > > Key: CLOUDSTACK-1683 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1683 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.1 >Reporter: Wei Zhou >Assignee: Wei Zhou > > There are two ExpungeTask running in cloudstack. > one is from UserVmManagerImpl, the _expungeInterval is max(expunge.interval, > 600), > the other one is from BareMetalVmManagerImpl, the _expungeInterval is > expunge.interval. > Only one thread should be running, and the _expungeInterval should be set to > max(expunge.interval, 600). -- 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-512) remove hostname in a virtual router's DNS service, after expunging VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-512. --- > remove hostname in a virtual router's DNS service, after expunging VM > - > > Key: CLOUDSTACK-512 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-512 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Choonho Son >Assignee: Wei Zhou > > The domain name of guest VM is not deleted, even though the guest VM is > expunged. > Scenario: > 1. Deploy VirtualMachine with hostname "head1" > 2. Delete "head1" VirtualMachine > 3. Deploy VirtualMachine with hostname "head1" > 4. Delete "head1" VirtualMachine > ... > After repeating this process, ask ip address of "head1" > nslookup head1 > The result looks like > [root@repo src-conf]# nslookup head1 > Server: 172.27.0.1 > Address:172.27.0.1#53 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.114.224 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.110.235 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.182.109 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.76.251 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.196.212 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.116.53 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.35.214 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.248.170 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.33.158 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.116.64 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.71.218 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.65.181 > Problem: > - Other guest VM cannot connect "head1" VM using domain name, > - Because only one IP address is valid. > -- 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-2891) Management server gets stuck when we try to add only a single vlan as a range , ex- try to add 615-615
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-2891. Resolution: Fixed > Management server gets stuck when we try to add only a single vlan as a range > , ex- try to add 615-615 > -- > > Key: CLOUDSTACK-2891 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2891 > 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: Abhinav Roy >Assignee: Likitha Shetty >Priority: Critical > Fix For: 4.2.0 > > > Steps : > = > 1. Deploy a CS setup with advanced network zone. > 2. Goto Infrastructure -> Zone -> Zone-1 -> Physical Network -> Guest and try > to add a vlan range like 100-100 or 200-200 or anything like that > or > Fire this api : > http://10.102.192.125:8096/client/api?command=updatePhysicalNetwork&id=200&vlan=100-100 > Observed behaviour : > > 1. The UI gets stuck and we need to restart management server to get it to a > working state. > 2. In the Logs the queryAsyncJobResult API keeps querying the job for a very > long time. -- 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-2891) Management server gets stuck when we try to add only a single vlan as a range , ex- try to add 615-615
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680252#comment-13680252 ] ASF subversion and git services commented on CLOUDSTACK-2891: - Commit 7b63894a0a2226c16de6ce2eaa5aa6f62746026c in branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7b63894 ] CLOUDSTACK-2891. While adding a new vlan range if the new range extends an existing range then CS extends the existing range to include the new range. This is done by checking if the last vlan in the new range is same as the start vlan of any existing range. Since for a single vlan the start and the end vlan are the same the check goes to an infinite loop resulting in a java.lang.OutOfMemoryError: Java heap space error. Remove the check for a single vlan because if an existing range starts with the single vlan then it implies that the range already exists > Management server gets stuck when we try to add only a single vlan as a range > , ex- try to add 615-615 > -- > > Key: CLOUDSTACK-2891 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2891 > 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: Abhinav Roy >Assignee: Likitha Shetty >Priority: Critical > Fix For: 4.2.0 > > > Steps : > = > 1. Deploy a CS setup with advanced network zone. > 2. Goto Infrastructure -> Zone -> Zone-1 -> Physical Network -> Guest and try > to add a vlan range like 100-100 or 200-200 or anything like that > or > Fire this api : > http://10.102.192.125:8096/client/api?command=updatePhysicalNetwork&id=200&vlan=100-100 > Observed behaviour : > > 1. The UI gets stuck and we need to restart management server to get it to a > working state. > 2. In the Logs the queryAsyncJobResult API keeps querying the job for a very > long time. -- 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-2702) unable to install XenServer Support Package (CSP) on Xen cloud platform 1.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680251#comment-13680251 ] Ryan Lei - Taiwan commented on CLOUDSTACK-2702: --- I tried CloudStack 4.1 (community RPMs) + XCP 1.6 (with xe-switch-network-backend bridge) + Basic Zone today. Unfortunately, Security Groups did not work out of the box. It behaved like ALLOW-ALL for in/out traffic. At least I can SSH into guest VM before adding any SG rules. Can I conclude that before there's a support package for XCP, Security Groups cannot work on XCP, even for previous versions? In that case, XCP would not be as supported as XenServer. :( > unable to install XenServer Support Package (CSP) on Xen cloud platform 1.6 > --- > > Key: CLOUDSTACK-2702 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2702 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Xen >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: Xen Cloud Platform 1.6 >Reporter: Dean Kamali > Labels: xen, xenserver > > To enable security groups, elastic load balancing, and elastic IP on > XenServer, We need to install CloudStack XenServer Support Package (CSP). > After installing Xen cloud platform Server. > I'm getting an error, when I try to install the package. > xe-install-supplemental-pack xenserver-cloud-supp.iso > Error repository is not compatible with the installed product (xenserver > expected), Do you want to continue? (Y/N)? > When I answer with Y > FATAL: missing dependency xs:main -- 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-743) Integrate Cisco VSG in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-743: --- Fix Version/s: (was: 4.2.0) Future > Integrate Cisco VSG in CloudStack > - > > Key: CLOUDSTACK-743 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-743 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Koushik Das > Fix For: Future > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integrate+Cisco+Virtual+Security+Gateway+%28VSG%29+into+CloudStack > Requirements discussion email thread link: -- 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-743) Integrate Cisco VSG in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680250#comment-13680250 ] Koushik Das commented on CLOUDSTACK-743: This was not done for 4.2. Moving this out of 4.2. In future if there is a need to do this thne need to revisit. > Integrate Cisco VSG in CloudStack > - > > Key: CLOUDSTACK-743 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-743 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Koushik Das > Fix For: 4.2.0 > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integrate+Cisco+Virtual+Security+Gateway+%28VSG%29+into+CloudStack > Requirements discussion email thread link: -- 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-2928) [VPC][ACL]ListACL dropdown is not listing defaultACLs while creating the tier network/replacing the ACL for tier
manasaveloori created CLOUDSTACK-2928: - Summary: [VPC][ACL]ListACL dropdown is not listing defaultACLs while creating the tier network/replacing the ACL for tier Key: CLOUDSTACK-2928 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2928 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: manasaveloori Fix For: 4.2.0 steps: 1. Have CS with advanced zone. 2. Create a VPC 3. Create a tier . Observation: While creating the tier,the API passed for list ACL is http://10.147.38.154:8080/client/api?command=listNetworkACLLists&vpcid=3d104d3d-2c5f-422e-b4fc-ae192b552d48&response=json&sessionkey=ydkJIe0pKVxfZP3S8wS9PfFTNjY%3D&_=1370932313421 which lists nothing as the parameter name vpcid should be “vpc_id” The same is observed while replacing the ACL for a tier. -- 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-2729) [Automation] Libvirt failed find primary storage and VM deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680249#comment-13680249
]
Wei Zhou commented on CLOUDSTACK-2729:
--
Rayees,
Can you mount primary/secondary storage manually?
-Wei
> [Automation] Libvirt failed find primary storage and VM deployment failed
>
>
> Key: CLOUDSTACK-2729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2729
> 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
> Environment: Master branch build
> Automation environment - KVM
>Reporter: Rayees Namathponnan
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2729.rar
>
>
> Failed to deploy VM in automation, environment created with , 2 hosts and 2
> primary storages in a cluster
> 1) /export/home/rayees/SC_QA_AUTO4/primary2
> 2) /export/home/rayees/SC_QA_AUTO4/primary
> Libvirt failed to find the primary storage
> /export/home/rayees/SC_QA_AUTO4/primary and VM deployment failed
> MS log
> 2013-05-28 21:11:44,540 DEBUG [agent.transport.Request] (consoleproxy-1:null)
> Seq 4-936706756: Sending { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1,
> Flags: 100111,
> [{"StartCommand":{"vm":{"id":29,"name":"v-29-QA","type":"ConsoleProxy","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP type=consoleproxy
> host=10.223.49.195 port=8250 name=v-29-QA premium=true zone=1 pod=1
> guid=Proxy.29 proxy_vm=29 disable_rp_filter=true eth2ip=10.223.122.73
> eth2mask=255.255.255.192 gateway=10.223.122.65 eth0ip=169.254.0.154
> eth0mask=255.255.0.0 eth1ip=10.223.50.96 eth1mask=255.255.255.192
> mgmtcidr=10.223.49.192/26 localgw=10.223.50.65 internaldns1=10.223.110.254
> dns1=72.52.126.11","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"d099568827911cef","params":{},"uuid":"5a146833-6a8c-44e5-83c0-50f34accf513","disks":[{"id":32,"name":"ROOT-29","mountPoint":"/export/home/rayees/SC_QA_AUTO4/primary","path":"f6f8d865-e9c0-4188-8a33-6c6383ca5075","size":276406784,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","deviceId":0}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"uuid":"21175978-96bd-4160-8228-8ad15aa40c66","ip":"10.223.122.73","netmask":"255.255.255.192","gateway":"10.223.122.65","mac":"06:2e:5a:00:00:42","dns1":"72.52.126.11","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://1221","isolationUri":"vlan://1221","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"e0651452-a76e-4564-96b2-3d5d51e9bcd6","ip":"169.254.0.154","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:00:9a","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"0765c229-468e-4dfd-8382-24ac49791a8d","ip":"10.223.50.96","netmask":"255.255.255.192","gateway":"10.223.50.65","mac":"06:a8:e8:00:00:1d","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false}]},"hostIp":"10.223.50.66","wait":0}},{"check.CheckSshCommand":{"ip":"169.254.0.154","port":3922,"interval":6,"retries":100,"name":"v-29-QA","wait":0}}]
> }
> 2013-05-28 21:11:44,552 DEBUG [agent.transport.Request]
> (AgentManager-Handler-1:null) Seq 4-936706756: Processing: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 110,
> [{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:380)\n\tat
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:72)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3399)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3293)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1187)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
>
> java.lang.Thre
[jira] [Resolved] (CLOUDSTACK-658) Scaling up CPU and RAM for running VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-658. Resolution: Fixed > Scaling up CPU and RAM for running VMs > -- > > Key: CLOUDSTACK-658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-658 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Koushik Das >Assignee: Nitin Mehta > Fix For: 4.2.0 > > > Currently CS supports changing CPU and RAM for stopped VM. This is achieved > by changing compute offering of the VM (with new CPU and RAM values) and then > starting it. I am planning to extend the same for running VM as well. > Initially planning to do it for Vmware where CPU and RAM can be dynamically > increased. Support of other HVs can also be added if they support increasing > CPU/RAM. > Assuming that in the updated compute offering only CPU and RAM has changed, > the deployment planner can either select the same host in which case the > values are dynamically scaled up OR a different one in which case the > operation fails. In future if there is support for live migration (provided > HV supports it) then another option in the latter case could be to migrate > the VM first and then scale it up. > Release Planning: > Dev list discussion: http://markmail.org/message/ocdt62utijeyxikc > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+scaling+of+CPU+and+RAM > Feature branch: unknown -- 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-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-2927: --- Attachment: awsapi.log > [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error > --- > > Key: CLOUDSTACK-2927 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0 >Reporter: Likitha Shetty > Fix For: 4.2.0 > > Attachments: awsapi.log > > > Set enable.ec2.api to true. > Register user using cloudstack-aws-api-register. > Make any SOAP API call e.g. ec2-describe-images using ec2 tools. > Output - Server.InternalError: An unexpected error occurred > Attached awsapi.log for log details > -- 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-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
Likitha Shetty created CLOUDSTACK-2927: -- Summary: [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error Key: CLOUDSTACK-2927 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Likitha Shetty Fix For: 4.2.0 Attachments: awsapi.log Set enable.ec2.api to true. Register user using cloudstack-aws-api-register. Make any SOAP API call e.g. ec2-describe-images using ec2 tools. Output - Server.InternalError: An unexpected error occurred Attached awsapi.log for log details -- 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-2604) [Multiple IpsPerNic] Unable to removeIpFromNic even when there are no PF rules associated with it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-2604. --- Resolution: Fixed > [Multiple IpsPerNic] Unable to removeIpFromNic even when there are no PF > rules associated with it > -- > > Key: CLOUDSTACK-2604 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2604 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 85d54cd1c088997dd08f0328984bee1a55703636 >Reporter: venkata swamybabu budumuru >Assignee: Jayapal Reddy > Labels: integration-test > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce : > 1. Have latest CloudStack setup with at least 1 advanced zone having KVM > cluster with 1 host. > 2. Have a non-ROOT domain user > 3. Login as the above user and try to deploy a VM with two nics > NIC1 : (eth0) => Network1 (10.1.1.0/24) > NIC2 : (eth1) => Network2 (10.1.1.0/24) > - by default, in my case it got the following primary IPs > > NIC1 - 10.1.1.233 > NIC2 - 10.1.1.241 > 4. acquired (addIpToNic) a secondary IP on NIC1 > NIC1 => First secondary IP : 10.1.1.29 > 5. acquired another secondary IP on NIC1 > NIC1 => another secondary IP : 10.1.1.121 > 6. acquired the same secondary IP on NIC2 as well > NIC2 => secondary IP : 10.1.1.121 > 7. Create a PF rule along with firewall rule on the Network2 public IP which > maps to the NIC2 secondary IP > create portforwardingrule > virtualmachineid=a44ca6c5-ff25-4934-842d-2401b9325076 > ipaddressid=b167c584-3ab4-4575-b812-9ed8e13f5040 openfirewall=true > vmguestip=10.1.1.121 privateendport=22 privateport=22 publicport= > publicendport= protocol=tcp > 8. Try to remove the second secondary IP on NIC1 which has no rules > associated with it. > Observations: > (i) Snapshot of the relevant tables from DB >id: 216 > name: Network2 > uuid: 23d1de85-18c0-481e-9e9a-cc77e23157c9 > display_text: Network2 > traffic_type: Guest > broadcast_domain_type: Vlan > broadcast_uri: vlan://904 > gateway: 10.1.1.1 > cidr: 10.1.1.0/24 > mode: Dhcp > network_offering_id: 8 > physical_network_id: 202 >data_center_id: 3 > guru_name: ExternalGuestNetworkGuru > state: Implemented > related: 216 > domain_id: 2 >account_id: 4 > dns1: NULL > dns2: NULL > guru_data: NULL >set_fields: 0 > acl_type: Account >network_domain: cs4cloud.internal >reservation_id: NULL >guest_type: Isolated > restart_required: 0 > created: 2013-05-21 11:27:17 > removed: NULL > specify_ip_ranges: 0 >vpc_id: NULL > ip6_gateway: NULL > ip6_cidr: NULL > network_cidr: NULL > display_network: 1 >network_acl_id: NULL > mysql> select * from networks where id=214\G > *** 1. row *** >id: 214 > name: Network1 > uuid: 3bc9f5eb-d77f-4308-8353-ff9f86dfd7d9 > display_text: Network1 > traffic_type: Guest > broadcast_domain_type: Vlan > broadcast_uri: vlan://900 > gateway: 10.1.1.1 > cidr: 10.1.1.0/24 > mode: Dhcp > network_offering_id: 8 > physical_network_id: 202 >data_center_id: 3 > guru_name: ExternalGuestNetworkGuru > state: Implemented > related: 214 > domain_id: 2 >account_id: 4 > dns1: 10.103.128.16 > dns2: NULL > guru_data: NULL >set_fields: 0 > acl_type: Account >network_domain: cs4cloud.internal >reservation_id: d5673437-8149-4dad-bf0b-5435e6d6711d >guest_type: Isolated > restart_required: 0 > created: 2013-05-21 09:16:41 > removed: NULL > specify_ip_ranges: 0 >vpc_id: NULL > ip6_gateway: NULL > ip6_cidr: NULL > network_cidr: NULL > display_network: 1 >network_acl_id: NULL > mysql> select * from port_forwarding_rules; > ++-+-+-+---+ > | id | instance_id | dest_ip_address | dest_port_start | dest_port_end | > ++-+-+--
[jira] [Resolved] (CLOUDSTACK-2862) CS AWSAPI SOAP calls fail with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-2862. Resolution: Fixed > CS AWSAPI SOAP calls fail with NPE > -- > > Key: CLOUDSTACK-2862 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2862 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Enable ec2 api flag. Use EC2 API Soap tool to run > ec2-describe-availability-zones. > Ouput - Server:unknown > Contents of awsapi.log - > 2013-05-28 15:53:53,127 WARN [controller.s3.ServiceProvider] > (catalina-exec-int-6:null) Unhandled exception null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > com.cloud.bridge.service.controller.s3.ServiceProvider$2.invoke(ServiceProvider.java:356) > at $Proxy67.describeAvailabilityZones(Unknown Source) > at > com.cloud.bridge.service.EC2SoapService.describeAvailabilityZones(EC2SoapService.java:230) > at > com.amazon.ec2.AmazonEC2MessageReceiverInOut.invokeBusinessLogic(AmazonEC2MessageReceiverInOut.java:874) > at > org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) > at > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) > at > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) > at > com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:114) > at > com.cloud.bridge.service.EC2MainServlet.doPost(EC2MainServlet.java:89) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2260) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > Caused by: java.lang.NullPointerException > at > com.cloud.bridge.service.EC2SoapServiceImpl.describeAvailabilityZones
[jira] [Commented] (CLOUDSTACK-2862) CS AWSAPI SOAP calls fail with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680221#comment-13680221 ] ASF subversion and git services commented on CLOUDSTACK-2862: - Commit bbfa9bfcbde78675a2aecb3736f76f11373f6084 in branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bbfa9bf ] CLOUDSTACK-2862. EC2Engine is not injected correctly > CS AWSAPI SOAP calls fail with NPE > -- > > Key: CLOUDSTACK-2862 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2862 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Enable ec2 api flag. Use EC2 API Soap tool to run > ec2-describe-availability-zones. > Ouput - Server:unknown > Contents of awsapi.log - > 2013-05-28 15:53:53,127 WARN [controller.s3.ServiceProvider] > (catalina-exec-int-6:null) Unhandled exception null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > com.cloud.bridge.service.controller.s3.ServiceProvider$2.invoke(ServiceProvider.java:356) > at $Proxy67.describeAvailabilityZones(Unknown Source) > at > com.cloud.bridge.service.EC2SoapService.describeAvailabilityZones(EC2SoapService.java:230) > at > com.amazon.ec2.AmazonEC2MessageReceiverInOut.invokeBusinessLogic(AmazonEC2MessageReceiverInOut.java:874) > at > org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) > at > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) > at > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) > at > com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:114) > at > com.cloud.bridge.service.EC2MainServlet.doPost(EC2MainServlet.java:89) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2260) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadP
[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=13680219#comment-13680219 ] Animesh Chaturvedi commented on CLOUDSTACK-212: --- Dharmesh are you planning this for 4.2? > 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] [Resolved] (CLOUDSTACK-2650) [Multiple IPs PerNic] disassociating public IP should clean cloud.user_ip_address.dnat_vmip
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-2650. --- Resolution: Fixed > [Multiple IPs PerNic] disassociating public IP should clean > cloud.user_ip_address.dnat_vmip > --- > > Key: CLOUDSTACK-2650 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2650 > 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: venkata swamybabu budumuru >Assignee: Jayapal Reddy >Priority: Minor > Fix For: 4.2.0 > > > Steps to reproduce : > 1. Have at least one CloudStack with advanced zone using KVM cluster > 2. Have at least one non-ROOT domain user > 3. deploy a VM using an isolated network. > 4. Acquire a public ip and enable static nat to secondary ip > 5. disassociated public ip > Observations: > - Disassociate public ip went fine but, it didnt clean dnat_vmip from the > cloud.user_ip_address table. > Here is the snippet of DB table. > mysql> select * from user_ip_address where public_ip_address like '%44.84%'\G > *** 1. row *** > id: 25 >uuid: 1969d567-20d6-4dd8-b879-5a81291463a6 > account_id: NULL > domain_id: NULL > public_ip_address: 10.147.44.84 > data_center_id: 3 > source_nat: 0 > allocated: NULL > vlan_db_id: 3 > one_to_one_nat: 0 > vm_id: NULL > state: Free > mac_address: 15 > source_network_id: 210 > network_id: NULL > physical_network_id: 202 > is_system: 0 > vpc_id: NULL > dnat_vmip: 10.0.16.2 -- 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-1585) Enact a consistent use of the "Refresh" button
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680213#comment-13680213 ] Animesh Chaturvedi commented on CLOUDSTACK-1585: Brian are you working on this for 4.2? > Enact a consistent use of the "Refresh" button > -- > > Key: CLOUDSTACK-1585 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1585 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Chrome on Mac OS X 10.8.2 >Reporter: Mike Tutkowski >Assignee: Brian Federle >Priority: Minor > Fix For: 4.2.0 > > > From an e-mail exchange (newer of the two messages is on the top): > Brian Federle brian.fede...@citrix.com via incubator.apache.org > 3:41 PM (21 minutes ago) > to Pranav, cloudstack-dev > Yes, please make a feature request for this. Having a table listing refresh > should be fairly easy to implement; it is one of those things I wanted to fix > but keep forgetting to do ;) You can assign to me or Pranav. > -Brian > -Original Message- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Thursday, March 07, 2013 1:37 PM > To: cloudstack-...@incubator.apache.org > Subject: Question about "Refresh" buttons in the GUI > Hi, > I've noticed that some panels have a "Refresh" button and others don't (and > in at least one case, it's actually called "Fetch latest"). I wonder if we > would benefit from making this consistent across the GUI? For example, when > I destroy a VM, I don't actually see it disappear from the table it's in > until I click on another tab and then click back to the Instances tab. > Thoughts on this? Is this "worthy" of a JIRA ticket? > Thanks! -- 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-2761) [VMware] [VPC] Failed to create PF/StaticNAT rules on VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayapal Reddy resolved CLOUDSTACK-2761.
---
Resolution: Fixed
> [VMware] [VPC] Failed to create PF/StaticNAT rules on VPC
> -
>
> Key: CLOUDSTACK-2761
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2761
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 8d1189c2ae87216bc1c4a1443f75e9a8629abdc2
>Reporter: venkata swamybabu budumuru
>Assignee: Jayapal Reddy
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have latest CloudStack build with at least 1 advanced zone
> 2. Have at least 1 VMware cluster with 1 host.
> 3. Create a VPC with at least 1 Tier
> 4. deploy a VM
> 5. apply an ACL to allow all
> 6. acquire at least 1 IP
> 7. create PF/staticNAT on the above created IP to the VM created in step (4)
> Observations:
> (i) It failed to create staticNAT with the following error
> 2013-05-30 08:05:20,203 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-38:null) Seq 1-1416495168: Response Received:
> 2013-05-30 08:05:20,206 DEBUG [agent.transport.Request] (DirectAgent-38:null)
> Seq 1-1416495168: Processing: { Ans: , MgmtId: 7280707764394, via: 1, Ver:
> v1, Flags: 0, [{"routing.IpAssocAnswer":{"results":["10.147.44.63 -
> success"],"result":true,"wait":0}}] }
> 2013-05-30 08:05:20,207 DEBUG [agent.transport.Request]
> (catalina-exec-19:null) Seq 1-1416495168: Received: { Ans: , MgmtId:
> 7280707764394, via: 1, Ver: v1, Flags: 0, { IpAssocAnswer } }
> 2013-05-30 08:05:20,211 INFO [cloud.network.NetworkManagerImpl]
> (catalina-exec-19:null) Let VpcVirtualRouter handle StaticNat in network 204
> 2013-05-30 08:05:20,223 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl] (catalina-exec-19:null)
> Applying static nat rules in network Ntwk[204|Guest|11]
> 2013-05-30 08:05:20,288 DEBUG [agent.transport.Request]
> (catalina-exec-19:null) Seq 1-1416495169: Sending { Cmd , MgmtId:
> 7280707764394, via: 1, Ver: v1, Flags: 11,
> [{"routing.SetStaticNatRulesCommand":{"rules":[{"dstIp":"10.0.1.188","id":0,"srcIp":"10.147.44.63","revoked":false,"alreadyAdded":false,"purpose":"StaticNat","icmpType":0,"icmpCode":0}],"vpcId":1,"accessDetails":{"router.guest.ip":"10.0.1.1","zone.network.type":"Advanced","router.ip":"10.147.40.62","router.name":"r-3-VM"},"wait":0}}]
> }
> 2013-05-30 08:05:20,288 DEBUG [agent.transport.Request]
> (catalina-exec-19:null) Seq 1-1416495169: Executing: { Cmd , MgmtId:
> 7280707764394, via: 1, Ver: v1, Flags: 11,
> [{"routing.SetStaticNatRulesCommand":{"rules":[{"dstIp":"10.0.1.188","id":0,"srcIp":"10.147.44.63","revoked":false,"alreadyAdded":false,"purpose":"StaticNat","icmpType":0,"icmpCode":0}],"vpcId":1,"accessDetails":{"router.guest.ip":"10.0.1.1","zone.network.type":"Advanced","router.ip":"10.147.40.62","router.name":"r-3-VM"},"wait":0}}]
> }
> 2013-05-30 08:05:20,289 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-16:null) Seq 1-1416495169: Executing request
> 2013-05-30 08:05:20,290 INFO [vmware.resource.VmwareResource]
> (DirectAgent-16:10.147.40.12) Executing resource SetFirewallRuleCommand:
> {"rules":[{"dstIp":"10.0.1.188","id":0,"srcIp":"10.147.44.63","revoked":false,"alreadyAdded":false,"purpose":"StaticNat","icmpType":0,"icmpCode":0}],"vpcId":1,"accessDetails":{"router.guest.ip":"10.0.1.1","zone.network.type":"Advanced","router.ip":"10.147.40.62","router.name":"r-3-VM"},"wait":0}
> 2013-05-30 08:05:20,290 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-16:10.147.40.12) Use router's private IP for SSH control. IP :
> 10.147.40.62
> 2013-05-30 08:05:21,746 ERROR [utils.ssh.SshHelper]
> (DirectAgent-16:10.147.40.12) SSH execution of command /root/firewall.sh -A
> -l 10.147.44.63 -r 10.0.1.188 -d 0:0 -G has an error status code in return.
> result output: Bad argument `10.147.44.63'
> Try `iptables -h' or 'iptables --help' for more information.
> Bad argument `10.147.44.63'
> Try `iptables -h' or 'iptables --help' for more information.
> iptables v1.4.14: option "--set-mark" requires an argument
> Try `iptables -h' or 'iptables --help' for more information.
> iptables: No chain/target/match by that name.
> Bad argument `10.147.44.63'
> Try `iptables -h' or 'iptables --help' for more information.
> Bad argument `eth0'
> Try `iptables -h' or 'iptables --help' for more information.
> Bad argument `10.147.44.63'
> Try `iptables -h' or 'iptables --help' for more information.
> iptables: No chain/target/match by that name.
> iptables: No chain/target/match by that
[jira] [Commented] (CLOUDSTACK-2884) Test case "test_service_offerings.py:test_04_change_offering_small" failing automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680207#comment-13680207 ] Prasanna Santhanam commented on CLOUDSTACK-2884: KVM specific failure. Will look into it. Xen and XCP are passing > Test case "test_service_offerings.py:test_04_change_offering_small" failing > automation runs > > > Key: CLOUDSTACK-2884 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2884 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.2.0 > Environment: Master - Automation run >Reporter: Rayees Namathponnan >Assignee: Prasanna Santhanam > Fix For: 4.2.0 > > > Test case "cloudstack/test/integration/smoke/test_service_offerings.py", line > 437, in test_04_change_offering_small" failing with below error > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/Repo_30X/ipcl/cloudstack/test/integration/smoke/test_service_offerings.py", > line 437, in test_04_change_offering_small > "Check Memory(kb) for small offering" > File "/usr/local/lib/python2.7/unittest/case.py", line 535, in > assertAlmostEqual > if round(abs(second-first), places) == 0: > 'str' object cannot be interpreted as an index -- 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-2926) An virtual machine instance cannot be started in a mixed hypervisor environment.
satoru nakaya created CLOUDSTACK-2926: - Summary: An virtual machine instance cannot be started in a mixed hypervisor environment. Key: CLOUDSTACK-2926 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2926 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Environment: XenServer 6.0.2 VMware vSphere 5 update 1 Reporter: satoru nakaya 1.Create XenServer cluster and primary storage. 2.Create VMware cluster and primary storage. 3.Create Instance in VMware cluster. An virtual machine instance cannot be started in VMware cluster. management-server.log: : 2013-06-11 10:57:24,427 WARN [agent.manager.AgentManagerImpl] (Job-Executor-12:job-12) Unsupported Command: Unsupported command issued:com.cloud.agent.api.storage.PrimaryStorageDownloadCommand. Are you sure you got the right type of server? 2013-06-11 10:57:24,427 DEBUG [agent.manager.AgentManagerImpl] (Job-Executor-12:job-12) Details from executing class com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Unsupported command issued:com.cloud.agent.api.storage.PrimaryStorageDownloadCommand. Are you sure you got the right type of server? 2013-06-11 10:57:24,429 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-12:job-12) Failed to start instance VM[DomainRouter|r-4-VM] java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be cast to com.cloud.agent.api.storage.PrimaryStorageDownloadAnswer at com.cloud.template.TemplateManagerImpl.prepareTemplateForCreate(TemplateManagerImpl.java:647) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.StorageManagerImpl.createVolume(StorageManagerImpl.java:3587) at com.cloud.storage.StorageManagerImpl.prepare(StorageManagerImpl.java:3478) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:748) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2615) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1824) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1924) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1902) at com.cloud.network.element.VirtualRouterElement.prepare(VirtualRouterElement.java:208) at com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:1541) at com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:1658) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:1599) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:746) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3865) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) : 2013-06-11 10:57:25,025 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-12:job-12) Unable to contact resource. com.cloud.exception.AgentUnavailableException: Resource [Host:5] is un
[jira] [Commented] (CLOUDSTACK-2879) Try using Nicira NVP plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680113#comment-13680113 ] tuna commented on CLOUDSTACK-2879: -- Hi Seb, I have already seen this guide before raising the comment. You see that I quoted from this. The problem is: - I can't deploy NVP Controller. - I don't know the steps to prepare hypervisor for Nicira NVP integration. No document for them. > Try using Nicira NVP plugin > --- > > Key: CLOUDSTACK-2879 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2879 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > > This process I'm trying to use Nicira NVP plugin. Building, trying and > figuring out what's happen. -- 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-2925) Don't rely on XS to cleanup idle session but proactively close it from console proxy
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680106#comment-13680106 ] Kelven Yang commented on CLOUDSTACK-2925: - Fixed in commit f38c4e9ea684cdec22491858620072f13f4f0155 I linked with a wrong bug number in the commit message. > Don't rely on XS to cleanup idle session but proactively close it from > console proxy > > > Key: CLOUDSTACK-2925 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2925 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Reporter: Kelven Yang >Assignee: Kelven Yang >Priority: Critical > > There is an regression issue after the VNC engine replacement which can cause > idle connection be kept in console proxy and XS host. The accumulated socket > connection can bring down XS host (running out of file handles). -- 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-2925) Don't rely on XS to cleanup idle session but proactively close it from console proxy
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-2925. - Resolution: Fixed > Don't rely on XS to cleanup idle session but proactively close it from > console proxy > > > Key: CLOUDSTACK-2925 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2925 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Reporter: Kelven Yang >Assignee: Kelven Yang >Priority: Critical > > There is an regression issue after the VNC engine replacement which can cause > idle connection be kept in console proxy and XS host. The accumulated socket > connection can bring down XS host (running out of file handles). -- 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-2021) IPV6 - UI - list Network view should include ipv6 cidr information.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680063#comment-13680063 ] ASF subversion and git services commented on CLOUDSTACK-2021: - Commit 4fce6448e65d22587ba72f6bfa493b71ae0e2a08 in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4fce644 ] CLOUDSTACK-2021: UI - Network menu - listView - add IPv6 CIDR field. > IPV6 - UI - list Network view should include ipv6 cidr information. > --- > > Key: CLOUDSTACK-2021 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2021 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 > Environment: Latest build from master >Reporter: Sangeetha Hariharan >Assignee: Jessica Wang > Fix For: 4.2.0 > > Attachments: ListNetwork-view.png > > > IPV6 - UI - list Network view should include ipv6 cidr information. > Steps to reproduce the problem: > Create a IPV6/dual shared network. > List networks by going to to Network tab. > Notice that we display only the ipv4 CIDR for any network. > In case of IPV6 network , I dont see the ipv6 cidr being dispalyed. > In case of a dual network (both ipv4 and ipv6) , I see only ipv4 cidr being > displayed. > Expected Behavior: > Ipv6 Cidr should also be displayed. -- 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-2021) IPV6 - UI - list Network view should include ipv6 cidr information.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-2021. -- Resolution: Fixed > IPV6 - UI - list Network view should include ipv6 cidr information. > --- > > Key: CLOUDSTACK-2021 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2021 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 > Environment: Latest build from master >Reporter: Sangeetha Hariharan >Assignee: Jessica Wang > Fix For: 4.2.0 > > Attachments: ListNetwork-view.png > > > IPV6 - UI - list Network view should include ipv6 cidr information. > Steps to reproduce the problem: > Create a IPV6/dual shared network. > List networks by going to to Network tab. > Notice that we display only the ipv4 CIDR for any network. > In case of IPV6 network , I dont see the ipv6 cidr being dispalyed. > In case of a dual network (both ipv4 and ipv6) , I see only ipv4 cidr being > displayed. > Expected Behavior: > Ipv6 Cidr should also be displayed. -- 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-2925) Don't rely on XS to cleanup idle session but proactively close it from console proxy
Kelven Yang created CLOUDSTACK-2925: --- Summary: Don't rely on XS to cleanup idle session but proactively close it from console proxy Key: CLOUDSTACK-2925 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2925 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: VNC Proxy Reporter: Kelven Yang Assignee: Kelven Yang Priority: Critical There is an regression issue after the VNC engine replacement which can cause idle connection be kept in console proxy and XS host. The accumulated socket connection can bring down XS host (running out of file handles). -- 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-2888) PVLAN - Ubuntu 13.04 vmware - should not allow networks with different primary VLAN with same Secondary VLAN, same primary VLAN with different Secondary VLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680010#comment-13680010 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2888: - Angie, whether or not the svlan and pvlan IDs are configured correctly on the underlying infrastructure is irrelevant to cloudstack. As far as cloudstack is concerned, the pvlan and svlan IDs are acceptable as long as they are valid vlan IDs. Having two secondary VLAN IDs associated with the same promiscuous VLAN ID is valid. Our aim in using PVLAN is basically to seal off VMs belonging to the same isolated VLAN from each other. If they're in different isolated VLANs, they will be able to talk to each other via the router VM, regardless of the promiscuous VLAN they are associated with. > PVLAN - Ubuntu 13.04 vmware - should not allow networks with different > primary VLAN with same Secondary VLAN, same primary VLAN with different > Secondary VLAN > -- > > Key: CLOUDSTACK-2888 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2888 > 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 > vmware ESXi 5.0 hosts > ubuntu 13.04 hosts >Reporter: angeline shen >Assignee: Venkata Siva Vijayendra Bhamidipati > Fix For: 4.2.0 > > Attachments: management-server.log.gz > > > Given: > pvlan1 = 1611svlan1 = 998 > pvlan2 = 1612svlan2 = 997 > nonexistent svlan3 = 999 > Following PVLAN networks SHOULD NOT HAVE BEEN ALLOWED to be created : > pvlan1 , svlan2 > pvlan1 , svlan3 > pvlan2 , svlan1 > pvlan2 , svlan3 > Result: Above PVLAN networks were allowed to be created -- 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-1586) UI:API: Throttling when certain conditions met can lead to too many Error messages.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-1586.
--
Resolution: Won't Fix
have discussed this bug with Parth.
UI pops up a dialog box when an API call returns error. This is the default
behavior.
We can't (and shouldn't) hack it to not pop up a dialog box when another API
call return similar error.
Because every API call is independent.
> UI:API: Throttling when certain conditions met can lead to too many Error
> messages.
>
>
> Key: CLOUDSTACK-1586
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1586
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
> Environment: Build 74.
>Reporter: Parth Jagirdar
>Assignee: Jessica Wang
>
> All,
> This is very annoying. To reproduce this bug; I have already dismissed 300+
> Error Messages.
> I believe we should have a minimum number for throttle. And also find a way
> to overcome 1:1 relation of "API:Error".
> This is similar to CLOUDSTACK-1506. So if these ERRORS are rendered by the
> same widget then please close 1506.
> --
> Set Max API to 15
> Set Time to 25 Seconds.
> Log in as user.
> Click on Network 2 times. (About 8 API calls used)
> Click on any one Network (About 7 used here)
> SO total 15 is reached.
> Now from moment you click on View IP Addresses you will be present with at
> least 1 Error box every 150 ms.
> by average speed on above steps you will be presented with atleast 75 of them.
> Every API, after throttling point, produces 1 error message.
> While in above scenario lisZones kept on getting fired till remaining
> throttle time reached 0 ms.
> This is not only unique scenario. Some single click actions on UI fire
> multiple API's which can potentially result into that many number of error
> boxes for user.
> Say in above scenario we reached the limit before clicking the some network;
> we will be ending up with 7 Error boxes to dismiss.
> --MS LOG BELOW
> 2013-03-07 15:08:59,741 INFO [cloud.api.ApiServer] (catalina-exec-10:null)
> (userId=3 accountId=3 sessionId=AC497FA834D75BAF5DF00CA2F7DA7603)
> 10.217.252.57 -- GET
> command=listNetworks&response=json&sessionkey=VMkdiJrRBW4DmNX%2FERX7IzBqmek%3D&supportedServices=SecurityGroup&listAll=true&details=min&_=1362697744143
> 200 { "listnetworksresponse" : { } }
> 2013-03-07 15:08:59,804 INFO [cloud.api.ApiServer] (catalina-exec-11:null)
> (userId=3 accountId=3 sessionId=AC497FA834D75BAF5DF00CA2F7DA7603)
> 10.217.252.57 -- GET
> command=listZones&response=json&sessionkey=VMkdiJrRBW4DmNX%2FERX7IzBqmek%3D&_=1362697744203
> 200 { "listzonesresponse" : { "count":1 ,"zone" : [
> {"id":"475147bd-968b-461a-9b16-2d97bb2155a6","name":"Test
> Zone","networktype":"Advanced","securitygroupsenabled":false,"allocationstate":"Enabled","zonetoken":"27ffc1ec-ed81-3452-9ea9-b8c767e4b934","dhcpprovider":"VirtualRouter","localstorageenabled":false}
> ] } }
> 2013-03-07 15:08:59,914 INFO [cloud.api.ApiServer] (catalina-exec-16:null)
> (userId=3 accountId=3 sessionId=AC497FA834D75BAF5DF00CA2F7DA7603)
> 10.217.252.57 -- GET
> command=listNetworks&response=json&sessionkey=VMkdiJrRBW4DmNX%2FERX7IzBqmek%3D&listAll=true&page=1&pagesize=20&_=1362697744317
> 200 { "listnetworksresponse" : { "count":1 ,"network" : [
> {"id":"e41b701c-8ef3-4e2a-8f6c-0927a453ea3c","name":"apitest","displaytext":"apitest","broadcastdomaintype":"Vlan","traffictype":"Guest","gateway":"10.1.1.1","netmask":"255.255.255.0","cidr":"10.1.1.0/24","zoneid":"475147bd-968b-461a-9b16-2d97bb2155a6","zonename":"Test
>
> Zone","networkofferingid":"33ddea01-0556-4637-b62a-310c1de2d19c","networkofferingname":"DefaultIsolatedNetworkOfferingWithSourceNatService","networkofferingdisplaytext":"Offering
> for Isolated networks with Source Nat service
> enabled","networkofferingavailability":"Required","issystem":false,"state":"Implemented","related":"e41b701c-8ef3-4e2a-8f6c-0927a453ea3c","dns1":"72.52.126.11","dns2":"72.52.126.12","type":"Isolated","acltype":"Account","account":"test","domainid":"7f88521c-86bf-11e2-b8cf-066a9a000451","domain":"ROOT","service":[{"name":"Dns","capability":[{"name":"AllowDnsSuffixModification","value":"true","canchooseservicecapability":false}]},{"name":"Lb","capability":[{"name":"SupportedStickinessMethods","value":"[{\"methodname\":\"LbCookie\",\"paramlist\":[{\"paramname\":\"cookie-name\",\"required\":false,\"isflag\":false,\"description\":\"
>
> \"},{\"paramname\":\"mode\",\"required\":false,\"isflag\":false,\"description\":\"
[jira] [Commented] (CLOUDSTACK-2886) storage vmotion - vmware dvswitch - migrate VM to another primary storage fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679987#comment-13679987
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2886:
-
Angie, I'm not running into this issue with the latest master. Can you please
check with the latest build and let me know? Thanks!
Regards,
Vijay
> storage vmotion - vmware dvswitch - migrate VM to another primary storage fail
> --
>
> Key: CLOUDSTACK-2886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2886
> 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 2.0 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vcenter ESXi 5.0 hosts
>Reporter: angeline shen
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack -
> Mozilla Firefox-6.png
>
>
> 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. Stop VMs in both PVLANs.
> VM > migrate instance to another primary storage fail:
> 2013-06-06 16:11:53,579 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===START=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&storageid=a8e01df5-f763-3bd9-8f7c-5f40751e8397&virtualmachineid=4eba5aeb-9309-4
> 9a7-be50-e31d8c5a9af7&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370560567954
> 2013-06-06 16:11:53,644 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-18:null) submit async job-36, details: AsyncJobVO {id:36,
> userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
> null, cmd
> : org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","sessionkey":"RV1iRzQ3pg636vVZIwdbrJlAJXU\u003d","virtualmachineid":"4eba5aeb-9309-49a7-be50-e31d8c5a9af7","ctxUs
> erId":"2","storageid":"a8e01df5-f763-3bd9-8f7c-5f40751e8397","httpmethod":"GET","_":"1370560567954","ctxAccountId":"2","ctxStartEventId":"138"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processSta
> tus: 0, resultCode: 0, result: null, initMsid: 206915885077197, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-06 16:11:53,646 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-36
> 2013-06-06 16:11:53,647 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===END=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&storageid=a8e01df5-f763-3bd9-8f7c-5f40751e8397&virtualmachineid=4eba5aeb-9309-49a
> 7-be50-e31d8c5a9af7&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370560567954
> 2013-06-06 16:11:53,662 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3782)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:149)
> 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-06 16:11:53,666 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Complete async job-36, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: null
> 2013-06-06 16:11:56,678 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 10.216.133.70 -- GET
> command=queryAsyncJobResult&jobId=829d4796-a852-4677-a2ca-f42c9ff431e6&response=json&sessionkey=RV1iRzQ3pg636
> vVZIwdbrJlAJXU%3D&_=1370560571051
> 2013-06-06 16:11:56,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-15:null) Async job-36 completed
> 2013-06-06 16:11:56,692 DEBUG
[jira] [Commented] (CLOUDSTACK-2729) [Automation] Libvirt failed find primary storage and VM deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679954#comment-13679954
]
Rayees Namathponnan commented on CLOUDSTACK-2729:
-
Hi Wei / Animesh
Still reproducible even after updating vi /etc/nfsmount.conf (as per wei
suggestion in http://support.citrix.com/article/CTX135927)
# Protocol Version [2,3,4]
# This defines the default protocol version which will
# be used to start the negotiation with the server.
Defaultvers=3
> [Automation] Libvirt failed find primary storage and VM deployment failed
>
>
> Key: CLOUDSTACK-2729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2729
> 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
> Environment: Master branch build
> Automation environment - KVM
>Reporter: Rayees Namathponnan
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2729.rar
>
>
> Failed to deploy VM in automation, environment created with , 2 hosts and 2
> primary storages in a cluster
> 1) /export/home/rayees/SC_QA_AUTO4/primary2
> 2) /export/home/rayees/SC_QA_AUTO4/primary
> Libvirt failed to find the primary storage
> /export/home/rayees/SC_QA_AUTO4/primary and VM deployment failed
> MS log
> 2013-05-28 21:11:44,540 DEBUG [agent.transport.Request] (consoleproxy-1:null)
> Seq 4-936706756: Sending { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1,
> Flags: 100111,
> [{"StartCommand":{"vm":{"id":29,"name":"v-29-QA","type":"ConsoleProxy","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP type=consoleproxy
> host=10.223.49.195 port=8250 name=v-29-QA premium=true zone=1 pod=1
> guid=Proxy.29 proxy_vm=29 disable_rp_filter=true eth2ip=10.223.122.73
> eth2mask=255.255.255.192 gateway=10.223.122.65 eth0ip=169.254.0.154
> eth0mask=255.255.0.0 eth1ip=10.223.50.96 eth1mask=255.255.255.192
> mgmtcidr=10.223.49.192/26 localgw=10.223.50.65 internaldns1=10.223.110.254
> dns1=72.52.126.11","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"d099568827911cef","params":{},"uuid":"5a146833-6a8c-44e5-83c0-50f34accf513","disks":[{"id":32,"name":"ROOT-29","mountPoint":"/export/home/rayees/SC_QA_AUTO4/primary","path":"f6f8d865-e9c0-4188-8a33-6c6383ca5075","size":276406784,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","deviceId":0}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"uuid":"21175978-96bd-4160-8228-8ad15aa40c66","ip":"10.223.122.73","netmask":"255.255.255.192","gateway":"10.223.122.65","mac":"06:2e:5a:00:00:42","dns1":"72.52.126.11","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://1221","isolationUri":"vlan://1221","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"e0651452-a76e-4564-96b2-3d5d51e9bcd6","ip":"169.254.0.154","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:00:9a","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"0765c229-468e-4dfd-8382-24ac49791a8d","ip":"10.223.50.96","netmask":"255.255.255.192","gateway":"10.223.50.65","mac":"06:a8:e8:00:00:1d","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false}]},"hostIp":"10.223.50.66","wait":0}},{"check.CheckSshCommand":{"ip":"169.254.0.154","port":3922,"interval":6,"retries":100,"name":"v-29-QA","wait":0}}]
> }
> 2013-05-28 21:11:44,552 DEBUG [agent.transport.Request]
> (AgentManager-Handler-1:null) Seq 4-936706756: Processing: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 110,
> [{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:380)\n\tat
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:72)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3399)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3293)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1187)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\
[jira] [Resolved] (CLOUDSTACK-2506) create network dialog is not displaying network offerings with specifyvlan=true to admin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-2506. -- Resolution: Invalid shweta, Create Network dialog in Networks menu is only for creating Isolated network with SourceNAT. The reason that the network offering you created didn't show up in network offering dropdown in Create Network dialog in Networks menu is because it didn't include SourceNAT service. Jessica > create network dialog is not displaying network offerings with > specifyvlan=true to admin > > > Key: CLOUDSTACK-2506 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2506 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: build: > CloudStack-non-OSS-MASTER-329-rhel6.3 >Reporter: shweta agarwal >Priority: Blocker > Fix For: 4.2.0 > > > Repro steps: > 1. Create a network offerings with specify vlan=true > 2. As a root admin Goto network tab and open create network dialog > Bug: > Notice its not showing network offerings created in step 1 > Expected result: > It should show the network offerings created in step1 > Actually When we open create network dialog presently its only firing > following api > http://10.147.59.212:8080/client/api?command=listNetworkOfferings&zoneid=dd1f4b0f-bc77-4b3b-8f47-45130d4b816a&forVpc=false&response=json&sessionkey=dNddt90WhymsHK2%2FNj9eD5fZbWk%3D&guestiptype=Isolated&supportedServices=SourceNat&specifyvlan=false&state=Enabled&_=1368600062363 > it need to fire one more api with specifyvlan=true param value for isolated > network -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-255) Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd
[ https://issues.apache.org/jira/browse/CLOUDSTACK-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679833#comment-13679833 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-255: Sailaja, I don't see an option in 4.2 to change the network offering of a guest network anymore - can you please check the steps and re-evaluate this bug and let me know? Thanks! > Null pointer exception while creating portforwarding rule after performing > UpdateNetworkCmd > > > Key: CLOUDSTACK-255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: pre-4.0.0 >Reporter: Sailaja Mada >Assignee: Venkata Siva Vijayendra Bhamidipati > Fix For: 4.2.0 > > Attachments: api-server.log, management-server-pf.log > > > Steps : > 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server. > 2. Create new account > 3. Create Network offering1 with Redundant Router enabled , > Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, > Lb, Dhcp, StaticNat > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false > 4. Create Network with the above offering. > 5. Deploy instance with this network > 6. Both Routers and instance got deployed. > 7. Configure LB rule with 22 port , Enable VPN , Once the key is generated > , disable VPN > 8. Create Network offering 2 with Single Router and > Supported ServicesPortForwarding, SourceNat, Firewall, Dns, Dhcp > Service Capabilities SupportedSourceNatTypes: peraccount, RedundantRouter: > false > 9. Edit Network details and update the Network offering 1 to Network offering > 2. > 10.It created new Router and deleted Redundant Routers. LB Rules are not > deleted. > 11. Now tried to create Port forwarding Rule with 22 . > Observation: > It failed with Null Pointer exception : > 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] > (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd: > java.lang.NullPointerException > at > com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863) > at > com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895) > at > com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205) > at > com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231) > at > com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299) > at > com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
[jira] [Commented] (CLOUDSTACK-2879) Try using Nicira NVP plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679741#comment-13679741 ] sebastien goasguen commented on CLOUDSTACK-2879: Check http://cloudstack.apache.org/docs/en-US/index.html left gutter, click on 4.1, you should see it > Try using Nicira NVP plugin > --- > > Key: CLOUDSTACK-2879 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2879 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > > This process I'm trying to use Nicira NVP plugin. Building, trying and > figuring out what's happen. -- 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-2729) [Automation] Libvirt failed find primary storage and VM deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-2729:
Priority: Major (was: Blocker)
> [Automation] Libvirt failed find primary storage and VM deployment failed
>
>
> Key: CLOUDSTACK-2729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2729
> 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
> Environment: Master branch build
> Automation environment - KVM
>Reporter: Rayees Namathponnan
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2729.rar
>
>
> Failed to deploy VM in automation, environment created with , 2 hosts and 2
> primary storages in a cluster
> 1) /export/home/rayees/SC_QA_AUTO4/primary2
> 2) /export/home/rayees/SC_QA_AUTO4/primary
> Libvirt failed to find the primary storage
> /export/home/rayees/SC_QA_AUTO4/primary and VM deployment failed
> MS log
> 2013-05-28 21:11:44,540 DEBUG [agent.transport.Request] (consoleproxy-1:null)
> Seq 4-936706756: Sending { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1,
> Flags: 100111,
> [{"StartCommand":{"vm":{"id":29,"name":"v-29-QA","type":"ConsoleProxy","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP type=consoleproxy
> host=10.223.49.195 port=8250 name=v-29-QA premium=true zone=1 pod=1
> guid=Proxy.29 proxy_vm=29 disable_rp_filter=true eth2ip=10.223.122.73
> eth2mask=255.255.255.192 gateway=10.223.122.65 eth0ip=169.254.0.154
> eth0mask=255.255.0.0 eth1ip=10.223.50.96 eth1mask=255.255.255.192
> mgmtcidr=10.223.49.192/26 localgw=10.223.50.65 internaldns1=10.223.110.254
> dns1=72.52.126.11","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"d099568827911cef","params":{},"uuid":"5a146833-6a8c-44e5-83c0-50f34accf513","disks":[{"id":32,"name":"ROOT-29","mountPoint":"/export/home/rayees/SC_QA_AUTO4/primary","path":"f6f8d865-e9c0-4188-8a33-6c6383ca5075","size":276406784,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","deviceId":0}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"uuid":"21175978-96bd-4160-8228-8ad15aa40c66","ip":"10.223.122.73","netmask":"255.255.255.192","gateway":"10.223.122.65","mac":"06:2e:5a:00:00:42","dns1":"72.52.126.11","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://1221","isolationUri":"vlan://1221","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"e0651452-a76e-4564-96b2-3d5d51e9bcd6","ip":"169.254.0.154","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:00:9a","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"0765c229-468e-4dfd-8382-24ac49791a8d","ip":"10.223.50.96","netmask":"255.255.255.192","gateway":"10.223.50.65","mac":"06:a8:e8:00:00:1d","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false}]},"hostIp":"10.223.50.66","wait":0}},{"check.CheckSshCommand":{"ip":"169.254.0.154","port":3922,"interval":6,"retries":100,"name":"v-29-QA","wait":0}}]
> }
> 2013-05-28 21:11:44,552 DEBUG [agent.transport.Request]
> (AgentManager-Handler-1:null) Seq 4-936706756: Processing: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 110,
> [{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Storage pool not found: no pool with matching
> uuid\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:380)\n\tat
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:72)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3399)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3293)\n\tat
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1187)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
>
> java.lang.Thread.run(Thread.java:679)\n","wait":0}},{"Answer":{"result":false,"details":"St
[jira] [Commented] (CLOUDSTACK-2886) PVLAN - vmware dvswitch - migrate VM to another primary storage fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679727#comment-13679727
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2886:
-
Not pvlan related :
at
com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3782)
This is the storage vmotion code path.
Will change the heading to reflect the same.
> PVLAN - vmware dvswitch - migrate VM to another primary storage fail
>
>
> Key: CLOUDSTACK-2886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2886
> 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 2.0 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vcenter ESXi 5.0 hosts
>Reporter: angeline shen
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack -
> Mozilla Firefox-6.png
>
>
> 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. Stop VMs in both PVLANs.
> VM > migrate instance to another primary storage fail:
> 2013-06-06 16:11:53,579 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===START=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&storageid=a8e01df5-f763-3bd9-8f7c-5f40751e8397&virtualmachineid=4eba5aeb-9309-4
> 9a7-be50-e31d8c5a9af7&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370560567954
> 2013-06-06 16:11:53,644 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-18:null) submit async job-36, details: AsyncJobVO {id:36,
> userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
> null, cmd
> : org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","sessionkey":"RV1iRzQ3pg636vVZIwdbrJlAJXU\u003d","virtualmachineid":"4eba5aeb-9309-49a7-be50-e31d8c5a9af7","ctxUs
> erId":"2","storageid":"a8e01df5-f763-3bd9-8f7c-5f40751e8397","httpmethod":"GET","_":"1370560567954","ctxAccountId":"2","ctxStartEventId":"138"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processSta
> tus: 0, resultCode: 0, result: null, initMsid: 206915885077197, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-06 16:11:53,646 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-36
> 2013-06-06 16:11:53,647 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===END=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&storageid=a8e01df5-f763-3bd9-8f7c-5f40751e8397&virtualmachineid=4eba5aeb-9309-49a
> 7-be50-e31d8c5a9af7&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370560567954
> 2013-06-06 16:11:53,662 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3782)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:149)
> 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-06 16:11:53,666 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Complete async job-36, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: null
> 2013-06-06 16:11:56,678 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 10.216.133.70 -- GET
> command=queryAsyncJobResult&jobId=829d4796-a852-4677-a2ca-f42c9ff431e6&response=json&sessionkey=RV1iRzQ3pg636
> vVZIwdbrJlAJXU%3D&_=1370560571051
> 2013-06-06 16:11:56,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-15:null) Async job-36 completed
> 2013-0
[jira] [Updated] (CLOUDSTACK-2886) storage vmotion - vmware dvswitch - migrate VM to another primary storage fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-2886:
Summary: storage vmotion - vmware dvswitch - migrate VM to another primary
storage fail (was: PVLAN - vmware dvswitch - migrate VM to another primary
storage fail)
> storage vmotion - vmware dvswitch - migrate VM to another primary storage fail
> --
>
> Key: CLOUDSTACK-2886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2886
> 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 2.0 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vcenter ESXi 5.0 hosts
>Reporter: angeline shen
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack -
> Mozilla Firefox-6.png
>
>
> 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. Stop VMs in both PVLANs.
> VM > migrate instance to another primary storage fail:
> 2013-06-06 16:11:53,579 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===START=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&storageid=a8e01df5-f763-3bd9-8f7c-5f40751e8397&virtualmachineid=4eba5aeb-9309-4
> 9a7-be50-e31d8c5a9af7&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370560567954
> 2013-06-06 16:11:53,644 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-18:null) submit async job-36, details: AsyncJobVO {id:36,
> userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
> null, cmd
> : org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","sessionkey":"RV1iRzQ3pg636vVZIwdbrJlAJXU\u003d","virtualmachineid":"4eba5aeb-9309-49a7-be50-e31d8c5a9af7","ctxUs
> erId":"2","storageid":"a8e01df5-f763-3bd9-8f7c-5f40751e8397","httpmethod":"GET","_":"1370560567954","ctxAccountId":"2","ctxStartEventId":"138"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processSta
> tus: 0, resultCode: 0, result: null, initMsid: 206915885077197, completeMsid:
> null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-06 16:11:53,646 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-36
> 2013-06-06 16:11:53,647 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===END=== 10.216.133.70 -- GET
> command=migrateVirtualMachine&storageid=a8e01df5-f763-3bd9-8f7c-5f40751e8397&virtualmachineid=4eba5aeb-9309-49a
> 7-be50-e31d8c5a9af7&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370560567954
> 2013-06-06 16:11:53,662 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.UserVmManagerImpl.vmStorageMigration(UserVmManagerImpl.java:3782)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:149)
> 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-06 16:11:53,666 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-36) Complete async job-36, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: null
> 2013-06-06 16:11:56,678 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 10.216.133.70 -- GET
> command=queryAsyncJobResult&jobId=829d4796-a852-4677-a2ca-f42c9ff431e6&response=json&sessionkey=RV1iRzQ3pg636
> vVZIwdbrJlAJXU%3D&_=1370560571051
> 2013-06-06 16:11:56,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-15:null) Async job-36 completed
> 2013-06-06 16:11:56,692 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
[jira] [Commented] (CLOUDSTACK-2827) Windows 8 (64 bit) guest OS enablement on KVM in cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679722#comment-13679722 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2827: - Marked as in review, patch posted on https://reviews.apache.org/r/11611/ > Windows 8 (64 bit) guest OS enablement on KVM in cloudstack > --- > > Key: CLOUDSTACK-2827 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2827 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0, 4.2.0 > Environment: KVM deployments in cloudstack. >Reporter: Venkata Siva Vijayendra Bhamidipati >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Minor > Fix For: 4.2.0 > > > We need to provide the option for users to create a Windows 8 (64 bit) guest > VM on KVM server deployments in cloudstack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2826) Windows 8 64 bit guest OS support for KVM in cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati closed CLOUDSTACK-2826. --- Duplicated by 2827. > Windows 8 64 bit guest OS support for KVM in cloudstack > --- > > Key: CLOUDSTACK-2826 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2826 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0, 4.2.0 > Environment: KVM deployments on cloudstack >Reporter: Venkata Siva Vijayendra Bhamidipati >Priority: Minor > Fix For: 4.2.0 > > > We need to enable the option of creating a Windows 8 (64 bit) guest VM on a > KVM server using cloudstack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-778) user provided hostname to be specified in vCenter instead of CloudStack generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-778. Resolution: Fixed > user provided hostname to be specified in vCenter instead of CloudStack > generated name > -- > > Key: CLOUDSTACK-778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-778 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: haroon abdelrahman >Assignee: Venkata Siva Vijayendra Bhamidipati > Fix For: 4.2.0 > > > Release Planning: > Dev List discussion: unknown > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+provided+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs > Feature Branch: unknown -- 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-778) user provided hostname to be specified in vCenter instead of CloudStack generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679719#comment-13679719 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-778: Marking as resolved. > user provided hostname to be specified in vCenter instead of CloudStack > generated name > -- > > Key: CLOUDSTACK-778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-778 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: haroon abdelrahman >Assignee: Venkata Siva Vijayendra Bhamidipati > Fix For: 4.2.0 > > > Release Planning: > Dev List discussion: unknown > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+provided+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs > Feature Branch: unknown -- 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-2887) PVLAN - vmware dvswitch - destroy VM fail with VM stuck in 'Stopping' state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati closed CLOUDSTACK-2887.
---
Resolution: Duplicate
Closing as dup of CLOUDSTACK-2881.
> PVLAN - vmware dvswitch - destroy VM fail with VM stuck in 'Stopping' state
>
>
> Key: CLOUDSTACK-2887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2887
> 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 2.0 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vcenter ESXi 5.0 hosts
>Reporter: angeline shen
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, management-server.log.gz,
> Screenshot-CloudStack - Mozilla Firefox-7.png
>
>
> 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. Destroy VMs in both PVLANs.
> Result:VMS remain in Stopping state.
> 2013-06-06 15:46:57,467 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
> ===START=== 10.216.133.70 -- GET
> command=destroyVirtualMachine&id=c27541d9-f4d2-40fc-8fab-3edfadc4067e&response=json&sessionkey=RV1iRzQ3pg636vVZIwdb
> rJlAJXU%3D&_=1370559071830
> 2013-06-06 15:46:57,575 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-10:null) submit async job-34, details: AsyncJobVO {id:34,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 12, c
> md: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","id":"c27541d9-f4d2-40fc-8fab-3edfadc4067e","sessionkey":"RV1iRzQ3pg636vVZIwdbrJlAJXU\u003d","ctxUserId":"2","httpmeth
> od":"GET","_":"1370559071830","ctxAccountId":"2","ctxStartEventId":"132"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 206915885077197,
> completeMsid
> : null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-06 15:46:57,577 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-34:job-34) Executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-34
> 2013-06-06 15:46:57,578 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
> ===END=== 10.216.133.70 -- GET
> command=destroyVirtualMachine&id=c27541d9-f4d2-40fc-8fab-3edfadc4067e&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370559071830
> 2013-06-06 15:46:57,630 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-34:job-34) Destroying vm VM[User|vm1612V61]
> 2013-06-06 15:46:57,667 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-34:job-34) VM state transitted from :Running to Stopping with
> event: StopRequestedvm's original host id: 1 new host id: 2 host id before
> state transition: 2
> 2013-06-06 15:46:57,702 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-34:job-34) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
> java.lang.ClassCastException:
> com.cloud.vm.VMInstanceVO$$EnhancerByCGLIB$$a77eface cannot be cast to
> com.cloud.vm.UserVmVO
> at
> com.cloud.vm.UserVmManagerImpl.prepareStop(UserVmManagerImpl.java:4712)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1168)
> at
> com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1285)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:265)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:225)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3385)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:1898)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:100)
> 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.
[jira] [Commented] (CLOUDSTACK-2887) PVLAN - vmware dvswitch - destroy VM fail with VM stuck in 'Stopping' state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679707#comment-13679707
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2887:
-
The exception signature is identical to the one seen in CLOUDSTACK-2865 and
CLOUDSTACK-2881. Will close this as a dup of 2881. 2881 needs to be closed as a
dup of 2865 in case the fix for 2865 fixes the former.
> PVLAN - vmware dvswitch - destroy VM fail with VM stuck in 'Stopping' state
>
>
> Key: CLOUDSTACK-2887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2887
> 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 2.0 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vcenter ESXi 5.0 hosts
>Reporter: angeline shen
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, management-server.log.gz,
> Screenshot-CloudStack - Mozilla Firefox-7.png
>
>
> 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. Destroy VMs in both PVLANs.
> Result:VMS remain in Stopping state.
> 2013-06-06 15:46:57,467 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
> ===START=== 10.216.133.70 -- GET
> command=destroyVirtualMachine&id=c27541d9-f4d2-40fc-8fab-3edfadc4067e&response=json&sessionkey=RV1iRzQ3pg636vVZIwdb
> rJlAJXU%3D&_=1370559071830
> 2013-06-06 15:46:57,575 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-10:null) submit async job-34, details: AsyncJobVO {id:34,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 12, c
> md: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","id":"c27541d9-f4d2-40fc-8fab-3edfadc4067e","sessionkey":"RV1iRzQ3pg636vVZIwdbrJlAJXU\u003d","ctxUserId":"2","httpmeth
> od":"GET","_":"1370559071830","ctxAccountId":"2","ctxStartEventId":"132"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 206915885077197,
> completeMsid
> : null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-06 15:46:57,577 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-34:job-34) Executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-34
> 2013-06-06 15:46:57,578 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
> ===END=== 10.216.133.70 -- GET
> command=destroyVirtualMachine&id=c27541d9-f4d2-40fc-8fab-3edfadc4067e&response=json&sessionkey=RV1iRzQ3pg636vVZIwdbrJlAJXU%3D&_=1370559071830
> 2013-06-06 15:46:57,630 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-34:job-34) Destroying vm VM[User|vm1612V61]
> 2013-06-06 15:46:57,667 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-34:job-34) VM state transitted from :Running to Stopping with
> event: StopRequestedvm's original host id: 1 new host id: 2 host id before
> state transition: 2
> 2013-06-06 15:46:57,702 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-34:job-34) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
> java.lang.ClassCastException:
> com.cloud.vm.VMInstanceVO$$EnhancerByCGLIB$$a77eface cannot be cast to
> com.cloud.vm.UserVmVO
> at
> com.cloud.vm.UserVmManagerImpl.prepareStop(UserVmManagerImpl.java:4712)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1168)
> at
> com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1285)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:265)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:225)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3385)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:1898)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:100)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.Asyn
[jira] [Commented] (CLOUDSTACK-2881) PVLAN - vmware dvswitch - VM stop result in VM remains in Stopping state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679701#comment-13679701 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2881: - The exception seen is unrelated to the pvlan code path. Angie, could you please corroborate Wei's comment by testing out with the latest build that fixes CLOUDSTACK-2865? > PVLAN - vmware dvswitch - VM stop result in VM remains in Stopping state > > > Key: CLOUDSTACK-2881 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2881 > 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 2.0 build > CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz > vcenter ESXi 5.0 hosts >Reporter: angeline shen >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log.gz, Screenshot-CloudStack - > Mozilla Firefox-1.png, Screenshot-CloudStack - Mozilla Firefox-2.png, > Screenshot-CloudStack - Mozilla Firefox.png > > > 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. Stop VMs in both PVLANs. > Result:VMS remain in Stopping state. > 2013-06-06 12:45:05,238 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-23:job-23) Executing > org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-23 > 2013-06-06 12:45:05,239 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null) > ===END=== 10.216.133.70 -- GET > command=stopVirtualMachine&id=89b5f080-29ee-40b2-9fa4-e844afd2fe81&forced=false&response=json&sessionkey=KdfMcbJgtOTr1WGs4CGQD4ckw2c%3D&_=1370548159473 > 2013-06-06 12:45:05,244 DEBUG [cloud.api.ApiDispatcher] > (Job-Executor-23:job-23) ControlledEntity name is:com.cloud.vm.VirtualMachine > 2013-06-06 12:45:05,247 DEBUG [cloud.api.ApiDispatcher] > (Job-Executor-23:job-23) ControlledEntity name is:com.cloud.uservm.UserVm > 2013-06-06 12:45:05,248 DEBUG [cloud.api.ApiDispatcher] > (Job-Executor-23:job-23) ControlledEntity name > is:com.cloud.network.router.VirtualRouter > 2013-06-06 12:45:05,328 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-23:job-23) VM state transitted from :Running to Stopping with > event: StopRequestedvm's original host id: 2 new host id: 2 host id before > state transition: 2 > 2013-06-06 12:45:05,362 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-23:job-23) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.StopVMCmd > java.lang.ClassCastException: > com.cloud.vm.VMInstanceVO$$EnhancerByCGLIB$$a77eface cannot be cast to > com.cloud.vm.UserVmVO > at > com.cloud.vm.UserVmManagerImpl.prepareStop(UserVmManagerImpl.java:4712) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1168) > at > com.cloud.vm.VirtualMachineManagerImpl.stop(VirtualMachineManagerImpl.java:974) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.stopvirtualmachine(VMEntityManagerImpl.java:257) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.stop(VirtualMachineEntityImpl.java:214) > at > com.cloud.vm.UserVmManagerImpl.stopVirtualMachine(UserVmManagerImpl.java:3152) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.StopVMCmd.execute(StopVMCmd.java:117) > 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-06 12:45:05,363 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-23:job-23) Complete async job-23, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: > com.cloud.vm.VMInstanceVO$$EnhancerByCGLIB$$a77eface cannot be cast to > co
[jira] [Reopened] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan reopened CLOUDSTACK-2882:
-
Still fails with error
paramiko.transport: DEBUG: [chan 3] EOF received (3)
sshClient: DEBUG: {Cmd: mount -rt iso9660 /dev/vda /mnt/tmp via Host:
10.208.10.20} {returns: ['mount: /dev/vda already mounted or /mnt/tmp busy']}
http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-smoke-matrix/418/suite=test_vm_life_cycle/testReport/junit/integration.smoke.test_vm_life_cycle/TestVMLifeCycle/test_10_attachAndDetach_iso/
> Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso"
> failing due to wrong mount point in KVM
> --
>
> Key: CLOUDSTACK-2882
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2882
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.2.0
> Environment: Automation - BVT
>Reporter: Rayees Namathponnan
>Assignee: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso"
> failing due to wrong mount point in KVM
> Test case failing with below error
> paramiko.transport: INFO: Secsh channel 3 opened.
> paramiko.transport: DEBUG: [chan 3] Sesch channel 3 request ok
> sshClient: DEBUG: {Cmd: mount -rt iso9660 /dev/xvdd /mnt/tmp via Host:
> 10.208.10.22} {returns: ['mount: special device /dev/xvdd does not exist']}
> http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-smoke-matrix/389/suite=test_vm_life_cycle/testReport/integration.smoke.test_vm_life_cycle/TestVMLifeCycle/test_10_attachAndDetach_iso/
--
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-2924) Recurring snapshot schedule not showing up in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679656#comment-13679656
]
ASF subversion and git services commented on CLOUDSTACK-2924:
-
Commit 5b48ec24d8d0dd5919d80d396d6f1825dfe5373f in branch
refs/heads/disk_io_throttling from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5b48ec2 ]
CLOUDSTACK-2924
Recurring snapshot schedule not showing up in UI
For some of the volumes Recurring snapshot schedule was not showing up in UI
because the active column was set to false. Since we dont use this column
anymore I am removing the active=true check in the listSnapshotPolicies call.
> Recurring snapshot schedule not showing up in UI
>
>
> Key: CLOUDSTACK-2924
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2924
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Nitin Mehta
>
> Issue is now exhibiting itself again:
> Volume id 502 has 4 snapshots, two DAILY, 1 WEEKLY, and 1 MONTHLY. Most
> recent snapshot is today.
> request:
> http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshots&listAll=true&page=1&pagesize=20&volumeid=502&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&_=1354580214377
> response:
> { "listsnapshotsresponse" : { "count":4 ,"snapshot" : [
> {"id":"0c2d17c1-a537-4d19-b83f-c13539d656a5","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"DAILY","state":"BackedUp","tags":[]},
>
> {"id":"d2438a81-6874-4e9b-8335-42c7f1d09691","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"WEEKLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"WEEKLY","state":"BackedUp","tags":[]},
>
> {"id":"03ceeafc-83ac-40fa-85b1-a18464429206","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"MONTHLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:36-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100336","intervaltype":"MONTHLY","state":"BackedUp","tags":[]},
>
> {"id":"29524d7e-e420-4193-9169-0d3cc4b1c810","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:35-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100335","intervaltype":"DAILY","state":"BackedUp","tags":[]}
> ] } }
> However, listing the recurring schedule shows nothing:
> request:
> http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshotPolicies&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&volumeid=502&_=1354580037175
> response:
> { "listsnapshotpoliciesresponse" : { } }
--
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-1301) VM Disk I/O Throttling
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679655#comment-13679655 ] ASF subversion and git services commented on CLOUDSTACK-1301: - Commit 869a6b0ce305b70c4be72bd5d03866310c4313cc in branch refs/heads/disk_io_throttling from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=869a6b0 ] CLOUDSTACK-1301: VM Disk I/O Throttling on Bps/IOps > VM Disk I/O Throttling > -- > > Key: CLOUDSTACK-1301 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1301 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.1.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.2.0 > > > VM Disk I/O Throttling, to set the maximum disk I/O rate of VMs. > Virtual machines are running on the same storage device (local storage or > share strage). Because of the rate limitation of device (such as iops), if > one VM has large disk operation, it may affect the disk performance of other > VMs running on the same storage device. > It is neccesary to set the maximum rate and limit the disk I/O of VMs. > More details: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+IO+Throttling -- 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-2879) Try using Nicira NVP plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679640#comment-13679640 ] tuna commented on CLOUDSTACK-2879: -- "Before enabling the Nicira NVP plugin the NVP Controller needs to be configured. Please review the NVP User Guide on how to do that." -> How can I find the NVP User Guide? "Please refer to the Nicira NVP configuration guide on how to prepare the hypervisors for Nicira NVP integration." -> How can I find the NVP configuration guide? > Try using Nicira NVP plugin > --- > > Key: CLOUDSTACK-2879 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2879 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > > This process I'm trying to use Nicira NVP plugin. Building, trying and > figuring out what's happen. -- 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-2796) [Automation] Failed to add primary storage with error "Missing parameter hypervisor."
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan closed CLOUDSTACK-2796. --- Verified > [Automation] Failed to add primary storage with error "Missing parameter > hypervisor." > - > > Key: CLOUDSTACK-2796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2796 > 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 > Environment: Master branch, commit : > 6dad8adf8fc22417f0242126b8f52ee081f74f49 >Reporter: Rayees Namathponnan >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Create new build from master branch commit > 6dad8adf8fc22417f0242126b8f52ee081f74f49 > Create advanced zone, with primary strorage scope = "cluster" > Result : > Failed to primary storage with below error > "Missing parameter hypervisor. Hypervisor type is required to create zone > wide primary storage." -- 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-2879) Try using Nicira NVP plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna updated CLOUDSTACK-2879: - Description: This process I'm trying to use Nicira NVP plugin. Building, trying and figuring out what's happen. > Try using Nicira NVP plugin > --- > > Key: CLOUDSTACK-2879 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2879 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > > This process I'm trying to use Nicira NVP plugin. Building, trying and > figuring out what's happen. -- 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-2878) Try using native SDN controller with XCP 1.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna updated CLOUDSTACK-2878: - Description: I'm trying to use native SDN controller with GRE isolation method. It's tested with XCP 1.6. The purpose is controlling what's happen. > Try using native SDN controller with XCP 1.6 > > > Key: CLOUDSTACK-2878 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2878 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > > I'm trying to use native SDN controller with GRE isolation method. It's > tested with XCP 1.6. The purpose is controlling what's happen. -- 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-2878) Try using native SDN controller with XCP 1.6
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679634#comment-13679634
]
tuna commented on CLOUDSTACK-2878:
--
I found this error starting from the below code.
NetworkManagerImpl.java
NicProfile profile = guru.allocate(network, requested, vm); (1)
if (isDefaultNic != null) {
profile.setDefaultNic(
isDefaultNic);
}
ExtenalGuestNetworkGuru.java
@Override
public NicProfile allocate(Network config, NicProfile nic,
VirtualMachineProfile vm) throws
InsufficientVirtualNetworkCapcityException,
InsufficientAddressCapacityException {
if
(_networkModel.networkIsConfiguredForExternalNetworking(config.getDataCenterId(),
config.getId()) && nic != null && nic.getRequestedIpv4() != null) {
throw new CloudRuntimeException("Does not support custom ip
allocation at this time: " + nic);
}
NicProfile profile = super.allocate(config, nic, vm);
boolean _isEnabled =
Boolean.parseBoolean(_configDao.getValue(Config.OvsTunnelNetwork.key()));
(2)
if (_isEnabled) {
return null;
}
if
(_networkModel.networkIsConfiguredForExternalNetworking(config.getDataCenterId(),
config.getId())) {
profile.setStrategy(ReservationStrategy.Start);
/* We won't clear IP address, because router may set gateway as it
IP, and it would be updated properly later */
//profile.setIp4Address(null);
profile.setGateway(null);
profile.setNetmask(null);
}
return profile;
}
The return from (1) is NULL, because at (2) sdn.ovs.controller set to true. So
profile = NULL and then we get NullPointerException error in the next step.
This error prevents me to deployVM using GRE isolation method. If I set
sdn.ovs.controller = false, no error anymore but can't using GRE.
> Try using native SDN controller with XCP 1.6
>
>
> Key: CLOUDSTACK-2878
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2878
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: tuna
>Assignee: tuna
> Fix For: 4.2.0
>
>
> I'm trying to use native SDN controller with GRE isolation method. It's
> tested with XCP 1.6. The purpose is controlling what's happen.
--
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-2884) Test case "test_service_offerings.py:test_04_change_offering_small" failing automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679628#comment-13679628 ] Rayees Namathponnan commented on CLOUDSTACK-2884: - Failed to last run also in jenkins.cloudstack.org http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-smoke-matrix/420/suite=test_service_offerings/testReport/junit/integration.smoke.test_service_offerings/TestServiceOfferings/test_04_change_offering_small/ > Test case "test_service_offerings.py:test_04_change_offering_small" failing > automation runs > > > Key: CLOUDSTACK-2884 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2884 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.2.0 > Environment: Master - Automation run >Reporter: Rayees Namathponnan >Assignee: Prasanna Santhanam > Fix For: 4.2.0 > > > Test case "cloudstack/test/integration/smoke/test_service_offerings.py", line > 437, in test_04_change_offering_small" failing with below error > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/Repo_30X/ipcl/cloudstack/test/integration/smoke/test_service_offerings.py", > line 437, in test_04_change_offering_small > "Check Memory(kb) for small offering" > File "/usr/local/lib/python2.7/unittest/case.py", line 535, in > assertAlmostEqual > if round(abs(second-first), places) == 0: > 'str' object cannot be interpreted as an index -- 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-2924) Recurring snapshot schedule not showing up in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679535#comment-13679535
]
ASF subversion and git services commented on CLOUDSTACK-2924:
-
Commit 5b48ec24d8d0dd5919d80d396d6f1825dfe5373f in branch refs/heads/master
from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5b48ec2 ]
CLOUDSTACK-2924
Recurring snapshot schedule not showing up in UI
For some of the volumes Recurring snapshot schedule was not showing up in UI
because the active column was set to false. Since we dont use this column
anymore I am removing the active=true check in the listSnapshotPolicies call.
> Recurring snapshot schedule not showing up in UI
>
>
> Key: CLOUDSTACK-2924
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2924
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Nitin Mehta
>
> Issue is now exhibiting itself again:
> Volume id 502 has 4 snapshots, two DAILY, 1 WEEKLY, and 1 MONTHLY. Most
> recent snapshot is today.
> request:
> http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshots&listAll=true&page=1&pagesize=20&volumeid=502&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&_=1354580214377
> response:
> { "listsnapshotsresponse" : { "count":4 ,"snapshot" : [
> {"id":"0c2d17c1-a537-4d19-b83f-c13539d656a5","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"DAILY","state":"BackedUp","tags":[]},
>
> {"id":"d2438a81-6874-4e9b-8335-42c7f1d09691","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"WEEKLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"WEEKLY","state":"BackedUp","tags":[]},
>
> {"id":"03ceeafc-83ac-40fa-85b1-a18464429206","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"MONTHLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:36-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100336","intervaltype":"MONTHLY","state":"BackedUp","tags":[]},
>
> {"id":"29524d7e-e420-4193-9169-0d3cc4b1c810","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:35-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100335","intervaltype":"DAILY","state":"BackedUp","tags":[]}
> ] } }
> However, listing the recurring schedule shows nothing:
> request:
> http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshotPolicies&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&volumeid=502&_=1354580037175
> response:
> { "listsnapshotpoliciesresponse" : { } }
--
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-2924) Recurring snapshot schedule not showing up in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Mehta resolved CLOUDSTACK-2924.
-
Resolution: Fixed
> Recurring snapshot schedule not showing up in UI
>
>
> Key: CLOUDSTACK-2924
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2924
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Nitin Mehta
>
> Issue is now exhibiting itself again:
> Volume id 502 has 4 snapshots, two DAILY, 1 WEEKLY, and 1 MONTHLY. Most
> recent snapshot is today.
> request:
> http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshots&listAll=true&page=1&pagesize=20&volumeid=502&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&_=1354580214377
> response:
> { "listsnapshotsresponse" : { "count":4 ,"snapshot" : [
> {"id":"0c2d17c1-a537-4d19-b83f-c13539d656a5","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"DAILY","state":"BackedUp","tags":[]},
>
> {"id":"d2438a81-6874-4e9b-8335-42c7f1d09691","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"WEEKLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"WEEKLY","state":"BackedUp","tags":[]},
>
> {"id":"03ceeafc-83ac-40fa-85b1-a18464429206","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"MONTHLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:36-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100336","intervaltype":"MONTHLY","state":"BackedUp","tags":[]},
>
> {"id":"29524d7e-e420-4193-9169-0d3cc4b1c810","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:35-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100335","intervaltype":"DAILY","state":"BackedUp","tags":[]}
> ] } }
> However, listing the recurring schedule shows nothing:
> request:
> http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshotPolicies&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&volumeid=502&_=1354580037175
> response:
> { "listsnapshotpoliciesresponse" : { } }
--
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-2924) Recurring snapshot schedule not showing up in UI
Nitin Mehta created CLOUDSTACK-2924:
---
Summary: Recurring snapshot schedule not showing up in UI
Key: CLOUDSTACK-2924
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2924
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Nitin Mehta
Issue is now exhibiting itself again:
Volume id 502 has 4 snapshots, two DAILY, 1 WEEKLY, and 1 MONTHLY. Most recent
snapshot is today.
request:
http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshots&listAll=true&page=1&pagesize=20&volumeid=502&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&_=1354580214377
response:
{ "listsnapshotsresponse" : { "count":4 ,"snapshot" : [
{"id":"0c2d17c1-a537-4d19-b83f-c13539d656a5","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"DAILY","state":"BackedUp","tags":[]},
{"id":"d2438a81-6874-4e9b-8335-42c7f1d09691","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"WEEKLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-03T02:03:38-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121203100338","intervaltype":"WEEKLY","state":"BackedUp","tags":[]},
{"id":"03ceeafc-83ac-40fa-85b1-a18464429206","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"MONTHLY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:36-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100336","intervaltype":"MONTHLY","state":"BackedUp","tags":[]},
{"id":"29524d7e-e420-4193-9169-0d3cc4b1c810","account":"profserv","domainid":"d7030e4e-f105-4996-bf82-bd4ec3e4cf38","domain":"PS","snapshottype":"DAILY","volumeid":"502","volumename":"i-8-478-VM-ROOT","volumetype":"ROOT","created":"2012-12-02T02:03:35-0800","name":"i-8-478-VM_i-8-478-VM-ROOT_20121202100335","intervaltype":"DAILY","state":"BackedUp","tags":[]}
] } }
However, listing the recurring schedule shows nothing:
request:
http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshotPolicies&response=json&sessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D&volumeid=502&_=1354580037175
response:
{ "listsnapshotpoliciesresponse" : { } }
--
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-2707) Usage server creates entries very slow for mysql performance degradation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679483#comment-13679483 ] ASF subversion and git services commented on CLOUDSTACK-2707: - Commit 76ce304411259dc4a29e0e070de829b79b46efe2 in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=76ce304 ] CLOUDSTACK-2707: use executeBatch instead of persist in Usage Server > Usage server creates entries very slow for mysql performance degradation > > > Key: CLOUDSTACK-2707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2707 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > > As we know, the insert performance into a mysql table degrades when the > records of table reaches 1,000,000. It takes more time and more CPU > utilization. > Here is log in usage.log > 2013-05-27 09:13:24,827 INFO [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) starting usage job... > 2013-05-27 09:13:24,829 INFO [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) Parsing usage records between Mon May 27 11:10:05 CEST > 2013 and Mon May 27 11:13:24 CEST 2013 > 2013-05-27 09:13:25,534 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 1252; abs: 847 > 2013-05-27 09:13:25,534 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 1252; abs: 847; curABS: 847; curABR: 1252; ubs: 0; ubr: 0 > 2013-05-27 09:13:26,467 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 16112; abs: 16112 > 2013-05-27 09:13:26,468 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 16112; abs: 16112; curABS: 16112; curABR: 16112; ubs: 0; ubr: 0 > 2013-05-27 09:13:28,220 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 0; abs: 0 > 2013-05-27 09:13:28,220 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 0; abs: 0; curABS: 0; curABR: 0; ubs: 0; ubr: 0 > 2013-05-27 09:13:29,266 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 3648; abs: 3648 > 2013-05-27 09:13:29,266 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 3648; abs: 3648; curABS: 3648; curABR: 3648; ubs: 0; ubr: 0 > 2013-05-27 09:13:30,339 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 32984; abs: 32984 > 2013-05-27 09:13:30,339 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 32984; abs: 32984; curABS: 32984; curABR: 32984; ubs: 0; ubr: 0 > 2013-05-27 09:13:31,830 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 118636; abs: 118940 > .. > 2013-05-27 09:16:08,285 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) getting current accounted bytes for... accountId: 2 in > zone: 1; abr: 0; abs: 0 > 2013-05-27 09:16:08,285 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) creating networkHelperEntry... accountId: 2 in zone: 1; > abr: 0; abs: 0; curABS: 0; curABR: 0; ubs: 0; ubr: 0 > 2013-05-27 09:16:09,308 DEBUG [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) created network stats helper entries for 134 accts -- 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-2922) System VM's agent dosent run in the Vmware setup with the latest System VM template.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679474#comment-13679474 ] Jayapal Reddy commented on CLOUDSTACK-2922: --- The issue is related to keys in vmware setup. When I tried to ssh to ssvm from the management server the ssh failed with permission denied (public key). I checked the public key of management server and authorised key those are different. So copied id_rsa.pub into authorised_keys of ssvm then ssh from the MS is success. [root@Kiran-RHEl631 ~]# ssh root@10.147.40.110 -p 3922 -i /var/cloudstack/management/.ssh/id_rsa > System VM's agent dosent run in the Vmware setup with the latest System VM > template. > > > Key: CLOUDSTACK-2922 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2922 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kiran Koneti >Priority: Blocker > > Tried creating a Advanced Zone with the new system VM template. > The System Vm's came up but the builtin template is not downloaded. > When tried to debug the cloud agent is not running in the SSVM. -- 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-2404) Document isolation in advanced zones using PVLAN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679463#comment-13679463 ] ASF subversion and git services commented on CLOUDSTACK-2404: - Commit 78811c50021202cb2374ceeb9edf0fdac5c66398 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=78811c5 ] CLOUDSTACK-2404 more conceptual info > Document isolation in advanced zones using PVLAN > > > Key: CLOUDSTACK-2404 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2404 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Radhika Nair > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2923) Delete Secondary storage of a Zone is giving java NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-2923. - Resolution: Fixed > Delete Secondary storage of a Zone is giving java NPE > - > > Key: CLOUDSTACK-2923 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2923 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Mehta > > Repro Steps: > 1.Create a Zone > 2. Create few VMs to it > 3.Delete Secondary storage > Bug: > Ms logs shows Java NPE > Expected Result: > Delete sceondary storage should not give any NPE > We are getting NPE in Ms log once we delete Secondary storage > MS Log shows : > 2012-11-16 13:36:23,370 WARN [cloud.vm.SystemVmLoadScanner] > (consoleproxy-1:null) Unexpected exception null > java.lang.NullPointerException > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:1177) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1894) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:166) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:101) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:30) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:79) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:69) > 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$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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-2923) Delete Secondary storage of a Zone is giving java NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679437#comment-13679437 ] ASF subversion and git services commented on CLOUDSTACK-2923: - Commit d8a235ee316af7d9b21ea62581c8b5c8925081d8 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d8a235e ] CLOUDSTACK-2923: Delete Secondary storage of a Zone was giving NPE bcz we were still refering to the object. Instead log that the cpvm and ssvm cant be created bcz sec storage is not available > Delete Secondary storage of a Zone is giving java NPE > - > > Key: CLOUDSTACK-2923 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2923 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Mehta > > Repro Steps: > 1.Create a Zone > 2. Create few VMs to it > 3.Delete Secondary storage > Bug: > Ms logs shows Java NPE > Expected Result: > Delete sceondary storage should not give any NPE > We are getting NPE in Ms log once we delete Secondary storage > MS Log shows : > 2012-11-16 13:36:23,370 WARN [cloud.vm.SystemVmLoadScanner] > (consoleproxy-1:null) Unexpected exception null > java.lang.NullPointerException > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:1177) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1894) > at > com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:166) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:101) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:30) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:79) > at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:69) > 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$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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] [Created] (CLOUDSTACK-2923) Delete Secondary storage of a Zone is giving java NPE
Nitin Mehta created CLOUDSTACK-2923: --- Summary: Delete Secondary storage of a Zone is giving java NPE Key: CLOUDSTACK-2923 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2923 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Mehta Repro Steps: 1.Create a Zone 2. Create few VMs to it 3.Delete Secondary storage Bug: Ms logs shows Java NPE Expected Result: Delete sceondary storage should not give any NPE We are getting NPE in Ms log once we delete Secondary storage MS Log shows : 2012-11-16 13:36:23,370 WARN [cloud.vm.SystemVmLoadScanner] (consoleproxy-1:null) Unexpected exception null java.lang.NullPointerException at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:1177) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1894) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:166) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:101) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:30) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:79) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:69) 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$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) 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] [Created] (CLOUDSTACK-2922) System VM's agent dosent run in the Vmware setup with the latest System VM template.
Kiran Koneti created CLOUDSTACK-2922: Summary: System VM's agent dosent run in the Vmware setup with the latest System VM template. Key: CLOUDSTACK-2922 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2922 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kiran Koneti Priority: Blocker Tried creating a Advanced Zone with the new system VM template. The System Vm's came up but the builtin template is not downloaded. When tried to debug the cloud agent is not running in the SSVM. -- 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-2915) NPE when creating network ACL item
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679428#comment-13679428 ] Prasanna Santhanam commented on CLOUDSTACK-2915: ~/workspace/cloudstack/incubator-cloudstack(branch:master*) » nosetests --with-marvin --marvin-config=setup/dev/advanced.cfg test/integration/component/test_vpc_network_pfrules.py --load tsp@cloud-2 Test : Create VPC PF rules on acquired public ip when VpcVirtualRouter is stopped ... ERROR Test Create VPC PF rules on acquired public ip when VpcVirtualRouter is Running ... ERROR Test Create multiple VPC PF rules on acquired public ip in diff't networks when VpcVirtualRouter is stopped ... ERROR Test Create multiple VPC PF rules on acquired public ip in diff't networks when VpcVirtualRouter is running ... ERROR Test delete a PF rule in VPC when VpcVirtualRouter is Stopped ... ERROR Test delete a PF rule in VPC when VpcVirtualRouter is Running ... ERROR Test delete all PF rules in VPC when VpcVirtualRouter is Stopped ... ERROR Test delete all PF rules in VPC when VpcVirtualRouter is Running ... ERROR Test delete all PF rules in VPC across multiple networks when VpcVirtualRouter is Stopped ... ERROR Test delete all PF rules in VPC across multiple networks when VpcVirtualRouter is Running ... ERROR All the above and more VPC tests fail because of the NPE > NPE when creating network ACL item > -- > > Key: CLOUDSTACK-2915 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2915 > 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: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > On creating a network ACL item following NPE is encountered and network ACL > creation fails > 2013-06-10 12:12:59,172 DEBUG [cloud.api.ApiServlet] > (1886622491@qtp-675153853-10:null) ===START=== 0:0:0:0:0:0:0:1%0 -- GET > networkid=84182b2d-52c0-4f47-bdf3-11df09cbd022&apiKey=tXflShMkw-k6smFTwQZ3Dq4MoyZNQzy2YqEU3STFIPdAEua9hSuLkldDG7AaJaYWKcaobhvMpLmk6v26X-j1fw&protocol=TCP&endport=&cidrlist=0.0.0.0%2F0&traffictype=Ingress&command=createNetworkACL&signature=MLJVyCeko3NydqcbEku833c9aOg%3D&action=Allow&startport=22&response=json > 2013-06-10 12:12:59,194 ERROR [cloud.api.ApiServer] > (1886622491@qtp-675153853-10:null) unhandled exception executing api command: > createNetworkACL > java.lang.NullPointerException > at > com.cloud.network.vpc.NetworkACLServiceImpl.createNetworkACLItem(NetworkACLServiceImpl.java:252) > at > org.apache.cloudstack.api.command.user.network.CreateNetworkACLCmd.create(CreateNetworkACLCmd.java:213) > at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:475) > 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:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) > 2013-06-10 12:12:59,195 DEBUG [cloud.api.ApiServlet]
[jira] [Commented] (CLOUDSTACK-2107) Only scaling up memory(ram) in not triggering vm live migration ;Unable to scale vm due to Catch exception com.xensource.xenapi.Types$HostNotEnoughFreeMemory when
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679422#comment-13679422
]
prashant kumar mishra commented on CLOUDSTACK-2107:
---
XS version - XS6.1
> Only scaling up memory(ram) in not triggering vm live migration ;Unable to
> scale vm due to Catch exception
> com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
> due to Not enough host memory is available to perform this operation
>
>
> Key: CLOUDSTACK-2107
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2107
> 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: Nitin Mehta
> Fix For: 4.2.0
>
> Attachments: access_log.2013-04-19.txt, apilog.log, catalina.out,
> management-server.log, MSlog.rar, RamScaleUp.png, xen.rar
>
>
> For cpu scalup ,vms getting live migrated to other host in cluster if no
> resources are available on current host ,but not in case of RAM Scaleup
> Steps to reproduce
>
> 1-Create zone->pod->cluster with one host
> 2-Deploy vm so that no resource left on host
> 3-Add another host in same cluster
> 4- Try to scale up vm's ram (in new service offering keep cpu speed same as
> previous ,increase ram by 500 MB)
> Expected
> --
> since there is no resource left on current host vm should get live migrate to
> other available host and scaleup should be successful .
> Actual
> -
> scaleup failed due to not enough resource on current host,;CS did not try to
> live migrate vm to other host on cluster
> My observation
> --
> 1-VM are getting live migrated in case of cpu scale up if current host does
> not have resource
> 2-Tried to scaleup vm to service offering x failed but able to deploy a new
> vm with same service offering
> Service offering details
> --
> Tried to scaleup from SO 20 to SO 22
> 1-SO 22
> mysql> select * from service_offering_view where id=22 \G
> *** 1. row ***
>id: 22
> uuid: 528443f5-f044-4e64-b1e1-87f6c0136921
> name: smallcpu2ram
> display_text: smallcpu2ram
> created: 2013-04-18 18:48:17
> tags: NULL
> removed: NULL
> use_local_storage: 0
>system_use: 0
> cpu: 1
> speed: 1500
> ram_size: 1024
> nw_rate: NULL
> mc_rate: NULL
>ha_enabled: 0
> limit_cpu_use: 0
> host_tag: NULL
> default_use: 0
> vm_type: NULL
> sort_key: 0
> domain_id: NULL
> domain_uuid: NULL
> domain_name: NULL
> domain_path: NULL
> 1 row in set (0.00 sec)
> 2-SO 20
> mysql> select * from service_offering_view where id=20 \G
> *** 1. row ***
>id: 20
> uuid: 4bafd8c7-c8cc-42db-a630-61909556803b
> name: smallcpu2
> display_text: smallcpu2
> created: 2013-04-18 18:39:59
> tags: NULL
> removed: NULL
> use_local_storage: 0
>system_use: 0
> cpu: 1
> speed: 1500
> ram_size: 500
> nw_rate: NULL
> mc_rate: NULL
>ha_enabled: 0
> limit_cpu_use: 0
> host_tag: NULL
> default_use: 0
> vm_type: NULL
> sort_key: 5
> domain_id: NULL
> domain_uuid: NULL
> domain_name: NULL
> domain_path: NULL
> 1 row in set (0.00 sec)
> Snippet of MS Log
> ---
> 2013-04-19 07:40:58,312 DEBUG [agent.transport.Request] (DirectAgent-12:null)
> Seq 1-521863179: Processing: { Ans: , MgmtId: 7191687856187, via: 1, Ver:
> v1, Flags: 110, [{"ScaleVmAnswer":{"result":false,"details":"Catch exception
> com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
> due to Not enough host memory is available to perform this
> operation","wait":0}}] }
> 2013-04-19 07:40:58,312 DEBUG [agent.transport.Request]
> (catalina-exec-6:null) Seq 1-521863179: Received: { Ans: , MgmtId:
> 7191687856187, via: 1, Ver: v1, Flags: 110, { ScaleVmAnswer } }
> 2013-04-19 07:40:58,312 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-6:null) Unable to scale vm due to Catch exception
> com.xensource.xenapi.
[jira] [Created] (CLOUDSTACK-2921) Fix stopped_vm testcases
Girish Shilamkar created CLOUDSTACK-2921: Summary: Fix stopped_vm testcases Key: CLOUDSTACK-2921 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2921 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Reporter: Girish Shilamkar Assignee: Girish Shilamkar Fix test_stopped_vm testcases failures http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/23/suite=test_stopped_vm/testReport/? -- 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-2920) VPC network from shared network offering for VPC does not work
Prasanna Santhanam created CLOUDSTACK-2920: -- Summary: VPC network from shared network offering for VPC does not work Key: CLOUDSTACK-2920 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2920 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: Prasanna Santhanam Fix For: 4.2.0 Can we create shared networks inside a VPC? If yes - why does the UI filter out the network offerings in the VPC dialog on listing networks using forvpc=true & guestiptype=Isolated? If no - we can get rid of a test suite - TestVMLifeCycleSharedNwVPC. But was it supported before and dropped recently? I was able to create a networkoffering with vpc=true and guestIpType=Shared, but the VPC network creation fails with """ Network offering can't be used for VPC networks """ -- 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-2915) NPE when creating network ACL item
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679413#comment-13679413 ] ASF subversion and git services commented on CLOUDSTACK-2915: - Commit 20c1f2c3466926163ccf0fe1487b3ca61d35da07 in branch refs/heads/master from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20c1f2c ] CLOUDSTACK-2914: lbScheme Public should be specified in NetworkOffering NetworkOfferings now require a mandatory scheme in the serviceCapabilityList to create a VPC loadbalancer on the public side. This commit fixes the test for VPC networks. Additionally there needs to be a fix for making this the default behaviour so as not to hurt the backwards compatibility. test still fails because of CLOUDSTACK-2915 however which is a related network ACL backwards compat issue. See bug for more details. Signed-off-by: Prasanna Santhanam > NPE when creating network ACL item > -- > > Key: CLOUDSTACK-2915 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2915 > 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: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > On creating a network ACL item following NPE is encountered and network ACL > creation fails > 2013-06-10 12:12:59,172 DEBUG [cloud.api.ApiServlet] > (1886622491@qtp-675153853-10:null) ===START=== 0:0:0:0:0:0:0:1%0 -- GET > networkid=84182b2d-52c0-4f47-bdf3-11df09cbd022&apiKey=tXflShMkw-k6smFTwQZ3Dq4MoyZNQzy2YqEU3STFIPdAEua9hSuLkldDG7AaJaYWKcaobhvMpLmk6v26X-j1fw&protocol=TCP&endport=&cidrlist=0.0.0.0%2F0&traffictype=Ingress&command=createNetworkACL&signature=MLJVyCeko3NydqcbEku833c9aOg%3D&action=Allow&startport=22&response=json > 2013-06-10 12:12:59,194 ERROR [cloud.api.ApiServer] > (1886622491@qtp-675153853-10:null) unhandled exception executing api command: > createNetworkACL > java.lang.NullPointerException > at > com.cloud.network.vpc.NetworkACLServiceImpl.createNetworkACLItem(NetworkACLServiceImpl.java:252) > at > org.apache.cloudstack.api.command.user.network.CreateNetworkACLCmd.create(CreateNetworkACLCmd.java:213) > at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:475) > 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:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) > 2013-06-10 12:12:59,195 DEBUG [cloud.api.ApiServlet] > (1886622491@qtp-675153853-10:null) ===END=== 0:0:0:0:0:0:0:1%0 -- GET > networkid=84182b2d-52c0-4f47-bdf3-11df09cbd022&apiKey=tXflShMkw-k6smFTwQZ3Dq4MoyZNQzy2YqEU3STFIPdAEua9hSuLkldDG7AaJaYWKcaobhvMpLmk6v26X-j1fw&protocol=TCP&endport=&cidrlist=0.0.0.0%2F0&traffictype=Ingress&command=createNetworkACL&signature=MLJVyCeko3NydqcbEku833c9aOg%3D&action=Allow&startport=22&response=json -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please co
[jira] [Commented] (CLOUDSTACK-2914) Regression: With introduction of internal lb provider one must specify the lbScheme when creating network offerings (backward compat)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679412#comment-13679412
]
ASF subversion and git services commented on CLOUDSTACK-2914:
-
Commit 20c1f2c3466926163ccf0fe1487b3ca61d35da07 in branch refs/heads/master
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20c1f2c ]
CLOUDSTACK-2914: lbScheme Public should be specified in NetworkOffering
NetworkOfferings now require a mandatory scheme in the
serviceCapabilityList to create a VPC loadbalancer on the public side.
This commit fixes the test for VPC networks. Additionally there needs to
be a fix for making this the default behaviour so as not to hurt the
backwards compatibility.
test still fails because of CLOUDSTACK-2915 however which is a related
network ACL backwards compat issue. See bug for more details.
Signed-off-by: Prasanna Santhanam
> Regression: With introduction of internal lb provider one must specify the
> lbScheme when creating network offerings (backward compat)
> -
>
> Key: CLOUDSTACK-2914
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2914
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Doc, Network Controller
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Critical
> Fix For: 4.2.0
>
>
> If you choose to have LB in your VPC (by default on the public side) you will
> need to specify the lbScheme in the serviceCapability list when creating the
> network offering or LB creation when the network is implemented will fail.
> Following automated test fails:
> :setup (from nosetests)
> Failing for the past 14 builds (Since #11 )
> Took 16 min.
> add description
> Error Message
> Execute cmd: createloadbalancerrule failed, due to: errorCode: 530,
> errorText:Failed to create load balancer rule: SSH
> Stacktrace
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
> line 208, in run
> self.setUp()
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
> line 291, in setUp
> self.setupContext(ancestor)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
> line 314, in setupContext
> try_run(context, names)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/util.py",
> line 469, in try_run
> return func()
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/test/integration/component/test_vpc_network.py",
> line 2238, in setUpClass
> domainid=cls.account.domainid
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 1498, in create
> return LoadBalancerRule(apiclient.createLoadBalancerRule(cmd).__dict__)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 893, in createLoadBalancerRule
> response = self.connection.marvin_request(command,
> response_type=response, method=method)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 223, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/jsonHelper.py",
> line 128, in getResultObj
> raise
> cloudstackException.cloudstackAPIException(responseName.replace("response",
> ""), errMsg)
> cloudstackAPIException: Execute cmd: createloadbalancerrule failed, due to:
> errorCode: 530, errorText:Failed to create load balancer rule: SSH
> In the management server logs:
> WARN [network.lb.LoadBalancingRulesManagerImpl]
> (1347080201@qtp-675153853-0:) Failed to create load balancer due to
> com.cloud.exception.InvalidParameterValueException: Scheme Public is not
> supported by the network offering [Network Offering [14-Guest-VPC Network
> offering-P5GNGX]
> at
> com.cloud.network.lb.LoadBalancingRulesManagerImpl.isLbServiceSupportedInNetwork(LoadBalancingRulesManagerImpl.java:2103)
> at
> com.cloud.network.lb.LoadBalancingRulesMa
[jira] [Commented] (CLOUDSTACK-2107) Only scaling up memory(ram) in not triggering vm live migration ;Unable to scale vm due to Catch exception com.xensource.xenapi.Types$HostNotEnoughFreeMemory when
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679409#comment-13679409
]
Nitin Mehta commented on CLOUDSTACK-2107:
-
Prashant - Can you also tell me the version of XS ?
> Only scaling up memory(ram) in not triggering vm live migration ;Unable to
> scale vm due to Catch exception
> com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
> due to Not enough host memory is available to perform this operation
>
>
> Key: CLOUDSTACK-2107
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2107
> 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: Nitin Mehta
> Fix For: 4.2.0
>
> Attachments: access_log.2013-04-19.txt, apilog.log, catalina.out,
> management-server.log, MSlog.rar, RamScaleUp.png, xen.rar
>
>
> For cpu scalup ,vms getting live migrated to other host in cluster if no
> resources are available on current host ,but not in case of RAM Scaleup
> Steps to reproduce
>
> 1-Create zone->pod->cluster with one host
> 2-Deploy vm so that no resource left on host
> 3-Add another host in same cluster
> 4- Try to scale up vm's ram (in new service offering keep cpu speed same as
> previous ,increase ram by 500 MB)
> Expected
> --
> since there is no resource left on current host vm should get live migrate to
> other available host and scaleup should be successful .
> Actual
> -
> scaleup failed due to not enough resource on current host,;CS did not try to
> live migrate vm to other host on cluster
> My observation
> --
> 1-VM are getting live migrated in case of cpu scale up if current host does
> not have resource
> 2-Tried to scaleup vm to service offering x failed but able to deploy a new
> vm with same service offering
> Service offering details
> --
> Tried to scaleup from SO 20 to SO 22
> 1-SO 22
> mysql> select * from service_offering_view where id=22 \G
> *** 1. row ***
>id: 22
> uuid: 528443f5-f044-4e64-b1e1-87f6c0136921
> name: smallcpu2ram
> display_text: smallcpu2ram
> created: 2013-04-18 18:48:17
> tags: NULL
> removed: NULL
> use_local_storage: 0
>system_use: 0
> cpu: 1
> speed: 1500
> ram_size: 1024
> nw_rate: NULL
> mc_rate: NULL
>ha_enabled: 0
> limit_cpu_use: 0
> host_tag: NULL
> default_use: 0
> vm_type: NULL
> sort_key: 0
> domain_id: NULL
> domain_uuid: NULL
> domain_name: NULL
> domain_path: NULL
> 1 row in set (0.00 sec)
> 2-SO 20
> mysql> select * from service_offering_view where id=20 \G
> *** 1. row ***
>id: 20
> uuid: 4bafd8c7-c8cc-42db-a630-61909556803b
> name: smallcpu2
> display_text: smallcpu2
> created: 2013-04-18 18:39:59
> tags: NULL
> removed: NULL
> use_local_storage: 0
>system_use: 0
> cpu: 1
> speed: 1500
> ram_size: 500
> nw_rate: NULL
> mc_rate: NULL
>ha_enabled: 0
> limit_cpu_use: 0
> host_tag: NULL
> default_use: 0
> vm_type: NULL
> sort_key: 5
> domain_id: NULL
> domain_uuid: NULL
> domain_name: NULL
> domain_path: NULL
> 1 row in set (0.00 sec)
> Snippet of MS Log
> ---
> 2013-04-19 07:40:58,312 DEBUG [agent.transport.Request] (DirectAgent-12:null)
> Seq 1-521863179: Processing: { Ans: , MgmtId: 7191687856187, via: 1, Ver:
> v1, Flags: 110, [{"ScaleVmAnswer":{"result":false,"details":"Catch exception
> com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
> due to Not enough host memory is available to perform this
> operation","wait":0}}] }
> 2013-04-19 07:40:58,312 DEBUG [agent.transport.Request]
> (catalina-exec-6:null) Seq 1-521863179: Received: { Ans: , MgmtId:
> 7191687856187, via: 1, Ver: v1, Flags: 110, { ScaleVmAnswer } }
> 2013-04-19 07:40:58,312 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-6:null) Unable to scale vm due to Catch exception
> com.xens
[jira] [Commented] (CLOUDSTACK-2919) Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Secondary Storage locations
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679398#comment-13679398 ] Nitin Mehta commented on CLOUDSTACK-2919: - For a snapshot operation, following enhancements are required. 1. Before trying to backup snapshot, introduce an allocator to take considerations like size, load, previous snapshots etc. in consideration so that a more refined decision can be taken for choosing sec. storage 2. If for some case backingup snapshot on one sec. storage fails, have a retry mechanism to back it up on other sec. storage especially when the previous sec. storage has been down or has some size issues etc. > Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other > Secondary Storage locations > - > > Key: CLOUDSTACK-2919 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2919 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Nitin Mehta > Fix For: 4.2.0 > > > This issue was noticed when the customer attempted to take a snapshot but > failed. > Logs revealed that the Secondary Storage to which CS was trying to save the > Snapshot had no more free space. > CS did retry multiple times to save to the same Secondary Storage location > after the initial failure but with no success. > However, CS failed to notice two other Secondary Storage locations in the same > zone with enough free space for a successful snapshot. -- 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-2919) Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Secondary Storage locations
Nitin Mehta created CLOUDSTACK-2919: --- Summary: Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Secondary Storage locations Key: CLOUDSTACK-2919 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2919 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Fix For: 4.2.0 This issue was noticed when the customer attempted to take a snapshot but failed. Logs revealed that the Secondary Storage to which CS was trying to save the Snapshot had no more free space. CS did retry multiple times to save to the same Secondary Storage location after the initial failure but with no success. However, CS failed to notice two other Secondary Storage locations in the same zone with enough free space for a successful snapshot. -- 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-2918) In a scaled up environment, hosts fail to come up after Management server restart in clustered set up
Sowmya Krishnan created CLOUDSTACK-2918: --- Summary: In a scaled up environment, hosts fail to come up after Management server restart in clustered set up Key: CLOUDSTACK-2918 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2918 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: Load Test environment with simulator Reporter: Sowmya Krishnan Fix For: 4.2.0 Scaled setup with 20K simulated hosts and as many VMs, Basic Zone, Clustered setup with 3 management servers. After restarting one or all the Management servers, re balancing hosts takes very long time, and the rebalanced hosts don't come to Up state either. Following is the error message from logs when the MS was starting up: 2013-05-31 00:00:22,361 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Joining node, IP: 10.223.48.2, msid: 206915885094132 2013-05-31 00:00:22,361 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Joining node, IP: 10.223.48.66, msid: 206915885097283 2013-05-31 00:00:22,362 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Receive cluster alert, EventArgs: com.cloud.cluster.ClusterNodeJoinEventArgs 2013-05-31 00:00:22,362 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Handle cluster node join alert, joined node: 10.223.48.2, msidL: 206915885094132 2013-05-31 00:00:22,362 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Handle cluster node join alert, joined node: 10.223.48.66, msidL: 206915885097283 2013-05-31 00:00:22,362 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Management server node 10.223.48.66 is up, send alert 2013-05-31 00:00:22,539 WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notifying management server join event took 178 ms 2013-05-31 00:00:25,825 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management server heartbeat takes too long to finish. profiler: Done. Duration: 5583ms, profilerH eartbeatUpdate: Done. Duration: 187ms, profilerPeerScan: Done. Duration: 560ms, profilerAgentLB: Done. Duration: 4836ms 2013-05-31 00:00:25,963 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Detected management node joined, id:3, nodeIP:10.223.48.130 2013-05-31 00:00:25,964 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notify management server node join to listeners. 2013-05-31 00:00:25,964 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Joining node, IP: 10.223.48.130, msid: 206915885093830 2013-05-31 00:00:25,964 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Receive cluster alert, EventArgs: com.cloud.cluster.ClusterNodeJoinEventArgs 2013-05-31 00:00:25,964 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Handle cluster node join alert, joined node: 10.223.48.130, msidL: 206915885093830 2013-05-31 00:00:25,964 WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notifying management server join event took 0 ms 2013-05-31 00:00:27,501 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management server heartbeat takes too long to finish. profiler: Done. Duration: 1675ms, profilerH eartbeatUpdate: Done. Duration: 135ms, profilerPeerScan: Done. Duration: 179ms, profilerAgentLB: Done. Duration: 1361ms 2013-05-31 00:00:29,389 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management server heartbeat takes too long to finish. profiler: Done. Duration: 1888ms, profilerH eartbeatUpdate: Done. Duration: 462ms, profilerPeerScan: Done. Duration: 2ms, profilerAgentLB: Done. Duration: 1424ms 2013-05-31 00:00:33,912 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management server heartbeat takes too long to finish. profiler: Done. Duration: 1643ms, profilerH eartbeatUpdate: Done. Duration: 141ms, profilerPeerScan: Done. Duration: 1ms, profilerAgentLB: Done. Duration: 1501ms 2013-05-31 00:00:41,328 DEBUG [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Management server heartbeat takes too long to finish. profiler: Done. Duration: 1675ms, profilerH eartbeatUpdate: Done. Duration: 178ms, profilerPeerScan: Done. Duration: 2ms, profilerAgentLB: Done. Duration: 1495ms 2013-05-31 00:00:48,799 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Running Capacity Checker ... 2013-05-31 00:00:48,805 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) recalculating system capacity 2013-05-31 00:00:48,805 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Executing cpu/ram capacity update 2013-05-31 00:00:48,883 DEB
[jira] [Assigned] (CLOUDSTACK-2914) Regression: With introduction of internal lb provider one must specify the lbScheme when creating network offerings (backward compat)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanna Santhanam reassigned CLOUDSTACK-2914:
--
Assignee: (was: Prasanna Santhanam)
Unassigning for the server side engineer to take a look
> Regression: With introduction of internal lb provider one must specify the
> lbScheme when creating network offerings (backward compat)
> -
>
> Key: CLOUDSTACK-2914
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2914
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Doc, Network Controller
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Critical
> Fix For: 4.2.0
>
>
> If you choose to have LB in your VPC (by default on the public side) you will
> need to specify the lbScheme in the serviceCapability list when creating the
> network offering or LB creation when the network is implemented will fail.
> Following automated test fails:
> :setup (from nosetests)
> Failing for the past 14 builds (Since #11 )
> Took 16 min.
> add description
> Error Message
> Execute cmd: createloadbalancerrule failed, due to: errorCode: 530,
> errorText:Failed to create load balancer rule: SSH
> Stacktrace
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
> line 208, in run
> self.setUp()
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
> line 291, in setUp
> self.setupContext(ancestor)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
> line 314, in setupContext
> try_run(context, names)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/util.py",
> line 469, in try_run
> return func()
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/test/integration/component/test_vpc_network.py",
> line 2238, in setUpClass
> domainid=cls.account.domainid
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/integration/lib/base.py",
> line 1498, in create
> return LoadBalancerRule(apiclient.createLoadBalancerRule(cmd).__dict__)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 893, in createLoadBalancerRule
> response = self.connection.marvin_request(command,
> response_type=response, method=method)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
> line 223, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
> File
> "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/jsonHelper.py",
> line 128, in getResultObj
> raise
> cloudstackException.cloudstackAPIException(responseName.replace("response",
> ""), errMsg)
> cloudstackAPIException: Execute cmd: createloadbalancerrule failed, due to:
> errorCode: 530, errorText:Failed to create load balancer rule: SSH
> In the management server logs:
> WARN [network.lb.LoadBalancingRulesManagerImpl]
> (1347080201@qtp-675153853-0:) Failed to create load balancer due to
> com.cloud.exception.InvalidParameterValueException: Scheme Public is not
> supported by the network offering [Network Offering [14-Guest-VPC Network
> offering-P5GNGX]
> at
> com.cloud.network.lb.LoadBalancingRulesManagerImpl.isLbServiceSupportedInNetwork(LoadBalancingRulesManagerImpl.java:2103)
> at
> com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancer(LoadBalancingRulesManagerImpl.java:1401)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1329)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.loadbalancer.CreateLoadBalancerRuleCmd.create(CreateLoadBalancerRuleCmd.java:281)
> at com.cloud
[jira] [Assigned] (CLOUDSTACK-2891) Management server gets stuck when we try to add only a single vlan as a range , ex- try to add 615-615
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty reassigned CLOUDSTACK-2891: -- Assignee: Likitha Shetty > Management server gets stuck when we try to add only a single vlan as a range > , ex- try to add 615-615 > -- > > Key: CLOUDSTACK-2891 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2891 > 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: Abhinav Roy >Assignee: Likitha Shetty >Priority: Critical > Fix For: 4.2.0 > > > Steps : > = > 1. Deploy a CS setup with advanced network zone. > 2. Goto Infrastructure -> Zone -> Zone-1 -> Physical Network -> Guest and try > to add a vlan range like 100-100 or 200-200 or anything like that > or > Fire this api : > http://10.102.192.125:8096/client/api?command=updatePhysicalNetwork&id=200&vlan=100-100 > Observed behaviour : > > 1. The UI gets stuck and we need to restart management server to get it to a > working state. > 2. In the Logs the queryAsyncJobResult API keeps querying the job for a very > long time. -- 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-2917) Router vm failed to start after setting up "network.throttling.rate" to 0.1 (100Kbit/sec)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2917: -- Attachment: Logs.rar > Router vm failed to start after setting up "network.throttling.rate" to 0.1 > (100Kbit/sec) > - > > Key: CLOUDSTACK-2917 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2917 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: Logs.rar > > > Tried to set "Network throttling rate to 100Kb/sec, VR failed to start. > Steps to Repro > -- > 1-Stop VR > 2-set GP "network.throttling.rate" to 0.1(100Kbit/sec) > 3-Restart MS > 4-Start router > Expected > -- > VR should come up > Actual > -- > VR failed to start > Log > - > 2013-06-10 08:59:12,777 ERROR [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-2:job-45) Failed to start instance VM[DomainRouter|r-12-VM] > java.lang.NumberFormatException: For input string: "0.1" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:481) > at java.lang.Integer.parseInt(Integer.java:514) > at > com.cloud.configuration.ConfigurationManagerImpl.getServiceOfferingNetworkRate(ConfigurationManagerImpl.java:4633) > at > com.cloud.network.NetworkModelImpl.getNetworkRate(NetworkModelImpl.java:945) > at > com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2032) > at > com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2021) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:842) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2720) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1861) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3118) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3068) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110) > 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-10 08:59:12,796 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-2:job-45) Cleaning up resources for the vm > VM[DomainRouter|r-12-VM] in Starting state -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2917) Router vm failed to start after setting up "network.throttling.rate" to 0.1 (100Kbit/sec)
prashant kumar mishra created CLOUDSTACK-2917: - Summary: Router vm failed to start after setting up "network.throttling.rate" to 0.1 (100Kbit/sec) Key: CLOUDSTACK-2917 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2917 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: prashant kumar mishra Fix For: 4.2.0 Tried to set "Network throttling rate to 100Kb/sec, VR failed to start. Steps to Repro -- 1-Stop VR 2-set GP "network.throttling.rate" to 0.1(100Kbit/sec) 3-Restart MS 4-Start router Expected -- VR should come up Actual -- VR failed to start Log - 2013-06-10 08:59:12,777 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-2:job-45) Failed to start instance VM[DomainRouter|r-12-VM] java.lang.NumberFormatException: For input string: "0.1" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:481) at java.lang.Integer.parseInt(Integer.java:514) at com.cloud.configuration.ConfigurationManagerImpl.getServiceOfferingNetworkRate(ConfigurationManagerImpl.java:4633) at com.cloud.network.NetworkModelImpl.getNetworkRate(NetworkModelImpl.java:945) at com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2032) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2021) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:842) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2720) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1861) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3118) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3068) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110) 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-10 08:59:12,796 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-2:job-45) Cleaning up resources for the vm VM[DomainRouter|r-12-VM] in Starting state -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2915) NPE when creating network ACL item
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679357#comment-13679357 ] Prasanna Santhanam commented on CLOUDSTACK-2915: Seems we need to associate the aclid (derived from networkid) when creating a network ACL. If not specified this is derived from the network, but previously deployed networks will have aclid as NULL mysql> select * from networks where uuid='228aa30b-a36d-460f-b2fe-3891040047bc'\G *** 1. row *** id: 209 name: Test Network uuid: 228aa30b-a36d-460f-b2fe-3891040047bc display_text: Test Network traffic_type: Guest broadcast_domain_type: Vlan broadcast_uri: vlan://104 gateway: 10.1.1.1 cidr: 10.1.1.0/24 mode: Dhcp network_offering_id: 19 physical_network_id: 200 data_center_id: 1 guru_name: ExternalGuestNetworkGuru state: Implemented related: 209 domain_id: 1 account_id: 7 dns1: NULL dns2: NULL guru_data: NULL set_fields: 0 acl_type: Account network_domain: cs7sandbox.simulator reservation_id: a2479c0b-f8ba-4d82-aebe-26aadb9a9379 guest_type: Isolated restart_required: 0 created: 2013-06-10 07:05:04 removed: NULL specify_ip_ranges: 0 vpc_id: 6 ip6_gateway: NULL ip6_cidr: NULL network_cidr: NULL display_network: 1 network_acl_id: NULL 1 row in set (0.00 sec) > NPE when creating network ACL item > -- > > Key: CLOUDSTACK-2915 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2915 > 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: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > On creating a network ACL item following NPE is encountered and network ACL > creation fails > 2013-06-10 12:12:59,172 DEBUG [cloud.api.ApiServlet] > (1886622491@qtp-675153853-10:null) ===START=== 0:0:0:0:0:0:0:1%0 -- GET > networkid=84182b2d-52c0-4f47-bdf3-11df09cbd022&apiKey=tXflShMkw-k6smFTwQZ3Dq4MoyZNQzy2YqEU3STFIPdAEua9hSuLkldDG7AaJaYWKcaobhvMpLmk6v26X-j1fw&protocol=TCP&endport=&cidrlist=0.0.0.0%2F0&traffictype=Ingress&command=createNetworkACL&signature=MLJVyCeko3NydqcbEku833c9aOg%3D&action=Allow&startport=22&response=json > 2013-06-10 12:12:59,194 ERROR [cloud.api.ApiServer] > (1886622491@qtp-675153853-10:null) unhandled exception executing api command: > createNetworkACL > java.lang.NullPointerException > at > com.cloud.network.vpc.NetworkACLServiceImpl.createNetworkACLItem(NetworkACLServiceImpl.java:252) > at > org.apache.cloudstack.api.command.user.network.CreateNetworkACLCmd.create(CreateNetworkACLCmd.java:213) > at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:475) > 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:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.
[jira] [Updated] (CLOUDSTACK-2916) admin is not able to login through UI after setting GP "cluster.cpu.allocated.capacity.notificationthreshold" to some string
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-2916:
--
Attachment: logs.rar
> admin is not able to login through UI after setting GP
> "cluster.cpu.allocated.capacity.notificationthreshold" to some string
> --
>
> Key: CLOUDSTACK-2916
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2916
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
>Reporter: prashant kumar mishra
> Fix For: 4.2.0
>
> Attachments: logs.rar
>
>
> Steps to Reproduce
> -
> 1-Set GP "cluster.cpu.allocated.capacity.notificationthreshold" to some
> string ("asda")
> 2- restart MS
> 3-try to login through UI
> Expected
> --
> Admin should be able to login
> Actual
> -
> Admin is not able to login
> Snippet of Log
> --
> 2013-06-10 08:05:53,893 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-19:null) Attempting to log in user: admin in domain 1
> 2013-06-10 08:05:53,893 DEBUG [server.auth.SHA256SaltedUserAuthenticator]
> (catalina-exec-19:null) Retrieving user: admin
> 2013-06-10 08:05:53,909 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-19:null) User: admin in domain 1 has successfully logged in
> 2013-06-10 08:05:53,943 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
> ===END=== 10.252.192.33 -- POST null
> 2013-06-10 08:05:54,065 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===START=== 10.252.192.33 -- GET
> command=listCapabilities&response=json&sessionkey=K1c%2FHMQLGtYXIwatCDmQW8tlN9s%3D&_=1370846503258
> 2013-06-10 08:05:54,082 DEBUG [cloud.api.ApiServer] (catalina-exec-21:null)
> The given command:listCapabilities does not exist or it is not available for
> user with id:2
> 2013-06-10 08:05:54,085 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===END=== 10.252.192.33 -- GET
> command=listCapabilities&response=json&sessionkey=K1c%2FHMQLGtYXIwatCDmQW8tlN9s%3D&_=1370846503258
> 2013-06-10 08:05:54,184 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
> ===START=== 10.252.192.33 -- GET
> command=listSwifts&response=json&sessionkey=K1c%2FHMQLGtYXIwatCDmQW8tlN9s%3D&_=1370846503357
> 2013-06-10 08:05:54,210 DEBUG [cloud.api.ApiServer] (catalina-exec-5:null)
> The given command:listSwifts does not exist or it is not available for user
> with id:2
> 2013-06-10 08:05:54,213 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
> ===END=== 10.252.192.33 -- GET
> command=listSwifts&response=json&sessionkey=K1c%2FHMQLGtYXIwatCDmQW8tlN9s%3D&_=1370846503357
--
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
