[jira] [Commented] (CLOUDSTACK-5591) [VMWare][64-bit template]Public network is not reachable by the System Vm's.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859846#comment-13859846 ] Jayapal Reddy commented on CLOUDSTACK-5591: --- This issue is not reproduced in my setup. Here are debug info: root@s-6-VM:~# uname -a Linux s-6-VM 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux root@s-6-VM:~# root@s-6-VM:~# ifconfig eth1 Link encap:Ethernet HWaddr 06:f6:c6:00:00:07 inet addr:10.147.41.127 Bcast:10.147.41.255 Mask:255.255.254.0 inet6 addr: fe80::4f6:c6ff:fe00:7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:445 errors:0 dropped:0 overruns:0 frame:0 TX packets:188 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:33771 (32.9 KiB) TX bytes:27180 (26.5 KiB) eth2 Link encap:Ethernet HWaddr 06:bb:f0:00:00:0c inet addr:10.147.52.101 Bcast:10.147.52.255 Mask:255.255.255.0 inet6 addr: fe80::4bb:f0ff:fe00:c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:43 errors:0 dropped:0 overruns:0 frame:0 TX packets:47 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4298 (4.1 KiB) TX bytes:4110 (4.0 KiB) eth3 Link encap:Ethernet HWaddr 06:5b:cc:00:00:04 inet addr:10.147.41.124 Bcast:10.147.41.255 Mask:255.255.254.0 inet6 addr: fe80::45b:ccff:fe00:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:195 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11752 (11.4 KiB) TX bytes:478 (478.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:168 (168.0 B) TX bytes:168 (168.0 B) root@s-6-VM:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.147.52.1 0.0.0.0 UG0 00 eth2 10.147.40.0 0.0.0.0 255.255.254.0 U 0 00 eth1 10.147.40.0 0.0.0.0 255.255.254.0 U 0 00 eth3 10.147.52.0 0.0.0.0 255.255.255.0 U 0 00 eth2 10.147.59.0 10.147.40.1 255.255.255.0 UG0 00 eth1 10.147.59.206 10.147.40.1 255.255.255.255 UGH 0 00 eth1 10.223.240.232 10.147.40.1 255.255.255.255 UGH 0 00 eth1 root@s-6-VM:~# ping google.com PING google.com (74.125.239.136): 48 data bytes 56 bytes from 74.125.239.136: icmp_seq=0 ttl=45 time=245.253 ms 56 bytes from 74.125.239.136: icmp_seq=1 ttl=45 time=242.582 ms ^C--- google.com ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 242.582/243.917/245.253/1.336 ms root@s-6-VM:~# root@s-6-VM:~# arp -a ? (10.147.40.1) at 00:19:b9:8c:8e:3a [ether] on eth1 ? (10.147.52.1) at 00:19:b9:8c:8e:3a [ether] on eth2 root@s-6-VM:~# root@s-6-VM:~# iptables -L -nv Chain INPUT (policy DROP 22 packets, 1768 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 160 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 0 0 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 519 36553 ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 54 4592 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 icmptype 13 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 509 packets, 61428 bytes) pk
[jira] [Resolved] (CLOUDSTACK-5591) [VMWare][64-bit template]Public network is not reachable by the System Vm's.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-5591. --- Resolution: Cannot Reproduce > [VMWare][64-bit template]Public network is not reachable by the System Vm's. > > > Key: CLOUDSTACK-5591 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5591 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0 >Reporter: Kiran Koneti >Assignee: Jayapal Reddy >Priority: Blocker > Fix For: 4.3.0 > > > The setup details are as follows: > 1)Installed the CS setup and changed the global setting to allow the download > from the internal sites. > 2)Created a Advanced Zone setup with Vmware 5.5 where the system Vm's came up. > 3)Then added one more cluster for the KVm and added a KVM host. > 4)After adding the KVM ost the system Vm template for the KVM was not ready > and it shows as connection timed out. > 5)Then logged into the SSVM and tried to ping the public network then the > network was not reachable,even the default gateway was not pingable. > 6)When stopped the IP tables the gateway was pingable. > 7)When tried to check the arp of the gw using "arping the gatewayIP" it says > the eth0 is down and when eth0 is made up the ping was successful and the > public network was reachable. > 8)Then tried to restart the SSVM again the situation is same that the public > network is not reachable. > 9)If we leave the stup for longer time without making any changes the Public > network will be reachable and when rebooted again the network will not be > reached again. > The Iptables details are as below: > "iptables -L -nv > Chain INPUT (policy DROP 4 packets, 312 bytes) > pkts bytes target prot opt in out source > destination > 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:443 > 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:80 > 160 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:3922 > 0 0 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 547 95190 ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 2 262 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED >10 588 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 > 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 >icmptype 13 > 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 > 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:3922 > Chain FORWARD (policy DROP 0 packets, 0 bytes) > pkts bytes target prot opt in out source > destination > Chain OUTPUT (policy ACCEPT 493 packets, 76135 bytes) > pkts bytes target prot opt in out source > destination > 0 0 ACCEPT tcp -- * eth10.0.0.0/0 > 10.147.28.0/24 state NEW tcp > 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 >state NEW tcp dpt:80 reject-with icmp-port-unreachable > 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 >state NEW tcp dpt:443 reject-with icmp-port-unreachable > Chain HTTP (0 references) > pkts bytes target prot opt in out source > destination" > The arping request is as below: > arping 10.147.X.X > Interface "eth0" is down -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5678) Cold Storage migration is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-5678:
---
Assignee: Kelven Yang (was: Devdeep Singh)
> Cold Storage migration is failing
> -
>
> Key: CLOUDSTACK-5678
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5678
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: hyperv , 4.3
>Reporter: Abhinav Roy
>Assignee: Kelven Yang
>Priority: Blocker
> Labels: vmsync
> Fix For: 4.3.0
>
>
> Steps to Reproduce:
>
> 1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS
> for both primary and secondary storage
> 2.Deploy one or two guest vms using default cent os template.
> 3.Add one more primary storage (say primary2) to the cluster
> 4.Stop one of the vms deployed at step2
> 5.Migrate the storage from source primary to new primary storage primary2
> Expected Result:
> =
> Storage migration should succeed when the vm is in stopped state
> Actual Result:
> ===
> 013-12-30 17:21:03,163 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-6:ctx-9672ce4b) ===START=== 10.144.7.20 -- GET
> command=migrateVirtualMachine&storageid=d65ffa8c-fdd7-360a-b729-c0d9ba5df050&virtualmachineid=9226ccd6-b409-4452-821f-5b33a24137a5&response=json&sessionkey=lIed4xLaMsDL4yCyAJYyUK0pAJk%3D&_=1388403965445
> 2013-12-30 17:21:03,194 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-6:ctx-9672ce4b ctx-5d353029) submit async job-129, details:
> AsyncJobVO {id:129, userId: 2, accountId: 2, instanceType: None, instanceId:
> null, cmd: org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
> {"response":"json","sessionkey":"lIed4xLaMsDL4yCyAJYyUK0pAJk\u003d","virtualmachineid":"9226ccd6-b409-4452-821f-5b33a24137a5","cmdEventType":"VM.MIGRATE","ctxUserId":"2","storageid":"d65ffa8c-fdd7-360a-b729-c0d9ba5df050","httpmethod":"GET","_":"1388403965445","ctxAccountId":"2","ctxStartEventId":"274"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-30 17:21:03,194 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-6:ctx-9672ce4b ctx-5d353029) ===END=== 10.144.7.20 -- GET
> command=migrateVirtualMachine&storageid=d65ffa8c-fdd7-360a-b729-c0d9ba5df050&virtualmachineid=9226ccd6-b409-4452-821f-5b33a24137a5&response=json&sessionkey=lIed4xLaMsDL4yCyAJYyUK0pAJk%3D&_=1388403965445
> 2013-12-30 17:21:03,196 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-48:ctx-46f6bd2b) Add job-129 into job monitoring
> 2013-12-30 17:21:03,196 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-48:ctx-46f6bd2b) Executing AsyncJobVO {id:129, userId: 2,
> accountId: 2, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
> {"response":"json","sessionkey":"lIed4xLaMsDL4yCyAJYyUK0pAJk\u003d","virtualmachineid":"9226ccd6-b409-4452-821f-5b33a24137a5","cmdEventType":"VM.MIGRATE","ctxUserId":"2","storageid":"d65ffa8c-fdd7-360a-b729-c0d9ba5df050","httpmethod":"GET","_":"1388403965445","ctxAccountId":"2","ctxStartEventId":"274"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-30 17:21:03,212 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-48:ctx-46f6bd2b ctx-5d353029) Rolling back the transaction:
> Time = 4 Name = Job-Executor-48; called by
> -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.migrateVmStorageThroughJobQueue:4475-VirtualMachineManagerImpl.storageMigration:1558-UserVmManagerImpl.vmStorageMigration:4069-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616
> 2013-12-30 17:21:03,213 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-48:ctx-46f6bd2b) Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkStorageMigration@40df9e44
> at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
> at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
> at
> com.cloud.vm.VirtualMachineManagerImpl$9.doInTransactionWithoutResult(VirtualMachineMa
[jira] [Updated] (CLOUDSTACK-5675) Destory VM is failing with "Unable to delete vm snapshots for VM"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-5675:
---
Assignee: Kelven Yang (was: Devdeep Singh)
> Destory VM is failing with "Unable to delete vm snapshots for VM"
> --
>
> Key: CLOUDSTACK-5675
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5675
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: Hyperv , 4.3
>Reporter: Abhinav Roy
>Assignee: Kelven Yang
>Priority: Blocker
> Labels: vmsync
> Fix For: 4.3.0
>
>
> Steps :
> ===
> 1. Deploy a CS advanced zone setup with Hyper-V as hypervisor type
> 2. Create a VM
> 3. Destroy the VM
> Expected result:
> ==
> The VM should be created and destroyed successfully.
> Observed result :
> =
> Destroy VM fails with :
> 2013-12-30 15:02:30,297 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-2:ctx-57d2f51b) ===START=== 10.144.7.20 -- GET
> command=destroyVirtualMachine&response=json&sessionkey=P7hUEU1kTW2jFEVpcBKYxFUSxx4%3D&id=706fae35-94d2-414d-94da-8c7b21051edd&expunge=true&_=1388396154899
> 2013-12-30 15:02:30,344 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-2:ctx-57d2f51b ctx-03d0a162) submit async job-38, details:
> AsyncJobVO {id:38, userId: 2, accountId: 2, instanceType: VirtualMachine,
> instanceId: 6, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd,
> cmdInfo:
> {"response":"json","id":"706fae35-94d2-414d-94da-8c7b21051edd","sessionkey":"P7hUEU1kTW2jFEVpcBKYxFUSxx4\u003d","cmdEventType":"VM.DESTROY","ctxUserId":"2","httpmethod":"GET","_":"1388396154899","ctxAccountId":"2","expunge":"true","ctxStartEventId":"108"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-30 15:02:30,344 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-2:ctx-57d2f51b ctx-03d0a162) ===END=== 10.144.7.20 -- GET
> command=destroyVirtualMachine&response=json&sessionkey=P7hUEU1kTW2jFEVpcBKYxFUSxx4%3D&id=706fae35-94d2-414d-94da-8c7b21051edd&expunge=true&_=1388396154899
> 2013-12-30 15:02:30,346 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-41:ctx-90d46ce0) Add job-38 into job monitoring
> 2013-12-30 15:02:30,346 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-41:ctx-90d46ce0) Executing AsyncJobVO {id:38, userId: 2,
> accountId: 2, instanceType: VirtualMachine, instanceId: 6, cmd:
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdInfo:
> {"response":"json","id":"706fae35-94d2-414d-94da-8c7b21051edd","sessionkey":"P7hUEU1kTW2jFEVpcBKYxFUSxx4\u003d","cmdEventType":"VM.DESTROY","ctxUserId":"2","httpmethod":"GET","_":"1388396154899","ctxAccountId":"2","expunge":"true","ctxStartEventId":"108"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-30 15:02:30,371 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Destroying vm VM[User|av3]
> 2013-12-30 15:02:30,372 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Stopped called on VM[User|av3]
> but the state is Error
> 2013-12-30 15:02:30,404 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-41:ctx-90d46ce0 ctx-03d0a162) Sync job-39 execution on object
> VmWorkJobQueue.6
> 2013-12-30 15:02:31,064 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-2:ctx-1f663345) StorageCollector is running...
> 2013-12-30 15:02:31,125 DEBUG [c.c.a.t.Request]
> (StatsCollector-2:ctx-1f663345) Seq 2-1575288891: Received: { Ans: , MgmtId:
> 280320865129348, via: 2, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-12-30 15:02:31,127 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-15:ctx-9d56111c) Seq 1-2099445910: Executing request
> 2013-12-30 15:02:31,128 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-15:ctx-9d56111c) POST request
> tohttp://10.102.192.14:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
> with
> contents{"id":"b183fb1d-c446-3a6f-b7ee-ec18507f39ae","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u003dabhinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-30 15:02:31,128 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-15:ctx-9d56111c) Sending cmd to
> http://10.102.192.14:8250/api/HypervResource/com.cloud.agent.api.Get
[jira] [Updated] (CLOUDSTACK-5676) Live migration of VM is failing with a NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-5676:
---
Assignee: Kelven Yang (was: Devdeep Singh)
> Live migration of VM is failing with a NPE
> --
>
> Key: CLOUDSTACK-5676
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5676
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: hyperv , 4.3
>Reporter: Abhinav Roy
>Assignee: Kelven Yang
>Priority: Blocker
> Labels: vmsync
> Fix For: 4.3.0
>
>
> Steps to Reproduce:
>
> 1.Bring up CS in advanced zone with 2 hosts in a hyper-v cluster using CIFS
> for both primary and secondary storage
> 2.Deploy one or two guest vms using default cent os template.
> 3.Migrate one of the VMs from Host1 to Host2
> Expected Behaviour:
> =
> Live VM migration should be successful
> Observed Behaviour:
> ===
> Live VM migration fails with :
> 013-12-30 16:41:29,564 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-1:ctx-2ba86ed3 ctx-ca0be041) Sync job-95 execution on object
> VmWorkJobQueue.16
> 2013-12-30 16:41:31,261 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-c85fb697) Execute sync-queue item:
> SyncQueueItemVO {id:30, queueId: 27, contentType: AsyncJob, contentId: 95,
> lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null,
> created: Mon Dec 30 16:41:29 IST 2013}
> 2013-12-30 16:41:31,263 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-c85fb697) Schedule queued job-95
> 2013-12-30 16:41:31,277 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-2:ctx-ba975c56) Add job-95 into job monitoring
> 2013-12-30 16:41:31,278 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-2:ctx-ba975c56) Executing AsyncJobVO {id:95, userId: 2,
> accountId: 2, instanceType: null, instanceId: null, cmd:
> com.cloud.vm.VmWorkMigrate, cmdInfo:
> rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAEHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwAEcQB-AAlwcQB-AAk,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Mon Dec 30 16:41:29 IST 2013}
> 2013-12-30 16:41:31,279 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Job-Executor-2:ctx-ba975c56) Run VM work job: com.cloud.vm.VmWorkMigrate
> 2013-12-30 16:41:31,287 ERROR [c.c.v.VmWorkJobDispatcher]
> (Job-Executor-2:ctx-ba975c56 ctx-ca0be041) Unable to complete AsyncJobVO
> {id:95, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
> com.cloud.vm.VmWorkMigrate, cmdInfo:
> rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAEHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwAEcQB-AAlwcQB-AAk,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 280320865129348, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Mon Dec 30 16:41:29 IST 2013}
> java.lang.NullPointerException
> at
> com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
> at
> com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4743)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.call
[jira] [Created] (CLOUDSTACK-5704) Inconsistent way OVA/OVF files are created for templates
Likitha Shetty created CLOUDSTACK-5704: -- Summary: Inconsistent way OVA/OVF files are created for templates Key: CLOUDSTACK-5704 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5704 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Priority: Critical Fix For: 4.3.0 With the fix provided for [https://issues.apache.org/jira/browse/CLOUDSTACK-671], CS is not supposed not to keep OVA file with a template and snapshots. There is no OVA saved and kept with a snapshot. But there is inconsistent behavior with regards to templates. Templates that are created from snapshots don't have OVA file whereas templates created from volumes have OVA file that consumes storage and causes longer template creation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5704) OVA files exist for templates created from volumes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-5704: --- Summary: OVA files exist for templates created from volumes (was: Inconsistent way OVA/OVF files are created for templates) > OVA files exist for templates created from volumes > -- > > Key: CLOUDSTACK-5704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5704 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, VMware >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Likitha Shetty >Priority: Critical > Fix For: 4.3.0 > > > With the fix provided for > [https://issues.apache.org/jira/browse/CLOUDSTACK-671], CS is not supposed > not to keep OVA file with a template and snapshots. > There is no OVA saved and kept with a snapshot. But there is inconsistent > behavior with regards to templates. Templates that are created from snapshots > don't have OVA file whereas templates created from volumes have OVA file that > consumes storage and causes longer template creation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5605) [Hyper-V] Fix GetStorageStatsCommand for Hyper-V
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859849#comment-13859849
]
ASF subversion and git services commented on CLOUDSTACK-5605:
-
Commit 4d05056252779b32c057ae85c53b1596a5ad072f in branch refs/heads/4.3 from
[~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4d05056 ]
CLOUDSTACK-5605: Fixing GetStorage stats command for hyper-v. The agent
wasn't looking up the share path correctly for reading the stats of a smb
share.
> [Hyper-V] Fix GetStorageStatsCommand for Hyper-V
>
>
> Key: CLOUDSTACK-5605
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5605
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
> Environment: Hyper-V setup, Advanced zone
>Reporter: Sowmya Krishnan
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: Hyper-V, hyper-V,, hyperv
> Fix For: 4.3.0
>
>
> Create an advanced zone set up with Hyper-V.
> Logs keep showing the following exceptions during Stats collection for
> Storage:
> 2013-12-22 21:52:05,122 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) POST request
> tohttp://10.102.192.14:8250/api/HypervResou
> rce/com.cloud.agent.api.GetStorageStatsCommand with
> contents{"id":"ce50406b-9038-37ba-9b72-6228d5eb0858","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u00
> 3dabhinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-22 21:52:05,122 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) Sending cmd to
> http://10.102.192.14:8250/api/HypervResou
> rce/com.cloud.agent.api.GetStorageStatsCommand cmd
> data:{"id":"ce50406b-9038-37ba-9b72-6228d5eb0858","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u003dab
> hinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-22 21:52:05,131 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) POST response
> is[{"com.cloud.agent.api.GetStorageStatsAn
> swer":{"result":false,"details":"com.cloud.agent.api.GetStorageStatsCommand
> failed on exceptionIllegal characters in
> path.","capacity":0,"used":0,"contextMap
> ":{}}}]
> 2013-12-22 21:52:05,131 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) executeRequest received response
> [{"com.cloud.agent.api.
> GetStorageStatsAnswer":{"used":0,"capacity":0,"result":false,"details":"com.cloud.agent.api.GetStorageStatsCommand
> failed on exceptionIllegal characters in p
> ath.","contextMap":{},"wait":0}}]
> Following are the agent side logs:
> 2013-12-18 12:18:57,596 [42] INFO HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] -
> com.cloud.agent.api.GetStorageStatsCommand{
> "id": "ce50406b-9038-37ba-9b72-6228d5eb0858",
> "localPath":
> "/HYPERV-SMB/abhinav-hyperv-ps1?user=abhinav&password=freebsd@123&domain=BLR",
> "pooltype": "NetworkFilesystem",
> "contextMap": {},
> "wait": 0
> }
> 2013-12-18 12:18:57,596 [42] ERROR HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] -
> com.cloud.agent.api.GetStorageStatsCommand failed on exceptionIllegal
> characters in path.
> System.ArgumentException: Illegal characters in path.
>at System.IO.Path.CheckInvalidPathChars(String path, Boolean
> checkAdditional)
>at
> System.Security.Permissions.FileIOPermission.CheckIllegalCharacters(String[]
> str)
>at
> System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> access, AccessControlActions control, String[] pathListOrig, Boolean
> checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
>at
> System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
>at System.IO.Path.GetFullPath(String path)
>at HypervResource.HypervResourceController.GetCapacityForLocalPath(String
> localStoragePath, Int64& capacityBytes, Int64& availableBytes) in
> c:\source_code\cloudstack\plugins\hypervisors\hyperv\DotNet\ServerResource\HypervResource\HypervResourceController.cs:line
> 1798
>at HypervResource.HypervResourceController.GetStorageStatsCommand(Object
> cmd) in
> c:\source_code\cloudstack\plugins\hypervisors\hyperv\DotNet\ServerResource\HypervResource\HypervResourceController.cs:line
> 1497
> 2013-12-18 12:18:57,596 [42] INFO HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] - {
>
[jira] [Commented] (CLOUDSTACK-5605) [Hyper-V] Fix GetStorageStatsCommand for Hyper-V
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859850#comment-13859850
]
ASF subversion and git services commented on CLOUDSTACK-5605:
-
Commit faa503d6fc5b6f7ef7ef9d63d15d07b392675d13 in branch refs/heads/master
from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=faa503d ]
CLOUDSTACK-5605: Fixing GetStorage stats command for hyper-v. The agent
wasn't looking up the share path correctly for reading the stats of a smb
share.
> [Hyper-V] Fix GetStorageStatsCommand for Hyper-V
>
>
> Key: CLOUDSTACK-5605
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5605
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
> Environment: Hyper-V setup, Advanced zone
>Reporter: Sowmya Krishnan
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: Hyper-V, hyper-V,, hyperv
> Fix For: 4.3.0
>
>
> Create an advanced zone set up with Hyper-V.
> Logs keep showing the following exceptions during Stats collection for
> Storage:
> 2013-12-22 21:52:05,122 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) POST request
> tohttp://10.102.192.14:8250/api/HypervResou
> rce/com.cloud.agent.api.GetStorageStatsCommand with
> contents{"id":"ce50406b-9038-37ba-9b72-6228d5eb0858","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u00
> 3dabhinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-22 21:52:05,122 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) Sending cmd to
> http://10.102.192.14:8250/api/HypervResou
> rce/com.cloud.agent.api.GetStorageStatsCommand cmd
> data:{"id":"ce50406b-9038-37ba-9b72-6228d5eb0858","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u003dab
> hinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-22 21:52:05,131 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) POST response
> is[{"com.cloud.agent.api.GetStorageStatsAn
> swer":{"result":false,"details":"com.cloud.agent.api.GetStorageStatsCommand
> failed on exceptionIllegal characters in
> path.","capacity":0,"used":0,"contextMap
> ":{}}}]
> 2013-12-22 21:52:05,131 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) executeRequest received response
> [{"com.cloud.agent.api.
> GetStorageStatsAnswer":{"used":0,"capacity":0,"result":false,"details":"com.cloud.agent.api.GetStorageStatsCommand
> failed on exceptionIllegal characters in p
> ath.","contextMap":{},"wait":0}}]
> Following are the agent side logs:
> 2013-12-18 12:18:57,596 [42] INFO HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] -
> com.cloud.agent.api.GetStorageStatsCommand{
> "id": "ce50406b-9038-37ba-9b72-6228d5eb0858",
> "localPath":
> "/HYPERV-SMB/abhinav-hyperv-ps1?user=abhinav&password=freebsd@123&domain=BLR",
> "pooltype": "NetworkFilesystem",
> "contextMap": {},
> "wait": 0
> }
> 2013-12-18 12:18:57,596 [42] ERROR HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] -
> com.cloud.agent.api.GetStorageStatsCommand failed on exceptionIllegal
> characters in path.
> System.ArgumentException: Illegal characters in path.
>at System.IO.Path.CheckInvalidPathChars(String path, Boolean
> checkAdditional)
>at
> System.Security.Permissions.FileIOPermission.CheckIllegalCharacters(String[]
> str)
>at
> System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> access, AccessControlActions control, String[] pathListOrig, Boolean
> checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
>at
> System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
>at System.IO.Path.GetFullPath(String path)
>at HypervResource.HypervResourceController.GetCapacityForLocalPath(String
> localStoragePath, Int64& capacityBytes, Int64& availableBytes) in
> c:\source_code\cloudstack\plugins\hypervisors\hyperv\DotNet\ServerResource\HypervResource\HypervResourceController.cs:line
> 1798
>at HypervResource.HypervResourceController.GetStorageStatsCommand(Object
> cmd) in
> c:\source_code\cloudstack\plugins\hypervisors\hyperv\DotNet\ServerResource\HypervResource\HypervResourceController.cs:line
> 1497
> 2013-12-18 12:18:57,596 [42] INFO HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] - {
>
[jira] [Resolved] (CLOUDSTACK-5605) [Hyper-V] Fix GetStorageStatsCommand for Hyper-V
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5605.
---
Resolution: Fixed
> [Hyper-V] Fix GetStorageStatsCommand for Hyper-V
>
>
> Key: CLOUDSTACK-5605
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5605
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.3.0
> Environment: Hyper-V setup, Advanced zone
>Reporter: Sowmya Krishnan
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: Hyper-V, hyper-V,, hyperv
> Fix For: 4.3.0
>
>
> Create an advanced zone set up with Hyper-V.
> Logs keep showing the following exceptions during Stats collection for
> Storage:
> 2013-12-22 21:52:05,122 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) POST request
> tohttp://10.102.192.14:8250/api/HypervResou
> rce/com.cloud.agent.api.GetStorageStatsCommand with
> contents{"id":"ce50406b-9038-37ba-9b72-6228d5eb0858","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u00
> 3dabhinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-22 21:52:05,122 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) Sending cmd to
> http://10.102.192.14:8250/api/HypervResou
> rce/com.cloud.agent.api.GetStorageStatsCommand cmd
> data:{"id":"ce50406b-9038-37ba-9b72-6228d5eb0858","localPath":"/HYPERV-SMB/abhinav-hyperv-ps1?user\u003dab
> hinav\u0026password\u003dfreebsd@123\u0026domain\u003dBLR","pooltype":"NetworkFilesystem","contextMap":{},"wait":0}
> 2013-12-22 21:52:05,131 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) POST response
> is[{"com.cloud.agent.api.GetStorageStatsAn
> swer":{"result":false,"details":"com.cloud.agent.api.GetStorageStatsCommand
> failed on exceptionIllegal characters in
> path.","capacity":0,"used":0,"contextMap
> ":{}}}]
> 2013-12-22 21:52:05,131 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-387:ctx-bb8cfa79) executeRequest received response
> [{"com.cloud.agent.api.
> GetStorageStatsAnswer":{"used":0,"capacity":0,"result":false,"details":"com.cloud.agent.api.GetStorageStatsCommand
> failed on exceptionIllegal characters in p
> ath.","contextMap":{},"wait":0}}]
> Following are the agent side logs:
> 2013-12-18 12:18:57,596 [42] INFO HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] -
> com.cloud.agent.api.GetStorageStatsCommand{
> "id": "ce50406b-9038-37ba-9b72-6228d5eb0858",
> "localPath":
> "/HYPERV-SMB/abhinav-hyperv-ps1?user=abhinav&password=freebsd@123&domain=BLR",
> "pooltype": "NetworkFilesystem",
> "contextMap": {},
> "wait": 0
> }
> 2013-12-18 12:18:57,596 [42] ERROR HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] -
> com.cloud.agent.api.GetStorageStatsCommand failed on exceptionIllegal
> characters in path.
> System.ArgumentException: Illegal characters in path.
>at System.IO.Path.CheckInvalidPathChars(String path, Boolean
> checkAdditional)
>at
> System.Security.Permissions.FileIOPermission.CheckIllegalCharacters(String[]
> str)
>at
> System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> access, AccessControlActions control, String[] pathListOrig, Boolean
> checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
>at
> System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
>at System.IO.Path.GetFullPath(String path)
>at HypervResource.HypervResourceController.GetCapacityForLocalPath(String
> localStoragePath, Int64& capacityBytes, Int64& availableBytes) in
> c:\source_code\cloudstack\plugins\hypervisors\hyperv\DotNet\ServerResource\HypervResource\HypervResourceController.cs:line
> 1798
>at HypervResource.HypervResourceController.GetStorageStatsCommand(Object
> cmd) in
> c:\source_code\cloudstack\plugins\hypervisors\hyperv\DotNet\ServerResource\HypervResource\HypervResourceController.cs:line
> 1497
> 2013-12-18 12:18:57,596 [42] INFO HypervResource.HypervResourceController
> [06b343ed-9619-4af0-b80a-e3f96b9bc53d] - {
> "com.cloud.agent.api.GetStorageStatsAnswer": {
> "result": false,
> "details": "com.cloud.agent.api.GetStorageStatsCommand failed on
> exceptionIllegal characters in path.",
> "capacity": 0,
> "used": 0,
> "contextMap": {}
> }
> }
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5705) [Hyper-V] Thumbnail for console of hyperv is not working
Anshul Gangwar created CLOUDSTACK-5705: -- Summary: [Hyper-V] Thumbnail for console of hyperv is not working Key: CLOUDSTACK-5705 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5705 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Anshul Gangwar Assignee: Anshul Gangwar Priority: Critical Fix For: 4.3.0 Thumbnail for console of hyperv is not working -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5701) physical size is not getting updated in snapshot_store_ref table.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-5701: --- Priority: Critical (was: Major) > physical size is not getting updated in snapshot_store_ref table. > - > > Key: CLOUDSTACK-5701 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5701 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.1 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.3.0 > > > Physical size is not getting updated in snapshot_store_ref table. Because of > that, CS doesn't has any record of delta snapshots size created in XenServer. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5705) [Hyper-V] Thumbnail for console of hyperv is not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-5705: --- Labels: hyper-V, (was: ) > [Hyper-V] Thumbnail for console of hyperv is not working > > > Key: CLOUDSTACK-5705 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5705 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Thumbnail for console of hyperv is not working -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5706) Multiple NPEs when host is put in maintenance after upgrading from 4.2.1 to 4.3
manasaveloori created CLOUDSTACK-5706:
-
Summary: Multiple NPEs when host is put in maintenance after
upgrading from 4.2.1 to 4.3
Key: CLOUDSTACK-5706
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5706
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Upgrade
Affects Versions: 4.3.0
Environment: upgraded the CS from 4.2.1 to 4.3
Reporter: manasaveloori
Priority: Critical
Fix For: 4.3.0
Steps:
1. Deployed CS 4.2.1 GA build with ESXi5.1(using Vsphere 5.1 client)
2. Deployed some VMs.
3. Upgraded the CS to 4.3.
4. Put the host into maintenance which will be successful.
Observed the following NPEs in MSlogs.
2014-01-01 20:17:11,749 DEBUG [c.c.a.ApiServlet] (catalina-exec-15:ctx-e389
ctx-1ab4f80c) ===END=== 10.252.192.34 -- GET
command=prepareHostForMaintenance&id=dbd66102-e51e-4014-be75-e7ac8ccb81f1&response=json&sessionkey=ble18kT0VfY%2BEPq8V8DzAZsM8L0%3D&_=1388568267594
2014-01-01 20:17:11,752 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-118:ctx-e4cb1a1d) Add job-166 into job monitoring
2014-01-01 20:17:11,752 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-118:ctx-e4cb1a1d) Executing AsyncJobVO {id:166, userId: 2,
accountId: 2, instanceType: Host, instanceId: 4, cmd:
org.apache.cloudstack.api.command.admin.host.PrepareForMaintenanceCmd, cmdInfo:
{"response":"json","id":"dbd66102-e51e-4014-be75-e7ac8ccb81f1","sessionkey":"ble18kT0VfY+EPq8V8DzAZsM8L0\u003d","cmdEventType":"MAINT.PREPARE","ctxUserId":"2","httpmethod":"GET","_":"1388568267594","ctxAccountId":"2","ctxStartEventId":"758"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 6758231703598, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-01-01 20:17:11,782 DEBUG [c.c.a.t.Request] (Job-Executor-118:ctx-e4cb1a1d
ctx-1ab4f80c) Seq 4-1399914503: Sending { Cmd , MgmtId: 6758231703598, via:
4(10.147.40.28), Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.MaintainCommand":{"wait":0}}] }
2014-01-01 20:17:11,782 DEBUG [c.c.a.t.Request] (Job-Executor-118:ctx-e4cb1a1d
ctx-1ab4f80c) Seq 4-1399914503: Executing: { Cmd , MgmtId: 6758231703598, via:
4(10.147.40.28), Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.MaintainCommand":{"wait":0}}] }
2014-01-01 20:17:11,806 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: Executing request
2014-01-01 20:17:11,807 INFO [c.c.h.v.r.VmwareResource]
(DirectAgent-410:ctx-32cc846b 10.147.40.28) Executing resource MaintainCommand:
{"wait":0}
2014-01-01 20:17:11,814 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: Response Received:
2014-01-01 20:17:11,814 DEBUG [c.c.a.t.Request] (DirectAgent-410:ctx-32cc846b)
Seq 4-1399914503: Processing: { Ans: , MgmtId: 6758231703598, via: 4, Ver: v1,
Flags: 110,
[{"com.cloud.agent.api.MaintainAnswer":{"willMigrate":true,"result":true,"details":"Put
host in maintaince","wait":0}}] }
2014-01-01 20:17:11,815 DEBUG [c.c.a.t.Request] (Job-Executor-118:ctx-e4cb1a1d
ctx-1ab4f80c) Seq 4-1399914503: Received: { Ans: , MgmtId: 6758231703598, via:
4, Ver: v1, Flags: 110, { MaintainAnswer } }
2014-01-01 20:17:11,815 DEBUG [c.c.a.m.AgentManagerImpl]
(Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Details from executing class
com.cloud.agent.api.MaintainCommand: Put host in maintaince
2014-01-01 20:17:11,817 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: No more commands found
2014-01-01 20:17:11,834 DEBUG [c.c.r.ResourceState]
(Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Resource state update: [id = 4;
name = 10.147.40.28; old state = Enabled; event = AdminAskMaintenace; new state
= PrepareForMaintenance]
2014-01-01 20:17:11,834 DEBUG [c.c.a.m.AgentAttache]
(Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Seq 4-1399914499: Sending
disconnect to class com.cloud.network.security.SecurityGroupListener
2014-01-01 20:17:11,888 DEBUG [c.c.h.HighAvailabilityManagerImpl]
(Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Scheduled
HAWork[44-ForceStop-9-Running-Scheduled]
2014-01-01 20:17:11,910 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-0:ctx-07bb080c work-44) Processing
HAWork[44-ForceStop-9-Running-Scheduled]
2014-01-01 20:17:11,917 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-0:ctx-07bb080c work-44) Stopping VM[DomainRouter|r-9-VM]
2014-01-01 20:17:11,920 ERROR [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-0:ctx-07bb080c work-44) Terminating
HAWork[44-ForceStop-9-Running-Scheduled]
java.lang.NullPointerException
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1264)
at
com.cloud.ha.HighAvailabilityManagerImpl.stopVM(HighAvailabilityManage
[jira] [Updated] (CLOUDSTACK-5706) Multiple NPEs when host is put in maintenance after upgrading from 4.2.1 to 4.3
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-5706:
--
Attachment: management-server.rar
> Multiple NPEs when host is put in maintenance after upgrading from 4.2.1 to
> 4.3
> ---
>
> Key: CLOUDSTACK-5706
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5706
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade
>Affects Versions: 4.3.0
> Environment: upgraded the CS from 4.2.1 to 4.3
>Reporter: manasaveloori
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.rar
>
>
> Steps:
> 1.Deployed CS 4.2.1 GA build with ESXi5.1(using Vsphere 5.1 client)
> 2.Deployed some VMs.
> 3.Upgraded the CS to 4.3.
> 4. Put the host into maintenance which will be successful.
> Observed the following NPEs in MSlogs.
> 2014-01-01 20:17:11,749 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-15:ctx-e389 ctx-1ab4f80c) ===END=== 10.252.192.34 -- GET
> command=prepareHostForMaintenance&id=dbd66102-e51e-4014-be75-e7ac8ccb81f1&response=json&sessionkey=ble18kT0VfY%2BEPq8V8DzAZsM8L0%3D&_=1388568267594
> 2014-01-01 20:17:11,752 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-118:ctx-e4cb1a1d) Add job-166 into job monitoring
> 2014-01-01 20:17:11,752 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-118:ctx-e4cb1a1d) Executing AsyncJobVO {id:166, userId: 2,
> accountId: 2, instanceType: Host, instanceId: 4, cmd:
> org.apache.cloudstack.api.command.admin.host.PrepareForMaintenanceCmd,
> cmdInfo:
> {"response":"json","id":"dbd66102-e51e-4014-be75-e7ac8ccb81f1","sessionkey":"ble18kT0VfY+EPq8V8DzAZsM8L0\u003d","cmdEventType":"MAINT.PREPARE","ctxUserId":"2","httpmethod":"GET","_":"1388568267594","ctxAccountId":"2","ctxStartEventId":"758"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6758231703598, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-01-01 20:17:11,782 DEBUG [c.c.a.t.Request]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Seq 4-1399914503: Sending { Cmd
> , MgmtId: 6758231703598, via: 4(10.147.40.28), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.MaintainCommand":{"wait":0}}] }
> 2014-01-01 20:17:11,782 DEBUG [c.c.a.t.Request]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Seq 4-1399914503: Executing: {
> Cmd , MgmtId: 6758231703598, via: 4(10.147.40.28), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.MaintainCommand":{"wait":0}}] }
> 2014-01-01 20:17:11,806 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: Executing request
> 2014-01-01 20:17:11,807 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-410:ctx-32cc846b 10.147.40.28) Executing resource
> MaintainCommand: {"wait":0}
> 2014-01-01 20:17:11,814 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: Response Received:
> 2014-01-01 20:17:11,814 DEBUG [c.c.a.t.Request]
> (DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: Processing: { Ans: ,
> MgmtId: 6758231703598, via: 4, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.MaintainAnswer":{"willMigrate":true,"result":true,"details":"Put
> host in maintaince","wait":0}}] }
> 2014-01-01 20:17:11,815 DEBUG [c.c.a.t.Request]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Seq 4-1399914503: Received: {
> Ans: , MgmtId: 6758231703598, via: 4, Ver: v1, Flags: 110, { MaintainAnswer }
> }
> 2014-01-01 20:17:11,815 DEBUG [c.c.a.m.AgentManagerImpl]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Details from executing class
> com.cloud.agent.api.MaintainCommand: Put host in maintaince
> 2014-01-01 20:17:11,817 DEBUG [c.c.a.m.AgentAttache]
> (DirectAgent-410:ctx-32cc846b) Seq 4-1399914503: No more commands found
> 2014-01-01 20:17:11,834 DEBUG [c.c.r.ResourceState]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Resource state update: [id = 4;
> name = 10.147.40.28; old state = Enabled; event = AdminAskMaintenace; new
> state = PrepareForMaintenance]
> 2014-01-01 20:17:11,834 DEBUG [c.c.a.m.AgentAttache]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Seq 4-1399914499: Sending
> disconnect to class com.cloud.network.security.SecurityGroupListener
> 2014-01-01 20:17:11,888 DEBUG [c.c.h.HighAvailabilityManagerImpl]
> (Job-Executor-118:ctx-e4cb1a1d ctx-1ab4f80c) Scheduled
> HAWork[44-ForceStop-9-Running-Scheduled]
> 2014-01-01 20:17:11,910 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-0:ctx-07bb080c work-44) Processing
> HAWork[44-ForceStop-9-Running-Scheduled]
> 2014-01-01 20:17:11,917 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-Worker-0:ctx-0
[jira] [Commented] (CLOUDSTACK-5705) [Hyper-V] Thumbnail for console of hyperv is not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859853#comment-13859853 ] ASF subversion and git services commented on CLOUDSTACK-5705: - Commit 0b643ddf09f25b569d7219de026aeda144a3b33f in branch refs/heads/4.3 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0b643dd ] CLOUDSTACK-5705: fixed the thumbnail not wrking for hyperv > [Hyper-V] Thumbnail for console of hyperv is not working > > > Key: CLOUDSTACK-5705 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5705 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Thumbnail for console of hyperv is not working -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5707) Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 5.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-5707: -- Attachment: management-server.rar > Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from > 5.1 > --- > > Key: CLOUDSTACK-5707 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5707 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.3.0 > Environment: Upgraded the CS 4.2.1 to 4.3 with ESXi5.1 using Vsphere > client 5.1 > Upgraded the Vsphere client to 5.5 >Reporter: manasaveloori >Priority: Critical > Fix For: 4.3.0 > > Attachments: management-server.rar > > > Steps followed: > 1.Deployed CS 4.2.1 GA build with ESXi5.1(using Vsphere 5.1 client) > 2.Deployed some VMs. > 3.Upgraded the CS to 4.3. > 4.Now unmanaged the cluster, kept the host in maintenance . > 5.Upgraded the Vsphere client to 5.5 > (http://www.vmadmin.co.uk/vmware/36-virtualcenter/284-vsphere4to5upgradevcenter41to5) > 6.Manage the cluster and cancelled the maintenance mode on host. > 7.Host is connected. > Observing the following exceptions in Ms logs: > 014-01-01 20:03:35,467 DEBUG [c.c.s.StatsCollector] > (StatsCollector-3:ctx-a4d2e607) StorageCollector is running... > 2014-01-01 20:03:35,497 INFO [c.c.a.m.AgentAttache] > (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Unable to send due to > Resource [Host:2] is unreachable: Host 2: Channel is closed > 2014-01-01 20:03:35,497 DEBUG [c.c.a.m.AgentAttache] > (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Cancelling. > 2014-01-01 20:03:35,498 DEBUG [o.a.c.s.RemoteHostEndPoint] > (StatsCollector-3:ctx-a4d2e607) Failed to send command, due to Agent:2, > com.cloud.exception.AgentUnavailableException: Resource [Host:2] is > unreachable: Host 2: Channel is closed > 2014-01-01 20:03:35,498 ERROR [c.c.s.StatsCollector] > (StatsCollector-3:ctx-a4d2e607) Error trying to retrieve storage stats > com.cloud.utils.exception.CloudRuntimeException: Failed to send command, due > to Agent:2, com.cloud.exception.AgentUnavailableException: Resource [Host:2] > is unreachable: Host 2: Channel is closed > at > org.apache.cloudstack.storage.RemoteHostEndPoint.sendMessage(RemoteHostEndPoint.java:116) > at > com.cloud.server.StatsCollector$StorageCollector.runInContext(StatsCollector.java:550) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > 2014-01-01 20:03:35,506 DEBUG [c.c.s.StatsCollector] > (StatsCollector-1:ctx-df84e56c) HostStatsCollector is running... > 2014-01-01 20:03:35,534 DEBUG [c.c.a.m.DirectAgentAttache] > (DirectAgent-374:ctx-c3b00e50) Seq 4-378077280: Executing request > 2014-01-01 20:03:35,638 ERROR [c.c.h.v.r.VmwareResource] > (DirectAgent-374:ctx-c3b00e50 10.147.40.28) Unable to execute > GetHostStatsCommand due to Exception: javax.xml.ws.soap.SOAPFaultException > Message: The session is not authenticated. > javax.xml.ws.soap.SOAPFaultException: The session is not authenticated. > at > com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at > com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) >
[jira] [Created] (CLOUDSTACK-5707) Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 5.1
manasaveloori created CLOUDSTACK-5707: - Summary: Hitting multiple exceptions when the Vsphere client is upgraded to 5.5 from 5.1 Key: CLOUDSTACK-5707 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5707 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Upgraded the CS 4.2.1 to 4.3 with ESXi5.1 using Vsphere client 5.1 Upgraded the Vsphere client to 5.5 Reporter: manasaveloori Priority: Critical Fix For: 4.3.0 Attachments: management-server.rar Steps followed: 1. Deployed CS 4.2.1 GA build with ESXi5.1(using Vsphere 5.1 client) 2. Deployed some VMs. 3. Upgraded the CS to 4.3. 4. Now unmanaged the cluster, kept the host in maintenance . 5. Upgraded the Vsphere client to 5.5 (http://www.vmadmin.co.uk/vmware/36-virtualcenter/284-vsphere4to5upgradevcenter41to5) 6. Manage the cluster and cancelled the maintenance mode on host. 7. Host is connected. Observing the following exceptions in Ms logs: 014-01-01 20:03:35,467 DEBUG [c.c.s.StatsCollector] (StatsCollector-3:ctx-a4d2e607) StorageCollector is running... 2014-01-01 20:03:35,497 INFO [c.c.a.m.AgentAttache] (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Unable to send due to Resource [Host:2] is unreachable: Host 2: Channel is closed 2014-01-01 20:03:35,497 DEBUG [c.c.a.m.AgentAttache] (StatsCollector-3:ctx-a4d2e607) Seq 2-1062210638: Cancelling. 2014-01-01 20:03:35,498 DEBUG [o.a.c.s.RemoteHostEndPoint] (StatsCollector-3:ctx-a4d2e607) Failed to send command, due to Agent:2, com.cloud.exception.AgentUnavailableException: Resource [Host:2] is unreachable: Host 2: Channel is closed 2014-01-01 20:03:35,498 ERROR [c.c.s.StatsCollector] (StatsCollector-3:ctx-a4d2e607) Error trying to retrieve storage stats com.cloud.utils.exception.CloudRuntimeException: Failed to send command, due to Agent:2, com.cloud.exception.AgentUnavailableException: Resource [Host:2] is unreachable: Host 2: Channel is closed at org.apache.cloudstack.storage.RemoteHostEndPoint.sendMessage(RemoteHostEndPoint.java:116) at com.cloud.server.StatsCollector$StorageCollector.runInContext(StatsCollector.java:550) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-01-01 20:03:35,506 DEBUG [c.c.s.StatsCollector] (StatsCollector-1:ctx-df84e56c) HostStatsCollector is running... 2014-01-01 20:03:35,534 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-374:ctx-c3b00e50) Seq 4-378077280: Executing request 2014-01-01 20:03:35,638 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-374:ctx-c3b00e50 10.147.40.28) Unable to execute GetHostStatsCommand due to Exception: javax.xml.ws.soap.SOAPFaultException Message: The session is not authenticated. javax.xml.ws.soap.SOAPFaultException: The session is not authenticated. at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:129) at $Proxy388.queryHostConnectionInfo(Unknown Source) at com.cloud.hypervisor.vmware.mo.HostMO.getHostHardwareSummary(HostMO.java:87) at com.cloud.hypervisor.vmware.mo.HostMO.getHyperHo
[jira] [Commented] (CLOUDSTACK-5703) [Hyper-V] Put the hard coded rdp server port value in host details
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859852#comment-13859852 ] ASF subversion and git services commented on CLOUDSTACK-5703: - Commit e74889ac91c919ab26852da3d93133eaeae874c8 in branch refs/heads/4.3 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e74889a ] CLOUDSTACK-5703: putting rdp server port value in host details > [Hyper-V] Put the hard coded rdp server port value in host details > -- > > Key: CLOUDSTACK-5703 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5703 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5702) [Hyper-V] Mouse doesn't work for Console
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859851#comment-13859851 ] ASF subversion and git services commented on CLOUDSTACK-5702: - Commit a4d4d4b09aaff5b5606d1f9f58b2b80c92aee0a9 in branch refs/heads/4.3 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a4d4d4b ] CLOUDSTACK-5702: Fixed mouse doesn't work for console > [Hyper-V] Mouse doesn't work for Console > > > Key: CLOUDSTACK-5702 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5702 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > > mouse keys are not working for console on hyperv -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5702) [Hyper-V] Mouse doesn't work for Console
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar resolved CLOUDSTACK-5702. Resolution: Fixed merged to 4.3 > [Hyper-V] Mouse doesn't work for Console > > > Key: CLOUDSTACK-5702 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5702 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > > mouse keys are not working for console on hyperv -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5703) [Hyper-V] Put the hard coded rdp server port value in host details
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar resolved CLOUDSTACK-5703. Resolution: Fixed merged to 4.3 > [Hyper-V] Put the hard coded rdp server port value in host details > -- > > Key: CLOUDSTACK-5703 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5703 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5705) [Hyper-V] Thumbnail for console of hyperv is not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar resolved CLOUDSTACK-5705. Resolution: Fixed merged to 4.3 > [Hyper-V] Thumbnail for console of hyperv is not working > > > Key: CLOUDSTACK-5705 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5705 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Thumbnail for console of hyperv is not working -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5708) Fix router template version to 4.3
Sowmya Krishnan created CLOUDSTACK-5708: --- Summary: Fix router template version to 4.3 Key: CLOUDSTACK-5708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5708 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template, Virtual Router Affects Versions: 4.3.0 Environment: Any hypervisor Reporter: Sowmya Krishnan Fix For: 4.3.0 Deploy latest 4.3 Create a network Start up router Verify router version using listrouters or UI: Infrastructure -> Virtual Routers -> Click on a router -> Version Shows 4.2 instead of 4.3 Following is from a hyper-v setup for which we had new template. Version needs to be fixed for other hypervisor templates as well. DB: id: 55 element_id: 1 public_mac_address: 06:10:40:00:00:18 public_ip_address: 10.102.196.212 public_netmask: 255.255.255.0 guest_netmask: NULL guest_ip_address: NULL is_redundant_router: 0 priority: 0 is_priority_bumpup: 0 redundant_state: UNKNOWN stop_pending: 0 role: VIRTUAL_ROUTER template_version: Cloudstack Release 4.2.0 Wed Dec 4 11:08:17 UTC 2013 scripts_version: 0f19d23eebd2679921f1d5a252a6f7c0 vpc_id: NULL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5463) Hyper-V does not report stopped VMs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859857#comment-13859857
]
Devdeep Singh commented on CLOUDSTACK-5463:
---
Checked against vmware setup. I see the same behavior. On stopping an instance
from vcenter, the status of the vm isn't updated in cloudstack.
> Hyper-V does not report stopped VMs
> ---
>
> Key: CLOUDSTACK-5463
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5463
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.3.0
>Reporter: Donal Lafferty
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: Hyper-V
>
> The Hyper-V agent is never asked whether a VM is running. E.g. it is only
> asked the VmStats:
> 2013-12-11 06:28:08,544 [32] INFO HypervResource.HypervResourceController
> [7bbebc6a-400a-4d9f-832a-06924b823ba4] -
> com.cloud.agent.api.GetVmStatsCommand{
> "vmNames": [
> "i-2-3-VM"
> ],
> "hostGuid": "700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource",
> "hostName": "10.70.176.29",
> "contextMap": {},
> "wait": 0
> }
> 2013-12-11 06:28:08,716 [32] DEBUG HypervResource.WmiCallsV2
> [7bbebc6a-400a-4d9f-832a-06924b823ba4] - VM
> 20E0665F-4EE0-42A5-AC94-03DC9D3B5E8C(elementName i-2-3-VM) has 1 CPUs, and
> load of 0
> 2013-12-11 06:28:08,717 [32] INFO HypervResource.HypervResourceController
> [7bbebc6a-400a-4d9f-832a-06924b823ba4] - {
> "com.cloud.agent.api.GetVmStatsAnswer": {
> "vmStatsMap": {
> "i-2-3-VM": {
> "cpuUtilization": 0.0,
> "networkReadKBs": 1.0,
> "networkWriteKBs": 1.0,
> "numCPUs": 1,
> "entityType": "vm"
> }
> },
> "result": true,
> "contextMap": {}
> }
> }
> Therefore, if the VM shut itself down, the management server thinks it is
> still running.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5314) [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in the resource count table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5314: - Assignee: Devdeep Singh (was: Sanjay Tripathi) > [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in > the resource count table > - > > Key: CLOUDSTACK-5314 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5314 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Description : > > The resource count value for primary storage and volumes in the > cloud.resource_count table is shown as negative (-ve) > mysql> select * from resource_count; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 1 | NULL | 1 | cpu | 6 | > | 2 | NULL | 1 | memory| 3072 | > | 3 | NULL | 1 | primary_storage | -103079215104 | > | 4 | NULL | 1 | secondary_storage | 56863775232 | > | 9 | NULL | 1 | user_vm | 6 | > | 10 | NULL | 1 | public_ip | 2 | > | 11 | NULL | 1 | volume|-5 | > | 12 | NULL | 1 | snapshot | 0 | > | 13 | NULL | 1 | template | 4 | > | 14 | NULL | 1 | project | 0 | > | 15 | NULL | 1 | network | 1 | > | 16 | NULL | 1 | vpc | 0 | > | 17 | 1 | NULL | user_vm | 0 | > | 18 | 1 | NULL | public_ip | 0 | > | 19 | 1 | NULL | volume| 0 | > | 20 | 1 | NULL | snapshot | 0 | > | 21 | 1 | NULL | template | 0 | > | 22 | 1 | NULL | project | 0 | > | 23 | 1 | NULL | network | 0 | > | 24 | 1 | NULL | vpc | 0 | > | 25 | 1 | NULL | cpu | 0 | > | 26 | 1 | NULL | memory| 0 | > | 27 | 1 | NULL | primary_storage | 0 | > | 28 | 1 | NULL | secondary_storage | 0 | > | 29 | 2 | NULL | user_vm | 6 | > | 30 | 2 | NULL | public_ip | 2 | > | 31 | 2 | NULL | volume|-5 | > | 32 | 2 | NULL | snapshot | 0 | > | 33 | 2 | NULL | template | 4 | > | 34 | 2 | NULL | project | 0 | > | 35 | 2 | NULL | network | 1 | > | 36 | 2 | NULL | vpc | 0 | > | 37 | 2 | NULL | cpu | 6 | > | 38 | 2 | NULL | memory| 3072 | > | 39 | 2 | NULL | primary_storage | -103079215104 | > | 40 | 2 | NULL | secondary_storage | 163220937216 | > +++---+---+---+ > 36 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5314) [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in the resource count table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5314. --- Resolution: Cannot Reproduce Checked against latest build. Tried various operations (vm depoloy, attach, detach volume, etc). I couldn't reproduce the issue, Marking the bug as not reproducible. Kindly reopen the issue if you still see the problem and a set of steps reproduces the issue. > [Hyper-V] Negative (-ve) values for primary storage and volumes are shown in > the resource count table > - > > Key: CLOUDSTACK-5314 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5314 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Management Server >Affects Versions: 4.3.0 > Environment: Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > Description : > > The resource count value for primary storage and volumes in the > cloud.resource_count table is shown as negative (-ve) > mysql> select * from resource_count; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 1 | NULL | 1 | cpu | 6 | > | 2 | NULL | 1 | memory| 3072 | > | 3 | NULL | 1 | primary_storage | -103079215104 | > | 4 | NULL | 1 | secondary_storage | 56863775232 | > | 9 | NULL | 1 | user_vm | 6 | > | 10 | NULL | 1 | public_ip | 2 | > | 11 | NULL | 1 | volume|-5 | > | 12 | NULL | 1 | snapshot | 0 | > | 13 | NULL | 1 | template | 4 | > | 14 | NULL | 1 | project | 0 | > | 15 | NULL | 1 | network | 1 | > | 16 | NULL | 1 | vpc | 0 | > | 17 | 1 | NULL | user_vm | 0 | > | 18 | 1 | NULL | public_ip | 0 | > | 19 | 1 | NULL | volume| 0 | > | 20 | 1 | NULL | snapshot | 0 | > | 21 | 1 | NULL | template | 0 | > | 22 | 1 | NULL | project | 0 | > | 23 | 1 | NULL | network | 0 | > | 24 | 1 | NULL | vpc | 0 | > | 25 | 1 | NULL | cpu | 0 | > | 26 | 1 | NULL | memory| 0 | > | 27 | 1 | NULL | primary_storage | 0 | > | 28 | 1 | NULL | secondary_storage | 0 | > | 29 | 2 | NULL | user_vm | 6 | > | 30 | 2 | NULL | public_ip | 2 | > | 31 | 2 | NULL | volume|-5 | > | 32 | 2 | NULL | snapshot | 0 | > | 33 | 2 | NULL | template | 4 | > | 34 | 2 | NULL | project | 0 | > | 35 | 2 | NULL | network | 1 | > | 36 | 2 | NULL | vpc | 0 | > | 37 | 2 | NULL | cpu | 6 | > | 38 | 2 | NULL | memory| 3072 | > | 39 | 2 | NULL | primary_storage | -103079215104 | > | 40 | 2 | NULL | secondary_storage | 163220937216 | > +++---+---+---+ > 36 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5690) [Upgrade from 4.2.1->4.3]System VMs and Router VMs are not upgraded to new 64bit templates .
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859861#comment-13859861
]
manasaveloori commented on CLOUDSTACK-5690:
---
observed this for 4.2 to 4.3 upgrade as well.
> [Upgrade from 4.2.1->4.3]System VMs and Router VMs are not upgraded to new
> 64bit templates .
>
>
> Key: CLOUDSTACK-5690
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5690
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade
>Affects Versions: 4.3.0
> Environment: upgrade from 4.2.1 to 4.3
>Reporter: manasaveloori
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: mysqldump421.dmp, mysqldump43.dmp
>
>
> Steps:
> 1.Deploy CS 4.2.1 .Use 32 bit templates.
> 2.Deploy some VRs.
> 3.Register 64bit templates.
> 4.Upgrade to 4.3.
> 5.Now stop and start(or destroy) the system VMs so that they get upgraded
> to new 64 bit templates.
> Observation:
> The system VMs are not upgraded to new 64 bit template:
> mysql> select * from volumes where instance_id=5\G;before destroying
> *** 1. row ***
> id: 7
> account_id: 1
> domain_id: 1
>pool_id: 2
> last_pool_id: NULL
>instance_id: 5
> device_id: 0
> name: ROOT-5
> uuid: 6f324474-5fa5-44cb-8950-d0aced23f334
> size: 0
> folder: NULL
> path: ROOT-5
> pod_id: NULL
> data_center_id: 2
> iscsi_name: NULL
>host_ip: NULL
>volume_type: ROOT
> pool_type: NULL
> disk_offering_id: 9
>template_id: 8
> first_snapshot_backup_uuid: NULL
>recreatable: 1
>created: 2013-12-30 17:22:48
> attached: NULL
>updated: 2013-12-31 13:24:33
>removed: 2013-12-31 13:24:33
> state: Expunged
> chain_info:
> {"diskDeviceBusName":"scsi0:0","diskChain":["[f672eae0b4003767808fb787a5c04d5f]
> s-5-VM/ROOT-5.vmdk"]}
> update_count: 6
> disk_type: NULL
> vm_snapshot_chain_size: NULL
> iso_id: NULL
> display_volume: 1
> format: OVA
> min_iops: NULL
> max_iops: NULL
> hv_ss_reserve: NULL
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
> mysql> select * from volumes where instance_id=14\G;--after destroying.
> *** 1. row ***
> id: 17
> account_id: 1
> domain_id: 1
>pool_id: 2
> last_pool_id: NULL
>instance_id: 14
> device_id: 0
> name: ROOT-14
> uuid: d4e8a55a-0cdc-4bbb-bfba-a18f16e29ff9
> size: 2097152000
> folder: NULL
> path: ROOT-14
> pod_id: NULL
> data_center_id: 2
> iscsi_name: NULL
>host_ip: NULL
>volume_type: ROOT
> pool_type: NULL
> disk_offering_id: 9
>template_id: 8
> first_snapshot_backup_uuid: NULL
>recreatable: 1
>created: 2013-12-31 13:24:33
> attached: NULL
>updated: 2013-12-31 13:26:13
>removed: NULL
> state: Ready
> chain_info:
> {"diskDeviceBusName":"ide0:1","diskChain":["[f672eae0b4003767808fb787a5c04d5f]
> s-14-VM/ROOT-14.vmdk"]}
> update_count: 2
> disk_type: NULL
> vm_snapshot_chain_size: NULL
> iso_id: NULL
> display_volume: 1
> format: OVA
> min_iops: NULL
> max_iops: NULL
> hv_ss_reserve: NULL
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
> Note:
> For Router VMs the field requires upgrade is set to “ No”. So there is no
> option to upgrade the VR to new 64 bit template.
> Even after stop and start of the VR the template is not upgraded to 64 bit.
> Attaching the mysql dumps.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5472) UI shows incorrect vm statistics if vm deployed with dynamic compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859864#comment-13859864
]
prashant kumar mishra commented on CLOUDSTACK-5472:
---
saw similar issue with scaleVMCmd response:Resolving above should solve the
problem
Logs:
--
[root@localhost ~]# cat /var/log/cloudstack/management/management-server.log
|grep job-33
2014-01-01 11:30:33,835 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-5:ctx-e421bde7 ctx-d73af7e9) submit async job-33, details:
AsyncJobVO {id:33, userId: 2, accountId: 2, instanceType: None, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.vm.ScaleVMCmd, cmdInfo:
{"serviceofferingid":"044b7a15-f9aa-42d2-a1ee-3821f82ba1e9","sessionkey":"oD9mZUVskgfKaloWHlv3GoUdbfU\u003d","cmdEventType":"VM.UPGRADE","ctxUserId":"2","customparameters[0].memory":"1024","httpmethod":"GET","id":"3701ab49-a39a-464d-8cee-89fd4f6e68f5","response":"json","customparameters[0].cpuSpeed":"200","customparameters[0].cpuNumber":"1","_":"1388574469923","ctxAccountId":"2","ctxStartEventId":"97"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 7484181839895, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-01-01 11:30:33,839 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-22:ctx-3f997354) Add job-33 into job monitoring
2014-01-01 11:30:34,289 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-22:ctx-3f997354 ctx-d73af7e9) Complete async job-33, jobStatus:
SUCCEEDED, resultCode: 0, result:
org.apache.cloudstack.api.response.UserVmResponse/virtualmachine/{"id":"3701ab49-a39a-464d-8cee-89fd4f6e68f5","name":"one","displayname":"one","account":"admin","domainid":"4d65da54-7226-11e3-8e5c-06ce8c17","domain":"ROOT","created":"2013-12-31T10:35:34-0500","state":"Stopped","haenable":false,"zoneid":"2ae47aea-0db4-4a84-b088-63004d2eb4be","zonename":"z1","templateid":"4d711ff4-7226-11e3-8e5c-06ce8c17","templatename":"CentOS
5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no
GUI
(XenServer)","passwordenabled":false,"serviceofferingid":"044b7a15-f9aa-42d2-a1ee-3821f82ba1e9","serviceofferingname":"dnm","cpunumber":0,"cpuspeed":0,"memory":0,"cpuused":"0%","networkkbsread":61,"networkkbswrite":0,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"4d846b90-7226-11e3-8e5c-06ce8c17","rootdeviceid":0,"rootdevicetype":"ROOT","securitygroup":[{"id":"9360e580-7226-11e3-8e5c-06ce8c17","name":"default","description":"Default
Security
Group","account":"admin","ingressrule":[],"egressrule":[],"tags":[]}],"nic":[{"id":"f01af7be-47ad-4e8a-bfac-1b4bc2bc1049","networkid":"cdd0106d-c5ba-4d24-8fa2-0e4046ef4a02","networkname":"defaultGuestNetwork","netmask":"255.255.254.0","gateway":"10.147.40.1","ipaddress":"10.147.41.222","isolationuri":"ec2://untagged","broadcasturi":"vlan://untagged","traffictype":"Guest","type":"Shared","isdefault":true,"macaddress":"06:b1:80:00:00:0d"}],"hypervisor":"XenServer","instancename":"i-2-3-VM","tags":[],"affinitygroup":[],"displayvm":true,"isdynamicallyscalable":true}
2014-01-01 11:30:34,309 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-22:ctx-3f997354) Done executing
org.apache.cloudstack.api.command.user.vm.ScaleVMCmd for job-33
2014-01-01 11:30:34,316 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-22:ctx-3f997354) Remove job-33 from job monitoring
> UI shows incorrect vm statistics if vm deployed with dynamic compute offering
> --
>
> Key: CLOUDSTACK-5472
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5472
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Reporter: prashant kumar mishra
>Assignee: Bharat Kumar
> Attachments: Logs_db.rar, screenshot-1.jpg
>
>
> Steps to repro
>
> 1-prepare CS setup with xen6.2
> 2-create a dynamic SO d1
> 3-deploy a vm with d1
> 4-check vm statistics in UI
> Actual
>
> vm statistics shows Total cpu=0
> My observation
>
> API response shows cpunumber":0,"cpuspeed":0,"memory":0,"cpuused":"0% which
> is incorrect.
> Details
> ==
> API
> -
> http://10.147.38.177:8080/client/api?command=listVirtualMachines&details=stats&id=352a9b66-4539-4117-9cea-ca9dd5da00fa&response=json&sessionkey=51sujrtdCbNbXHU3LotE2wx6UMk%3D&_=1386828570170
> API Response
> -
> { "listvirtualmachinesresponse" : { "count":1 ,"virtualmachine" : [
> {"id":"352a9b66-4539-4117-9cea-ca9dd5da00fa","name":"last","displayname":"last","account":"admin","domainid":"45b3c110-6261-11e3-87cf-0654483b","doma
[jira] [Commented] (CLOUDSTACK-5698) [UI] search not working in "Router - Network ACL lists panel"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859867#comment-13859867 ] ASF subversion and git services commented on CLOUDSTACK-5698: - Commit 78b9d5cda208f052d522c740871873ecd366cf2a in branch refs/heads/4.3 from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=78b9d5c ] CLOUDSTACK-5698: support network ACL list search by keyword > [UI] search not working in "Router - Network ACL lists panel" > - > > Key: CLOUDSTACK-5698 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5698 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.3.0 >Reporter: Rayees Namathponnan >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.3.0 > > Attachments: CLOUDSTACK-5698.png, dbdump.rar > > > Steps to reproduce > 1) Create VPC > 2) Add few Network ACL list > 3) Select Network ACL list and search with some junk characters "" > Expected result > Nothing should be displayed in search > Actual result > Search is not working here -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5698) [UI] search not working in "Router - Network ACL lists panel"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859869#comment-13859869 ] ASF subversion and git services commented on CLOUDSTACK-5698: - Commit 79dc74dcb85adfbc0b5b72925263b383e6155cda in branch refs/heads/master from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=79dc74d ] CLOUDSTACK-5698: support network ACL list search by keyword Conflicts: server/src/com/cloud/network/vpc/NetworkACLServiceImpl.java > [UI] search not working in "Router - Network ACL lists panel" > - > > Key: CLOUDSTACK-5698 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5698 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.3.0 >Reporter: Rayees Namathponnan >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.3.0 > > Attachments: CLOUDSTACK-5698.png, dbdump.rar > > > Steps to reproduce > 1) Create VPC > 2) Add few Network ACL list > 3) Select Network ACL list and search with some junk characters "" > Expected result > Nothing should be displayed in search > Actual result > Search is not working here -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5698) [UI] search not working in "Router - Network ACL lists panel"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-5698. --- Resolution: Fixed > [UI] search not working in "Router - Network ACL lists panel" > - > > Key: CLOUDSTACK-5698 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5698 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.3.0 >Reporter: Rayees Namathponnan >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.3.0 > > Attachments: CLOUDSTACK-5698.png, dbdump.rar > > > Steps to reproduce > 1) Create VPC > 2) Add few Network ACL list > 3) Select Network ACL list and search with some junk characters "" > Expected result > Nothing should be displayed in search > Actual result > Search is not working here -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
Nux created CLOUDSTACK-5709: --- Summary: Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary & secondary storage Reporter: Nux Snapshots fail and get stuck in "Created on primary". Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-4308) [Snapshot][KVM] UI - KVM.snapshot.enabled=FALSE UI should not allow setup recurring snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4308. > [Snapshot][KVM] UI - KVM.snapshot.enabled=FALSE UI should not allow setup > recurring snapshot > - > > Key: CLOUDSTACK-4308 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4308 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 > Environment: 4.2 MS, hypervisor: KVM, >Reporter: Fang Wang >Assignee: Jessica Wang > Fix For: 4.2.0 > > > KVM: the default snapshot setting for 4.2 MS has a global flag: > kvm.snapshot.enabled > default value is set to FALSE. > With this default setting, we should disable the recurring snapshot from UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5709: - Fix Version/s: 4.2.1 > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859981#comment-13859981 ] Sudha Ponnaganti commented on CLOUDSTACK-5709: -- CentOS 6.5 is nor supported yet right?? Also need to review edison's comments from below mail thread to understand the actual issue. > -Original Message- > From: Nux! [mailto:n...@li.nux.ro] > Sent: Monday, December 23, 2013 6:35 AM > To: d...@cloudstack.apache.org > Subject: Re: [VOTE] 3rd round of voting for ASF 4.2.1 RC > > On 23.12.2013 05:42, Abhinandan Prateek wrote: > > It gives me immense pleasure to inform that the vote to label this > > ASF > > 4.2.1 RC as the GA release has been passed with following stats: > > Can someone check KVM volume snapshots before declaring this GA? It's > been consistently broken for me in 4.2.1-SNAPSHOT with NFS as well as > GlusterFS shared mount point. > It was working in 4.2.0 afaicr. In the ACS release(since 4.0), KVM snapshot only works when CLVM is used as primary storage, otherwise, taking snapshot in KVM will fail, as there is no formal way to backup snapshot from primary storage to secondary storage. > > I've sent several emails about this as well as bothering people in > CLOUDSTACK-5393. > http://www.mail-archive.com/dev@cloudstack.apache.org/msg20123.html > > HTH > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > Snapshots fail on ACS 4.2.1 SNAPSHOT > > > Key: CLOUDSTACK-5709 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Snapshot >Affects Versions: 4.2.1 > Environment: CentOS 6.5 HV, NFS primary & secondary storage >Reporter: Nux > Labels: fail, kvm, snapshot > Fix For: 4.2.1 > > > Snapshots fail and get stuck in "Created on primary". > Logs with Basic Zone install (after the runbook): > http://tmp.nux.ro/t9P-snapfail.txt > Logs with the same problem but with Adv zone and Shared Mount Point > (glusterfs) as primary storage: > http://tmp.nux.ro/T94-ACSgluster.txt > AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5498) [Atomation] Marvin - Logs are not storing to folder with suite name
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5498:
Priority: Critical (was: Major)
> [Atomation] Marvin - Logs are not storing to folder with suite name
> ---
>
> Key: CLOUDSTACK-5498
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5498
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, marvin
>Affects Versions: 4.3.0
> Environment: Automation
>Reporter: Rayees Namathponnan
>Assignee: Santhosh Kumar Edukulla
>Priority: Critical
> Fix For: 4.3.0
>
>
> Configure .cfg file with below data and run automation eg "test_ssvm"
> },
> "logger":
> {
> "LogFolderPath": "/Repo_30X/ipcl/cloudstack/test/logs/"
> },
> "globalConfig": [
> {
> "name": "network.gc.wait",
> "value": "60"
> },
> {
> "
> Expected result
> Folder "test_ssvm_+timestamp" should be created under
> /Repo_30X/ipcl/cloudstack/test/logs/", and below 3 files should be under
> that
> failed_plus_exceptions.txt
> results.txt
> runinfo.txt
> Actual Result
> Folder "timestamp" created instead of "test_ssvm_+timestamp", and i can see
> other 3 text files;
> Its very hard to find corresponding folder for test_ssvm, with current
> implementation
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5498) [Atomation] Marvin - Logs are not storing to folder with suite name
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5498:
Assignee: Santhosh Kumar Edukulla
> [Atomation] Marvin - Logs are not storing to folder with suite name
> ---
>
> Key: CLOUDSTACK-5498
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5498
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, marvin
>Affects Versions: 4.3.0
> Environment: Automation
>Reporter: Rayees Namathponnan
>Assignee: Santhosh Kumar Edukulla
> Fix For: 4.3.0
>
>
> Configure .cfg file with below data and run automation eg "test_ssvm"
> },
> "logger":
> {
> "LogFolderPath": "/Repo_30X/ipcl/cloudstack/test/logs/"
> },
> "globalConfig": [
> {
> "name": "network.gc.wait",
> "value": "60"
> },
> {
> "
> Expected result
> Folder "test_ssvm_+timestamp" should be created under
> /Repo_30X/ipcl/cloudstack/test/logs/", and below 3 files should be under
> that
> failed_plus_exceptions.txt
> results.txt
> runinfo.txt
> Actual Result
> Folder "timestamp" created instead of "test_ssvm_+timestamp", and i can see
> other 3 text files;
> Its very hard to find corresponding folder for test_ssvm, with current
> implementation
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5710) [Automation] VM migration failed in kvm with NPE
Rayees Namathponnan created CLOUDSTACK-5710:
---
Summary: [Automation] VM migration failed in kvm with NPE
Key: CLOUDSTACK-5710
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5710
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.3.0
Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.3.0
Steps to reproduce
Step 1 : Create advanced zone with KVM
Step 2 : Add to hosts
Step 3 : Deploy VM in host 1
Step 4 : Migrate vm from host 1 to host 2
migration failed with below NPE
2014-01-01 21:37:03,602 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-625534e2) Schedule queued job-4429
2014-01-01 21:37:03,648 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-61:ctx-44c473db) Add job-4429 into job monitoring
2014-01-01 21:37:03,649 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-61:ctx-44c473db) Executing AsyncJobVO {id:4429, userId: 2,
accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIDU3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwACcQB-AAlwcQB-AAk,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Wed Jan 01 21:37:02 PST 2014}
2014-01-01 21:37:03,649 DEBUG [c.c.v.VmWorkJobDispatcher]
(Job-Executor-61:ctx-44c473db) Run VM work job: com.cloud.vm.VmWorkMigrate
2014-01-01 21:37:03,665 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Job-Executor-61:ctx-44c473db ctx-f08806b2) Execute VM work job:
com.cloud.vm.VmWorkMigrate{"zoneId":1,"podId":1,"clusterId":1,"hostId":2,"srcHostId":1,"userId":2,"accountId":2,"vmId":851,"handlerName":"VirtualMachineManagerImpl"}
2014-01-01 21:37:03,666 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Job-Executor-61:ctx-44c473db ctx-f08806b2) Invocation exception, caused by:
java.lang.NullPointerException
2014-01-01 21:37:03,667 ERROR [c.c.v.VmWorkJobDispatcher]
(Job-Executor-61:ctx-44c473db ctx-f08806b2) Unable to complete AsyncJobVO
{id:4429, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIDU3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwACcQB-AAlwcQB-AAk,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Wed Jan 01 21:37:02 PST 2014}
java.lang.NullPointerException
at
com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrate(VirtualMachineManagerImpl.java:4758)
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.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4855)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.c
[jira] [Updated] (CLOUDSTACK-5711) allow scaling from the same offering when using custom compute offering.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5711: - Priority: Critical (was: Major) > allow scaling from the same offering when using custom compute offering. > > > Key: CLOUDSTACK-5711 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5711 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Bharat Kumar >Assignee: Bharat Kumar >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5711) allow scaling from the same offering when using custom compute offering.
Bharat Kumar created CLOUDSTACK-5711: Summary: allow scaling from the same offering when using custom compute offering. Key: CLOUDSTACK-5711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5711 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Reporter: Bharat Kumar Assignee: Bharat Kumar -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5710) [Automation] VM migration failed in kvm with NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5710:
Attachment: management-server.rar
> [Automation] VM migration failed in kvm with NPE
>
>
> Key: CLOUDSTACK-5710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: KVM RHEL 6.3
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar
>
>
> Steps to reproduce
> Step 1 : Create advanced zone with KVM
> Step 2 : Add to hosts
> Step 3 : Deploy VM in host 1
> Step 4 : Migrate vm from host 1 to host 2
> migration failed with below NPE
> 2014-01-01 21:37:03,602 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-625534e2) Schedule queued job-4429
> 2014-01-01 21:37:03,648 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-61:ctx-44c473db) Add job-4429 into job monitoring
> 2014-01-01 21:37:03,649 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-61:ctx-44c473db) Executing AsyncJobVO {id:4429, userId: 2,
> accountId: 2, instanceType: null, instanceId: null, cmd:
> com.cloud.vm.VmWorkMigrate, cmdInfo:
> rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIDU3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwACcQB-AAlwcQB-AAk,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Wed Jan 01 21:37:02 PST 2014}
> 2014-01-01 21:37:03,649 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Job-Executor-61:ctx-44c473db) Run VM work job: com.cloud.vm.VmWorkMigrate
> 2014-01-01 21:37:03,665 DEBUG [c.c.v.VmWorkJobHandlerProxy]
> (Job-Executor-61:ctx-44c473db ctx-f08806b2) Execute VM work job:
> com.cloud.vm.VmWorkMigrate{"zoneId":1,"podId":1,"clusterId":1,"hostId":2,"srcHostId":1,"userId":2,"accountId":2,"vmId":851,"handlerName":"VirtualMachineManagerImpl"}
> 2014-01-01 21:37:03,666 ERROR [c.c.v.VmWorkJobHandlerProxy]
> (Job-Executor-61:ctx-44c473db ctx-f08806b2) Invocation exception, caused by:
> java.lang.NullPointerException
> 2014-01-01 21:37:03,667 ERROR [c.c.v.VmWorkJobDispatcher]
> (Job-Executor-61:ctx-44c473db ctx-f08806b2) Unable to complete AsyncJobVO
> {id:4429, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
> com.cloud.vm.VmWorkMigrate, cmdInfo:
> rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIDU3QAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAXNxAH4ABwACcQB-AAlwcQB-AAk,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Wed Jan 01 21:37:02 PST 2014}
> java.lang.NullPointerException
> at
> com.cloud.vm.VmWorkMigrate.getDeployDestination(VmWorkMigrate.java:60)
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrate(VirtualMachineManagerImpl.java:4758)
> 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.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4855)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
>
[jira] [Resolved] (CLOUDSTACK-5196) SSH to VM fails when done through public ip associated through NAT Rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-5196. -- Resolution: Cannot Reproduce I am able to successfully acquire a portable IP and create 1:1 NAT, and able to access the VM through SSH. Please ensure that VLAN specified for portable IP range is a valid (trunked on hypervisor) VLAN. > SSH to VM fails when done through public ip associated through NAT Rule > --- > > Key: CLOUDSTACK-5196 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5196 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 >Reporter: Ashutosk Kelkar >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.3.0 > > > Deploy a VM > Acquire a portable IP in the network of VM and open the firewall and create > NAT rule associating the portable ip with the VM. > Try to SSH to the VM through portable ip. > SSH fails. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5672) [Automation]Failed to add new nic to vm; error "Unable to serialize" observed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860032#comment-13860032
]
Saksham Srivastava commented on CLOUDSTACK-5672:
The issue is not only in KVM. I am able to reproduce the issue on XenServer
also.
The issue is not restricted to addNic it also shows up in removeNic.
Root Cause : Regression caused due to a recent commit by Kelven:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=dc303fda
I tested the scenario on
1. the code with this commit and
2. on the code just before this commit
The issue is seen always in #1 and never in #2
Assigning it to Kelven.
> [Automation]Failed to add new nic to vm; error "Unable to serialize"
> observed
> ---
>
> Key: CLOUDSTACK-5672
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5672
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Controller
>Affects Versions: 4.3.0
> Environment: KVM
> branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Saksham Srivastava
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Create advanced zone
> Step 2 : Depoy and vm VM-QA1
> Step 3 : Create new network
> Step 4 : Add new nic to VM-QA1
> Result
> Failed to add new nic to the vm, below error observed
> nstanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd, cmdInfo:
> {"response":"json","sessionkey":"ZZ4QXAUZwIPe83MSDipOFbHVpwo\u003d","virtualmachineid":"751ac91a-9a63-4d75-9700-70e269b539a4","cmdEventType":"NIC.CREATE","ctxUserId":"2","httpmethod":"GET","_":"1388332341748","ctxAccountId":"2","networkid":"ac35a773-08d1-4f55-9a57-bf0b78111698","ctxStartEventId":"16101"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-29 07:49:06,291 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-29:ctx-f5b59752 ctx-fbfc6d7f) Rolling back the transaction:
> Time = 91 Name = Job-Executor-29; called by
> -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4525-VirtualMachineManagerImpl.addVmToNetwork:3112-UserVmManagerImpl.addNicToVirtualMachine:1038-GeneratedMethodAccessor813.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616-AopUtils.invokeJoinpointUsingReflection:317
> 2013-12-29 07:49:06,324 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-29:ctx-f5b59752) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@57ca10b0
> at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
> at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
> at
> com.cloud.vm.VirtualMachineManagerImpl$10.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4554)
> at
> com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
> at
> com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.vm.VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue(VirtualMachineManagerImpl.java:4525)
> at
> com.cloud.vm.VirtualMachineManagerImpl.addVmToNetwork(VirtualMachineManagerImpl.java:3112)
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:1038)
> at sun.reflect.GeneratedMethodAccessor813.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.
[jira] [Updated] (CLOUDSTACK-5672) [Automation]Failed to add new nic to vm; error "Unable to serialize" observed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava updated CLOUDSTACK-5672:
---
Environment: branch 4.3 (was: KVM
branch 4.3)
> [Automation]Failed to add new nic to vm; error "Unable to serialize"
> observed
> ---
>
> Key: CLOUDSTACK-5672
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5672
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Controller
>Affects Versions: 4.3.0
> Environment: branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Kelven Yang
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Create advanced zone
> Step 2 : Depoy and vm VM-QA1
> Step 3 : Create new network
> Step 4 : Add new nic to VM-QA1
> Result
> Failed to add new nic to the vm, below error observed
> nstanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd, cmdInfo:
> {"response":"json","sessionkey":"ZZ4QXAUZwIPe83MSDipOFbHVpwo\u003d","virtualmachineid":"751ac91a-9a63-4d75-9700-70e269b539a4","cmdEventType":"NIC.CREATE","ctxUserId":"2","httpmethod":"GET","_":"1388332341748","ctxAccountId":"2","networkid":"ac35a773-08d1-4f55-9a57-bf0b78111698","ctxStartEventId":"16101"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-29 07:49:06,291 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-29:ctx-f5b59752 ctx-fbfc6d7f) Rolling back the transaction:
> Time = 91 Name = Job-Executor-29; called by
> -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4525-VirtualMachineManagerImpl.addVmToNetwork:3112-UserVmManagerImpl.addNicToVirtualMachine:1038-GeneratedMethodAccessor813.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616-AopUtils.invokeJoinpointUsingReflection:317
> 2013-12-29 07:49:06,324 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-29:ctx-f5b59752) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@57ca10b0
> at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
> at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
> at
> com.cloud.vm.VirtualMachineManagerImpl$10.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4554)
> at
> com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
> at
> com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.vm.VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue(VirtualMachineManagerImpl.java:4525)
> at
> com.cloud.vm.VirtualMachineManagerImpl.addVmToNetwork(VirtualMachineManagerImpl.java:3112)
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:1038)
> at sun.reflect.GeneratedMethodAccessor813.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy169.addNicToVirtualMachine(Unknown Source)
> at
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:110)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAs
[jira] [Assigned] (CLOUDSTACK-5672) [Automation]Failed to add new nic to vm; error "Unable to serialize" observed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava reassigned CLOUDSTACK-5672:
--
Assignee: Kelven Yang (was: Saksham Srivastava)
> [Automation]Failed to add new nic to vm; error "Unable to serialize"
> observed
> ---
>
> Key: CLOUDSTACK-5672
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5672
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Controller
>Affects Versions: 4.3.0
> Environment: KVM
> branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Kelven Yang
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Create advanced zone
> Step 2 : Depoy and vm VM-QA1
> Step 3 : Create new network
> Step 4 : Add new nic to VM-QA1
> Result
> Failed to add new nic to the vm, below error observed
> nstanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd, cmdInfo:
> {"response":"json","sessionkey":"ZZ4QXAUZwIPe83MSDipOFbHVpwo\u003d","virtualmachineid":"751ac91a-9a63-4d75-9700-70e269b539a4","cmdEventType":"NIC.CREATE","ctxUserId":"2","httpmethod":"GET","_":"1388332341748","ctxAccountId":"2","networkid":"ac35a773-08d1-4f55-9a57-bf0b78111698","ctxStartEventId":"16101"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-29 07:49:06,291 DEBUG [c.c.u.d.T.Transaction]
> (Job-Executor-29:ctx-f5b59752 ctx-fbfc6d7f) Rolling back the transaction:
> Time = 91 Name = Job-Executor-29; called by
> -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue:4525-VirtualMachineManagerImpl.addVmToNetwork:3112-UserVmManagerImpl.addNicToVirtualMachine:1038-GeneratedMethodAccessor813.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:616-AopUtils.invokeJoinpointUsingReflection:317
> 2013-12-29 07:49:06,324 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-29:ctx-f5b59752) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to serialize:
> com.cloud.vm.VmWorkAddVmToNetwork@57ca10b0
> at
> org.apache.cloudstack.framework.jobs.impl.JobSerializerHelper.toObjectSerializedString(JobSerializerHelper.java:118)
> at com.cloud.vm.VmWorkSerializer.serialize(VmWorkSerializer.java:63)
> at
> com.cloud.vm.VirtualMachineManagerImpl$10.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:4554)
> at
> com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
> at
> com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> at
> com.cloud.vm.VirtualMachineManagerImpl.addVmToNetworkThroughJobQueue(VirtualMachineManagerImpl.java:4525)
> at
> com.cloud.vm.VirtualMachineManagerImpl.addVmToNetwork(VirtualMachineManagerImpl.java:3112)
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:1038)
> at sun.reflect.GeneratedMethodAccessor813.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy169.addNicToVirtualMachine(Unknown Source)
> at
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:110)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobI
[jira] [Reopened] (CLOUDSTACK-5447) [Automation] Volume migration failing with NullPointerException in vmware and KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan reopened CLOUDSTACK-5447:
-
Still facing storage migration issue in vmware,
2014-01-01 21:39:22,502 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-93:ctx-b606242c) Done executing
org.apache.cloudstack.api.command. user.volume.MigrateVolumeCmd for
job-4761
2014-01-01 21:39:22,505 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-56:ctx-bb7ebc62) Complete async job-4761, jobStatus: FAILED,
resul tCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
to migrate volu me"}
2014-01-01 21:39:22,513 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-93:ctx-b606242c) Remove job-4761 from job monitoring
2014-01-01 21:39:22,513 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-56:ctx-bb7ebc62) Done executing
org.apache.cloudstack.api.command. user.volume.MigrateVolumeCmd for
job-4761
2014-01-01 21:39:22,518 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-56:ctx-bb7ebc62) Remove job-4761 from job monitoring
2014-01-01 21:39:22,520 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl]
(Job-Executor-6:ctx-f66dc601) Sync queue (367) is currently empty
2014-01-01 21:39:22,521 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-6:ctx-f66dc601) Remove job-4762 from job monitoring
2014-01-01 21:39:22,636 INFO [c.c.h.v.r.VmwareResource]
(DirectAgent-56:ctx-dff965fd 10.223.250.130) Destroy template volume
26af4375b1d13ff69a 51cbbac2347bb8
2014-01-01 21:39:22,793 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 6-7876: Processing Seq 6-7876: { Cmd ,
MgmtId: -1,via: 6, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":3,"_loadInfo":"{\n
\"connections\": []\n}","wa it":0}}] }
2014-01-01 21:39:22,798 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 6-7876: Sending Seq 6-7876: { Ans: ,
MgmtId: 90928 106758026, via: 6, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2014-01-01 21:39:23,036 ERROR [c.c.h.v.r.VmwareResource]
(DirectAgent-56:ctx-dff965fd 10.223.250.130) DestroyCommand failed due to
Exception: ja va.lang.RuntimeException
Message: Invalid configuration for device '0'.
java.lang.RuntimeException: Invalid configuration for device '0'.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:336)
at com.cloud.hypervisor.vmware.mo.BaseMO.destroy(BaseMO.java:75)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:7017)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:456)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-01-01 21:39:23,037 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-56:ctx-dff965fd) Seq 2-834934157: Response Received:
2014-01-01 21:39:23,037 DEBUG [c.c.a.t.Request] (DirectAgent-56:ctx-dff965fd)
Seq 2-834934157: Processing: { Ans: , MgmtId: 90928106758026, via :
2, Ver: v1, Flags: 110,
[{"com.cloud.agent.api.Answer":{"result":false,"details":"DestroyCommand failed
due to Exception: java.lang.RuntimeExc eption\nMessage: Invalid
configuration for device '0'.\n","wait":0}}] }
> [Automation] Volume migration failing with NullPointerException in vmware and
> KVM
> -
>
> Key: CLOUDSTACK-5447
>
[jira] [Updated] (CLOUDSTACK-5447) [Automation] Volume migration failing with NullPointerException in vmware and KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5447:
Attachment: management-server.rar
> [Automation] Volume migration failing with NullPointerException in vmware and
> KVM
> -
>
> Key: CLOUDSTACK-5447
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5447
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, VMware, Volumes
>Affects Versions: 4.3.0
> Environment: vmware 5.0
> branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Sateesh Chodapuneedi
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar, management-server.rar
>
>
> Steps to reproduce
> Step 1 : Deploy advanced zone in vm ware with two primary storage in a cluster
> Step 2 : Deploy VM vm1
> Step 3 : migrate volume of vm to second primary storage
> Actual result
> Migration failed with below error
> 2013-12-10 11:39:20,642 DEBUG [c.c.a.t.Request]
> (DirectAgent-320:ctx-47dcbdc1) Seq 2-34478645: Executing: { Cmd , MgmtId:
> 90928106758026, via: 2(10.223.250.130), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.storage.MigrateVolumeCommand":{"volumeId":374,"volumePath":"ROOT-324","pool":{"id":1,"uuid":"6cfb1cb3-1909-3295-a4d3-8920e5cf0b00","host":"10.223.240.164","path":"/home/common/automation/SC-CLOUD-QA03/primary1","port":2049,"type":"NetworkFilesystem"},"wait":0}}]
> }
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Executing request
> 2013-12-10 11:39:20,643 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-75:ctx-5c8b7163 10.223.250.130) Executing resource
> MigrateVolumeCommand:
> {"volumeId":374,"volumePath":"ROOT-324","pool":{"id":1,"uuid":"6cfb1cb3-1909-3295-a4d3-8920e5cf0b00","host":"10.223.240.164","path":"/home/common/automation/SC-CLOUD-QA03/primary1","port":2049,"type":"NetworkFilesystem"},"wait":0}
> 2013-12-10 11:39:20,643 WARN [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Exception Caught while
> executing command
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4347)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:457)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Response Received:
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.t.Request] (DirectAgent-75:ctx-5c8b7163)
> Seq 2-34478645: Processing: { Ans: , MgmtId: 90928106758026, via: 2, Ver:
> v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"java.lang.NullPointerException","wait":0}}]
> }
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.t.Request]
> (Job-Executor-142:ctx-1d4fa953 ctx-f2be2981) Seq 2-34478645: Received: {
> Ans: , MgmtId: 90928106758026, via: 2, Ver: v1, Flags: 110, { Answer } }
> 2013-12-10 11:39:20,644 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-142:ctx-1d4fa953 ctx-f2be2981) copy failed
> com.cloud.utils.exception.CloudRuntimeException: Failed to migrate volume
> org.apache.cloudstack.storage.volume.VolumeObject@16ed3557 to storage pool
> org.apache.cloudstack.storage.datastore.Pri
[jira] [Resolved] (CLOUDSTACK-5708) Fix router template version to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-5708. --- Resolution: Not A Problem Router template has not changed in 4.3 4.2 template is used in 4.3 also. There is no separate 4.3 template > Fix router template version to 4.3 > -- > > Key: CLOUDSTACK-5708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5708 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Virtual Router >Affects Versions: 4.3.0 > Environment: Any hypervisor >Reporter: Sowmya Krishnan >Assignee: Kishan Kavala > Fix For: 4.3.0 > > > Deploy latest 4.3 > Create a network > Start up router > Verify router version using listrouters or UI: Infrastructure -> Virtual > Routers -> Click on a router -> Version > Shows 4.2 instead of 4.3 > Following is from a hyper-v setup for which we had new template. > Version needs to be fixed for other hypervisor templates as well. > DB: > id: 55 > element_id: 1 > public_mac_address: 06:10:40:00:00:18 > public_ip_address: 10.102.196.212 > public_netmask: 255.255.255.0 > guest_netmask: NULL >guest_ip_address: NULL > is_redundant_router: 0 >priority: 0 > is_priority_bumpup: 0 > redundant_state: UNKNOWN >stop_pending: 0 >role: VIRTUAL_ROUTER >template_version: Cloudstack Release 4.2.0 Wed Dec 4 11:08:17 UTC 2013 > scripts_version: 0f19d23eebd2679921f1d5a252a6f7c0 > vpc_id: NULL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5708) Fix router template version to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala reassigned CLOUDSTACK-5708: - Assignee: Kishan Kavala > Fix router template version to 4.3 > -- > > Key: CLOUDSTACK-5708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5708 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Virtual Router >Affects Versions: 4.3.0 > Environment: Any hypervisor >Reporter: Sowmya Krishnan >Assignee: Kishan Kavala > Fix For: 4.3.0 > > > Deploy latest 4.3 > Create a network > Start up router > Verify router version using listrouters or UI: Infrastructure -> Virtual > Routers -> Click on a router -> Version > Shows 4.2 instead of 4.3 > Following is from a hyper-v setup for which we had new template. > Version needs to be fixed for other hypervisor templates as well. > DB: > id: 55 > element_id: 1 > public_mac_address: 06:10:40:00:00:18 > public_ip_address: 10.102.196.212 > public_netmask: 255.255.255.0 > guest_netmask: NULL >guest_ip_address: NULL > is_redundant_router: 0 >priority: 0 > is_priority_bumpup: 0 > redundant_state: UNKNOWN >stop_pending: 0 >role: VIRTUAL_ROUTER >template_version: Cloudstack Release 4.2.0 Wed Dec 4 11:08:17 UTC 2013 > scripts_version: 0f19d23eebd2679921f1d5a252a6f7c0 > vpc_id: NULL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5447) [Automation] Volume migration failing with NullPointerException in vmware and KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-5447.
--
Resolution: Fixed
NullPointerException issue reported in this bug is fixed.
Please reopen for the same issue.
Kindly raise separate ticket for any other issues observed in volume migration
operation.
> [Automation] Volume migration failing with NullPointerException in vmware and
> KVM
> -
>
> Key: CLOUDSTACK-5447
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5447
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, VMware, Volumes
>Affects Versions: 4.3.0
> Environment: vmware 5.0
> branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Sateesh Chodapuneedi
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar, management-server.rar
>
>
> Steps to reproduce
> Step 1 : Deploy advanced zone in vm ware with two primary storage in a cluster
> Step 2 : Deploy VM vm1
> Step 3 : migrate volume of vm to second primary storage
> Actual result
> Migration failed with below error
> 2013-12-10 11:39:20,642 DEBUG [c.c.a.t.Request]
> (DirectAgent-320:ctx-47dcbdc1) Seq 2-34478645: Executing: { Cmd , MgmtId:
> 90928106758026, via: 2(10.223.250.130), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.storage.MigrateVolumeCommand":{"volumeId":374,"volumePath":"ROOT-324","pool":{"id":1,"uuid":"6cfb1cb3-1909-3295-a4d3-8920e5cf0b00","host":"10.223.240.164","path":"/home/common/automation/SC-CLOUD-QA03/primary1","port":2049,"type":"NetworkFilesystem"},"wait":0}}]
> }
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Executing request
> 2013-12-10 11:39:20,643 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-75:ctx-5c8b7163 10.223.250.130) Executing resource
> MigrateVolumeCommand:
> {"volumeId":374,"volumePath":"ROOT-324","pool":{"id":1,"uuid":"6cfb1cb3-1909-3295-a4d3-8920e5cf0b00","host":"10.223.240.164","path":"/home/common/automation/SC-CLOUD-QA03/primary1","port":2049,"type":"NetworkFilesystem"},"wait":0}
> 2013-12-10 11:39:20,643 WARN [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Exception Caught while
> executing command
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4347)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:457)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Response Received:
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.t.Request] (DirectAgent-75:ctx-5c8b7163)
> Seq 2-34478645: Processing: { Ans: , MgmtId: 90928106758026, via: 2, Ver:
> v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"java.lang.NullPointerException","wait":0}}]
> }
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.t.Request]
> (Job-Executor-142:ctx-1d4fa953 ctx-f2be2981) Seq 2-34478645: Received: {
> Ans: , MgmtId: 90928106758026, via: 2, Ver: v1, Flags: 110, { Answer } }
> 2013-12-10 11:39:20,644 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-142:ctx-1d4fa953 ctx-f2be2981) copy failed
> com.cloud.utils.exception
[jira] [Resolved] (CLOUDSTACK-5192) [Automation] Test case TestSecurityGroup.test_08_security_group failed, expected exception not raised
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye resolved CLOUDSTACK-5192.
Resolution: Fixed
> [Automation] Test case TestSecurityGroup.test_08_security_group failed,
> expected exception not raised
> --
>
> Key: CLOUDSTACK-5192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5192
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.3.0
> Environment: KVM automation
>Reporter: Rayees Namathponnan
>Assignee: Gaurav Aradhye
> Fix For: 4.3.0
>
>
> Test cases
> integration.component.test_project_resources.TestSecurityGroup.test_08_security_group
> failed in Basic SG KVM automation run; observed below error
> Error Message
> Exception not raised
> >> begin captured logging <<
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Created security group with ID: 81914871-83e9-44ee-b882-ccd90226ef2e
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Authorizing ingress rule for sec group ID:
> 81914871-83e9-44ee-b882-ccd90226ef2e for ssh access
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deployed VM (ID: 3169df57-1f93-4180-a290-7af45a5b605b) in project:
> 6b78292d-921d-4c14-8e6c-e0b0138e13b7
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deploying VM with security group: 81914871-83e9-44ee-b882-ccd90226ef2e
> outside project:6b78292d-921d-4c14-8e6c-e0b0138e13b7
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_project_resources.py",
> line 1320, in test_08_security_group
> securitygroupids=[security_group.id],
> File "/usr/local/lib/python2.7/unittest/case.py", line 112, in __exit__
> "{0} not raised".format(exc_name))
> Exception not raised
> >> begin captured logging <<
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Created security group with ID: 81914871-83e9-44ee-b882-ccd90226ef2e
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Authorizing ingress rule for sec group ID:
> 81914871-83e9-44ee-b882-ccd90226ef2e for ssh access
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deployed VM (ID: 3169df57-1f93-4180-a290-7af45a5b605b) in project:
> 6b78292d-921d-4c14-8e6c-e0b0138e13b7
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deploying VM with security group: 81914871-83e9-44ee-b882-ccd90226ef2e
> outside project:6b78292d-921d-4c14-8e6c-e0b0138e13b7
> - >> end captured logging << -
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Reopened] (CLOUDSTACK-5447) [Automation] Volume migration failing with NullPointerException in vmware and KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan reopened CLOUDSTACK-5447:
-
Hi Satheesh,
We no need to open new defect, because the issue reported in defect still not
fixed, reopening
> [Automation] Volume migration failing with NullPointerException in vmware and
> KVM
> -
>
> Key: CLOUDSTACK-5447
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5447
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, VMware, Volumes
>Affects Versions: 4.3.0
> Environment: vmware 5.0
> branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Sateesh Chodapuneedi
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar, management-server.rar
>
>
> Steps to reproduce
> Step 1 : Deploy advanced zone in vm ware with two primary storage in a cluster
> Step 2 : Deploy VM vm1
> Step 3 : migrate volume of vm to second primary storage
> Actual result
> Migration failed with below error
> 2013-12-10 11:39:20,642 DEBUG [c.c.a.t.Request]
> (DirectAgent-320:ctx-47dcbdc1) Seq 2-34478645: Executing: { Cmd , MgmtId:
> 90928106758026, via: 2(10.223.250.130), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.storage.MigrateVolumeCommand":{"volumeId":374,"volumePath":"ROOT-324","pool":{"id":1,"uuid":"6cfb1cb3-1909-3295-a4d3-8920e5cf0b00","host":"10.223.240.164","path":"/home/common/automation/SC-CLOUD-QA03/primary1","port":2049,"type":"NetworkFilesystem"},"wait":0}}]
> }
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Executing request
> 2013-12-10 11:39:20,643 INFO [c.c.h.v.r.VmwareResource]
> (DirectAgent-75:ctx-5c8b7163 10.223.250.130) Executing resource
> MigrateVolumeCommand:
> {"volumeId":374,"volumePath":"ROOT-324","pool":{"id":1,"uuid":"6cfb1cb3-1909-3295-a4d3-8920e5cf0b00","host":"10.223.240.164","path":"/home/common/automation/SC-CLOUD-QA03/primary1","port":2049,"type":"NetworkFilesystem"},"wait":0}
> 2013-12-10 11:39:20,643 WARN [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Exception Caught while
> executing command
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4347)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:457)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-75:ctx-5c8b7163) Seq 2-34478645: Response Received:
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.t.Request] (DirectAgent-75:ctx-5c8b7163)
> Seq 2-34478645: Processing: { Ans: , MgmtId: 90928106758026, via: 2, Ver:
> v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"java.lang.NullPointerException","wait":0}}]
> }
> 2013-12-10 11:39:20,643 DEBUG [c.c.a.t.Request]
> (Job-Executor-142:ctx-1d4fa953 ctx-f2be2981) Seq 2-34478645: Received: {
> Ans: , MgmtId: 90928106758026, via: 2, Ver: v1, Flags: 110, { Answer } }
> 2013-12-10 11:39:20,644 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-142:ctx-1d4fa953 ctx-f2be2981) copy failed
> com.cloud.utils.exception.CloudRuntimeException: Failed to migrate volume
> org.apache.cloudstack.storage.volume.VolumeOb
[jira] [Closed] (CLOUDSTACK-3828) [Automation ]test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated failed to delete network
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye closed CLOUDSTACK-3828.
--
Resolution: Fixed
The 2 tests in these test suite have passed all the recent builds on all
hypervisors.
Closing this.
> [Automation ]test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated failed to
> delete network
>
>
> Key: CLOUDSTACK-3828
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3828
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.2.0
> Environment: Automation
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
> Fix For: 4.3.0
>
>
> Test case component/test_vpc_vm_life_cycle.py:TestVMLifeCycleBothIsolated
> failed, test case failed to delete network, observed below error in log
> Error Message
> Warning: Exception during cleanup : Execute cmd: deletenetworkoffering
> failed, due to: errorCode: 431, errorText:Can't delete network offering 51 as
> its used by 1 networks. To make the network offering unavaiable, disable it
> Stacktrace
> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 227, in
> run
> self.tearDown()
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 350, in
> tearDown
> self.teardownContext(ancestor)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 366, in
> teardownContext
> try_run(context, names)
> File "/usr/local/lib/python2.7/site-packages/nose/util.py", line 469, in
> try_run
> return func()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_vpc_vm_life_cycle.py",
> line 1790, in tearDownClass
> raise Exception("Warning: Exception during cleanup : %s" % e)
> Exception: Warning: Exception during cleanup : Execute cmd:
> deletenetworkoffering failed, due to: errorCode: 431, errorText:Can't delete
> network offering 51 as its used by 1 networks. To make the network offering
> unavaiable, disable it
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5192) [Automation] Test case TestSecurityGroup.test_08_security_group failed, expected exception not raised
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye closed CLOUDSTACK-5192.
--
> [Automation] Test case TestSecurityGroup.test_08_security_group failed,
> expected exception not raised
> --
>
> Key: CLOUDSTACK-5192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5192
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.3.0
> Environment: KVM automation
>Reporter: Rayees Namathponnan
>Assignee: Gaurav Aradhye
> Fix For: 4.3.0
>
>
> Test cases
> integration.component.test_project_resources.TestSecurityGroup.test_08_security_group
> failed in Basic SG KVM automation run; observed below error
> Error Message
> Exception not raised
> >> begin captured logging <<
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Created security group with ID: 81914871-83e9-44ee-b882-ccd90226ef2e
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Authorizing ingress rule for sec group ID:
> 81914871-83e9-44ee-b882-ccd90226ef2e for ssh access
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deployed VM (ID: 3169df57-1f93-4180-a290-7af45a5b605b) in project:
> 6b78292d-921d-4c14-8e6c-e0b0138e13b7
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deploying VM with security group: 81914871-83e9-44ee-b882-ccd90226ef2e
> outside project:6b78292d-921d-4c14-8e6c-e0b0138e13b7
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_project_resources.py",
> line 1320, in test_08_security_group
> securitygroupids=[security_group.id],
> File "/usr/local/lib/python2.7/unittest/case.py", line 112, in __exit__
> "{0} not raised".format(exc_name))
> Exception not raised
> >> begin captured logging <<
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Created security group with ID: 81914871-83e9-44ee-b882-ccd90226ef2e
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Authorizing ingress rule for sec group ID:
> 81914871-83e9-44ee-b882-ccd90226ef2e for ssh access
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deployed VM (ID: 3169df57-1f93-4180-a290-7af45a5b605b) in project:
> 6b78292d-921d-4c14-8e6c-e0b0138e13b7
> test_08_security_group
> (integration.component.test_project_resources.TestSecurityGroup): DEBUG:
> Deploying VM with security group: 81914871-83e9-44ee-b882-ccd90226ef2e
> outside project:6b78292d-921d-4c14-8e6c-e0b0138e13b7
> - >> end captured logging << -
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (CLOUDSTACK-5632) [Automation]template deletion failed because teardown is not waiting for it to download
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye reassigned CLOUDSTACK-5632:
--
Assignee: Gaurav Aradhye
> [Automation]template deletion failed because teardown is not waiting for it
> to download
> ---
>
> Key: CLOUDSTACK-5632
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5632
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.3.0
> Environment: xenserver 62
> advanced zone
>Reporter: Srikanteswararao Talluri
>Assignee: Gaurav Aradhye
> Fix For: 4.3.0
>
>
> Creating this bug as a place holder for the following failures, needs further
> analysis,
> ContextSuite context=TestTemplateHierarchy>:teardown FAILED Warning:
> Exception during cleanup : Execute cmd: asyncquery failed, due to: {errorcode
> : 530, errortext : u'Please specify a template that is not currently being
> downloaded.'}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error "Unable to update VM"
Rayees Namathponnan created CLOUDSTACK-5712:
---
Summary: [Automation] Failed to stop vm during vm destroy command,
observed the error "Unable to update VM"
Key: CLOUDSTACK-5712
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5712
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.3.0
Environment: KVM (RHEL 6.3)
Reporter: Rayees Namathponnan
Priority: Blocker
Fix For: 4.3.0
This issue is observed during regression automation; there are many vm stop
operation failed with below error "Unable to update VM"
2014-01-01 07:59:40,877 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-107:ctx-740b1e62 ctx-e6d04e1c) Successfully released network
resources for the vm VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]
2014-01-01 07:59:40,877 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-107:ctx-740b1e62 ctx-e6d04e1c) Successfully released storage
resources for the vm VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]
2014-01-01 07:59:40,881 DEBUG [c.c.v.d.VMInstanceDaoImpl]
(Job-Executor-107:ctx-740b1e62 ctx-e6d04e1c) Unable to update
VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]: DB Data={Host=1;
State=Stopped; updated=10; time=Wed Jan 01 07:57:53 PST 2014} New Data:
{Host=null; State=Stopped; updated=10; time=Wed Jan 01 07:57:53 PST 2014} Stale
Data: {Host=1; State=Stopping; updated=9; time=Wed Jan 01 07:57:37 PST 2014}
2014-01-01 07:59:40,887 ERROR [c.c.a.ApiAsyncJobDispatcher]
(Job-Executor-107:ctx-740b1e62) Unexpected exception while executing
org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
com.cloud.utils.exception.CloudRuntimeException: unable to stop
VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1475)
at
com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1528)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:256)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:223)
at com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3616)
at com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:2085)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy169.destroyVm(Unknown Source)
at
org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:112)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at
com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache
[jira] [Updated] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error "Unable to update VM"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-5712:
Attachment: management-server.rar
> [Automation] Failed to stop vm during vm destroy command, observed the error
> "Unable to update VM"
> ---
>
> Key: CLOUDSTACK-5712
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5712
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.3.0
> Environment: KVM (RHEL 6.3)
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: management-server.rar
>
>
> This issue is observed during regression automation; there are many vm stop
> operation failed with below error "Unable to update VM"
> 2014-01-01 07:59:40,877 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-107:ctx-740b1e62 ctx-e6d04e1c) Successfully released network
> resources for the vm VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]
> 2014-01-01 07:59:40,877 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-107:ctx-740b1e62 ctx-e6d04e1c) Successfully released storage
> resources for the vm VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]
> 2014-01-01 07:59:40,881 DEBUG [c.c.v.d.VMInstanceDaoImpl]
> (Job-Executor-107:ctx-740b1e62 ctx-e6d04e1c) Unable to update
> VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]: DB Data={Host=1;
> State=Stopped; updated=10; time=Wed Jan 01 07:57:53 PST 2014} New Data:
> {Host=null; State=Stopped; updated=10; time=Wed Jan 01 07:57:53 PST 2014}
> Stale Data: {Host=1; State=Stopping; updated=9; time=Wed Jan 01 07:57:37 PST
> 2014}
> 2014-01-01 07:59:40,887 ERROR [c.c.a.ApiAsyncJobDispatcher]
> (Job-Executor-107:ctx-740b1e62) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
> com.cloud.utils.exception.CloudRuntimeException: unable to stop
> VM[User|QA-2ce28269-1eea-4514-8d75-59272f71f5ff]
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1475)
> at
> com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1528)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:256)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:223)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3616)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:2085)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy169.destroyVm(Unknown Source)
> at
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:112)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53
[jira] [Commented] (CLOUDSTACK-5636) [Automation]Failed to upgrade network offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860055#comment-13860055
]
ASF subversion and git services commented on CLOUDSTACK-5636:
-
Commit 8f15fc1fc13c2aa4ebb6ccc618b5192eae2e6063 in branch refs/heads/4.3 from
[~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8f15fc1 ]
CLOUDSTACK-5636: Fixed issue 'Failed to upgrade network offering' in
test_vpc_network test suite
> [Automation]Failed to upgrade network offering
> --
>
> Key: CLOUDSTACK-5636
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5636
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.3.0
> Environment: xenserver 62
> advanced zone
>Reporter: Srikanteswararao Talluri
>Assignee: Gaurav Aradhye
> Fix For: 4.3.0
>
>
> Creating this bug as a place holder for the following failures, needs further
> analysis,
> test_01_network_services_upgrade FAILED failed to upgrade the network
> offering- Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext
> : u'Failed to shutdown the network elements and resources as a part of update
> to network with specified id; network is in wrong state: Shutdown'}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5636) [Automation]Failed to upgrade network offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye resolved CLOUDSTACK-5636.
Resolution: Fixed
> [Automation]Failed to upgrade network offering
> --
>
> Key: CLOUDSTACK-5636
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5636
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.3.0
> Environment: xenserver 62
> advanced zone
>Reporter: Srikanteswararao Talluri
>Assignee: Gaurav Aradhye
> Fix For: 4.3.0
>
>
> Creating this bug as a place holder for the following failures, needs further
> analysis,
> test_01_network_services_upgrade FAILED failed to upgrade the network
> offering- Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext
> : u'Failed to shutdown the network elements and resources as a part of update
> to network with specified id; network is in wrong state: Shutdown'}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Reopened] (CLOUDSTACK-5708) Fix router template version to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sowmya Krishnan reopened CLOUDSTACK-5708: - This is required for hyper-v since we have a new template for hyper-v > Fix router template version to 4.3 > -- > > Key: CLOUDSTACK-5708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5708 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Virtual Router >Affects Versions: 4.3.0 > Environment: Any hypervisor >Reporter: Sowmya Krishnan >Assignee: Kishan Kavala > Labels: hyper-v > Fix For: 4.3.0 > > > Deploy latest 4.3 > Create a network > Start up router > Verify router version using listrouters or UI: Infrastructure -> Virtual > Routers -> Click on a router -> Version > Shows 4.2 instead of 4.3 > Following is from a hyper-v setup for which we had new template. > Version needs to be fixed for other hypervisor templates as well. > DB: > id: 55 > element_id: 1 > public_mac_address: 06:10:40:00:00:18 > public_ip_address: 10.102.196.212 > public_netmask: 255.255.255.0 > guest_netmask: NULL >guest_ip_address: NULL > is_redundant_router: 0 >priority: 0 > is_priority_bumpup: 0 > redundant_state: UNKNOWN >stop_pending: 0 >role: VIRTUAL_ROUTER >template_version: Cloudstack Release 4.2.0 Wed Dec 4 11:08:17 UTC 2013 > scripts_version: 0f19d23eebd2679921f1d5a252a6f7c0 > vpc_id: NULL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5708) Fix router template version to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sowmya Krishnan resolved CLOUDSTACK-5708. - Resolution: Duplicate This was fixed as part of this commit: Commit fc306d13bf00d8039f36b329ea5dbf252b31c817 in branch refs/heads/master from Rajesh Battala [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fc306d1 ] as mentioned in CLOUDSTACK-5602 > Fix router template version to 4.3 > -- > > Key: CLOUDSTACK-5708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5708 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Virtual Router >Affects Versions: 4.3.0 > Environment: Any hypervisor >Reporter: Sowmya Krishnan >Assignee: Kishan Kavala > Labels: hyper-v > Fix For: 4.3.0 > > > Deploy latest 4.3 > Create a network > Start up router > Verify router version using listrouters or UI: Infrastructure -> Virtual > Routers -> Click on a router -> Version > Shows 4.2 instead of 4.3 > Following is from a hyper-v setup for which we had new template. > Version needs to be fixed for other hypervisor templates as well. > DB: > id: 55 > element_id: 1 > public_mac_address: 06:10:40:00:00:18 > public_ip_address: 10.102.196.212 > public_netmask: 255.255.255.0 > guest_netmask: NULL >guest_ip_address: NULL > is_redundant_router: 0 >priority: 0 > is_priority_bumpup: 0 > redundant_state: UNKNOWN >stop_pending: 0 >role: VIRTUAL_ROUTER >template_version: Cloudstack Release 4.2.0 Wed Dec 4 11:08:17 UTC 2013 > scripts_version: 0f19d23eebd2679921f1d5a252a6f7c0 > vpc_id: NULL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5708) Fix router template version to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sowmya Krishnan updated CLOUDSTACK-5708: Labels: hyper-v (was: ) > Fix router template version to 4.3 > -- > > Key: CLOUDSTACK-5708 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5708 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Virtual Router >Affects Versions: 4.3.0 > Environment: Any hypervisor >Reporter: Sowmya Krishnan >Assignee: Kishan Kavala > Labels: hyper-v > Fix For: 4.3.0 > > > Deploy latest 4.3 > Create a network > Start up router > Verify router version using listrouters or UI: Infrastructure -> Virtual > Routers -> Click on a router -> Version > Shows 4.2 instead of 4.3 > Following is from a hyper-v setup for which we had new template. > Version needs to be fixed for other hypervisor templates as well. > DB: > id: 55 > element_id: 1 > public_mac_address: 06:10:40:00:00:18 > public_ip_address: 10.102.196.212 > public_netmask: 255.255.255.0 > guest_netmask: NULL >guest_ip_address: NULL > is_redundant_router: 0 >priority: 0 > is_priority_bumpup: 0 > redundant_state: UNKNOWN >stop_pending: 0 >role: VIRTUAL_ROUTER >template_version: Cloudstack Release 4.2.0 Wed Dec 4 11:08:17 UTC 2013 > scripts_version: 0f19d23eebd2679921f1d5a252a6f7c0 > vpc_id: NULL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5636) [Automation]Failed to upgrade network offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860065#comment-13860065
]
ASF subversion and git services commented on CLOUDSTACK-5636:
-
Commit 97ede2524c1e19a5de68deab7c5d8327d26a81e9 in branch refs/heads/master
from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=97ede25 ]
CLOUDSTACK-5636: Fixed issue 'Failed to upgrade network offering' in
test_vpc_network test suite
Conflicts:
test/integration/component/test_vpc_network.py
> [Automation]Failed to upgrade network offering
> --
>
> Key: CLOUDSTACK-5636
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5636
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.3.0
> Environment: xenserver 62
> advanced zone
>Reporter: Srikanteswararao Talluri
>Assignee: Gaurav Aradhye
> Fix For: 4.3.0
>
>
> Creating this bug as a place holder for the following failures, needs further
> analysis,
> test_01_network_services_upgrade FAILED failed to upgrade the network
> offering- Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext
> : u'Failed to shutdown the network elements and resources as a part of update
> to network with specified id; network is in wrong state: Shutdown'}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Reopened] (CLOUDSTACK-5697) multiple public ranges don't work with vxlan on KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen reopened CLOUDSTACK-5697: - reopening since this only fixes half of the issue (the agent side). The other half is that one can't define multiple ip ranges for public traffic, as it is only vlan compatible. > multiple public ranges don't work with vxlan on KVM > --- > > Key: CLOUDSTACK-5697 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5697 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.3.0 >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.3.0 > > > You can add multiple VLAN/VNI network ranges to your public traffic in > cloudstack, these don't work with VXLAN on KVM. In other words, only guest > traffic type creates VNI interfaces and bridges. Tested a solution and will > push shortly. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5344) [Hyper-V] Console access does not work for any VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860075#comment-13860075 ] ASF subversion and git services commented on CLOUDSTACK-5344: - Commit 48c47101aa9996c68851de878cb2229cf70dcf2b in branch refs/heads/master from [~dlaffe...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48c4710 ] CLOUDSTACK-5344: Updated to allow rdp console to access hyper-v vm virtual framebuffer. > [Hyper-V] Console access does not work for any VM > - > > Key: CLOUDSTACK-5344 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5344 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server >Affects Versions: 4.3.0 > Environment: Latest build from 4.3 >Reporter: Sanjeev N >Assignee: Anshul Gangwar >Priority: Blocker > Labels: hyper-V, > Fix For: 4.3.0 > > > [Hyperv-V] Console access does not work for any VM > Steps to Reproduce: > > 1.Bring up CS with latest build from 4.3 using hyperv > 2.Wait for the CPVM to come up. > 3.Deploy guest vm and try to access the vm's console > Result: > === > Server Internal Error -- This message was sent by Atlassian JIRA (v6.1.5#6160)
