[jira] [Resolved] (CLOUDSTACK-3237) [vmware][SM] Migrate volume is failing when there are snapshots for that volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3237. - Resolution: Fixed > [vmware][SM] Migrate volume is failing when there are snapsh

[jira] [Resolved] (CLOUDSTACK-2904) After volume migration on Vmware, taking a snapshot, and then volume migration fails on this new volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-2904. - Resolution: Fixed > After volume migration on Vmware, taking a snapshot, and the

[jira] [Commented] (CLOUDSTACK-2904) After volume migration on Vmware, taking a snapshot, and then volume migration fails on this new volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735597#comment-13735597 ] Kelven Yang commented on CLOUDSTACK-2904: - When root volume is migrated via v

[jira] [Assigned] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-3568: --- Assignee: Kelven Yang (was: Min Chen) > [Automation]Parallel deployment - V

[jira] [Commented] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735615#comment-13735615 ] Kelven Yang commented on CLOUDSTACK-3568: - We need to manage a pool of Vmware

[jira] [Assigned] (CLOUDSTACK-4228) [VMWARE]NPE & operation timed out issues while migrating volumes across different Zone wide primary storages

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4228: --- Assignee: Kelven Yang > [VMWARE]NPE & operation timed out issues while migra

[jira] [Assigned] (CLOUDSTACK-4239) [upgrade][2.2.14 to 4.2][vmware]Snapshot creation after upgrade on ESX 4.1 host fails with "BackupSnapshotCommand exception: javax.xml.ws.soap.SOAPFaultException"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4239: --- Assignee: Kelven Yang > [upgrade][2.2.14 to 4.2][vmware]Snapshot creation af

[jira] [Resolved] (CLOUDSTACK-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3568. - Resolution: Fixed > [Automation]Parallel deployment - Vmware - When deploying 30

[jira] [Resolved] (CLOUDSTACK-3844) [VMWARE]System VMs are failed to start first time with NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3844. - Resolution: Fixed This issues looks like to be related with the scenarios that are a

[jira] [Resolved] (CLOUDSTACK-4228) [VMWARE]NPE & operation timed out issues while migrating volumes across different Zone wide primary storages

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4228. - Resolution: Cannot Reproduce Can't reproduce locally. Please redo it after commit 4

[jira] [Resolved] (CLOUDSTACK-4239) [upgrade][2.2.14 to 4.2][vmware]Snapshot creation after upgrade on ESX 4.1 host fails with "BackupSnapshotCommand exception: javax.xml.ws.soap.SOAPFaultException"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4239. - Resolution: Incomplete Is the problem reproducible? It looks like a run-time situati

[jira] [Commented] (CLOUDSTACK-4264) CLOUDSTACK-3869 breaks detach logic on VMware for managed storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738460#comment-13738460 ] Kelven Yang commented on CLOUDSTACK-4264: - Mike, Thanks. I'll merge all the c

[jira] [Assigned] (CLOUDSTACK-4288) Management server is hanging quite often and in indefinite time intervals.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4288: --- Assignee: Kelven Yang > Management server is hanging quite often and in inde

[jira] [Assigned] (CLOUDSTACK-4239) [upgrade][2.2.14 to 4.2][vmware]Snapshot creation after upgrade on ESX 4.1 host fails with "BackupSnapshotCommand exception: javax.xml.ws.soap.SOAPFaultException"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4239: --- Assignee: edison su (was: Kelven Yang) Edision, could you take a look, I just n

[jira] [Resolved] (CLOUDSTACK-4288) Management server is hanging quite often and in indefinite time intervals.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4288. - Resolution: Fixed > Management server is hanging quite often and in indefinite t

[jira] [Resolved] (CLOUDSTACK-4275) [VMWARE] simultaneous snapshots on different volumes fail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4275. - Resolution: Fixed Please retest it with the build that contains following commit. Re

[jira] [Commented] (CLOUDSTACK-4239) [upgrade][2.2.14 to 4.2][vmware]Snapshot creation after upgrade on ESX 4.1 host fails with "BackupSnapshotCommand exception: javax.xml.ws.soap.SOAPFaultException"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741706#comment-13741706 ] Kelven Yang commented on CLOUDSTACK-4239: - I need more information to determi

[jira] [Resolved] (CLOUDSTACK-4239) [upgrade][2.2.14 to 4.2][vmware]Snapshot creation after upgrade on ESX 4.1 host fails with "BackupSnapshotCommand exception: javax.xml.ws.soap.SOAPFaultException"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4239. - Resolution: Incomplete > [upgrade][2.2.14 to 4.2][vmware]Snapshot creation after

[jira] [Commented] (CLOUDSTACK-4363) [VMware]Migration of data volume is throwing NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743050#comment-13743050 ] Kelven Yang commented on CLOUDSTACK-4363: - This NPE itself has nothing relate

[jira] [Assigned] (CLOUDSTACK-4363) [VMware]Migration of data volume is throwing NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4363: --- Assignee: edison su (was: Kelven Yang) Please check out my comments and fix thi

[jira] [Resolved] (CLOUDSTACK-4363) [VMware]Migration of data volume is throwing NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4363. - Resolution: Fixed I'll mark this NPE bug based on Edison's commit. For runtime excep

[jira] [Resolved] (CLOUDSTACK-4357) [Automation] Failed to create snapshot in vmware, failed with SOAP Exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4357. - Resolution: Fixed This issue is caused by that the caching semantics in VmwareClient

[jira] [Commented] (CLOUDSTACK-4358) [Automation] [vmware] Few VM deployment failed with IndexOutOfBoundsException at "VolumeManagerImpl.java:2534"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743158#comment-13743158 ] Kelven Yang commented on CLOUDSTACK-4358: - This should be caused by the same

[jira] [Resolved] (CLOUDSTACK-4358) [Automation] [vmware] Few VM deployment failed with IndexOutOfBoundsException at "VolumeManagerImpl.java:2534"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4358. - Resolution: Fixed > [Automation] [vmware] Few VM deployment failed with IndexOut

[jira] [Created] (CLOUDSTACK-4390) Using full-clone by default for VMware deployment

Kelven Yang created CLOUDSTACK-4390: --- Summary: Using full-clone by default for VMware deployment Key: CLOUDSTACK-4390 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4390 Project: CloudStack

[jira] [Resolved] (CLOUDSTACK-4390) Using full-clone by default for VMware deployment

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4390. - Resolution: Fixed > Using full-clone by default for VMware deployment >

[jira] [Resolved] (CLOUDSTACK-4358) [Automation] [vmware] Few VM deployment failed with IndexOutOfBoundsException at "VolumeManagerImpl.java:2534"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4358. - Resolution: Fixed > [Automation] [vmware] Few VM deployment failed with IndexOut

[jira] [Commented] (CLOUDSTACK-4376) [Automation] [vmware] Failed to deploy VPC router in parallel deployment scenario

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743579#comment-13743579 ] Kelven Yang commented on CLOUDSTACK-4376: - Following commit contains a fix fo

[jira] [Resolved] (CLOUDSTACK-4376) [Automation] [vmware] Failed to deploy VPC router in parallel deployment scenario

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4376. - Resolution: Fixed > [Automation] [vmware] Failed to deploy VPC router in paralle

[jira] [Commented] (CLOUDSTACK-4376) [Automation] [vmware] Failed to deploy VPC router in parallel deployment scenario

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745512#comment-13745512 ] Kelven Yang commented on CLOUDSTACK-4376: - Thanks Rayee to reproduce the prob

[jira] [Resolved] (CLOUDSTACK-4376) [Automation] [vmware] Failed to deploy VPC router in parallel deployment scenario

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4376. - Resolution: Fixed > [Automation] [vmware] Failed to deploy VPC router in paralle

[jira] [Assigned] (CLOUDSTACK-2904) After volume migration on Vmware, taking a snapshot, and then volume migration fails on this new volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-2904: --- Assignee: Kelven Yang > After volume migration on Vmware, taking a snapshot,

[jira] [Assigned] (CLOUDSTACK-3237) [vmware][SM] Migrate volume is failing when there are snapshots for that volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-3237: --- Assignee: Kelven Yang > [vmware][SM] Migrate volume is failing when there ar

[jira] [Resolved] (CLOUDSTACK-4063) Unidentified detached data disk names in CS don’t match what is in Vmware

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4063. - Resolution: Fixed This will be fixed automatically when fix of 3869 is in place

[jira] [Resolved] (CLOUDSTACK-3869) Current VMware datastore layout structure breaks storage live motion

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3869. - Resolution: Fixed > Current VMware datastore layout structure breaks storage liv

[jira] [Resolved] (CLOUDSTACK-3778) [VMware] SSVM VM fails to create for the first time with message "specified key already exists".

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3778. - Resolution: Fixed > [VMware] SSVM VM fails to create for the first time with me

[jira] [Commented] (CLOUDSTACK-3534) SQL Exception while updating Async job status when trying to put cluster level primary storage into maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720309#comment-13720309 ] Kelven Yang commented on CLOUDSTACK-3534: - Please do following configuration

[jira] [Created] (CLOUDSTACK-3869) Current VMware datastore layout structure breaks storage live motion

Kelven Yang created CLOUDSTACK-3869: --- Summary: Current VMware datastore layout structure breaks storage live motion Key: CLOUDSTACK-3869 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3869 Pr

[jira] [Commented] (CLOUDSTACK-3534) SQL Exception while updating Async job status when trying to put cluster level primary storage into maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722690#comment-13722690 ] Kelven Yang commented on CLOUDSTACK-3534: - Please do following configuration

[jira] [Created] (CLOUDSTACK-4950) Latest VMware SDK client has a problem to support sessions towards multiple vCenter instance within the same JVM

Kelven Yang created CLOUDSTACK-4950: --- Summary: Latest VMware SDK client has a problem to support sessions towards multiple vCenter instance within the same JVM Key: CLOUDSTACK-4950 URL: https://issues.apache.org

[jira] [Resolved] (CLOUDSTACK-4950) Latest VMware SDK client has a problem to support sessions towards multiple vCenter instance within the same JVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4950. - Resolution: Fixed > Latest VMware SDK client has a problem to support sessions towar

[jira] [Resolved] (CLOUDSTACK-3237) [vmware][SM] Migrate volume is failing when there are snapshots for that volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3237. - Resolution: Fixed > [vmware][SM] Migrate volume is failing when there are snapsh

[jira] [Resolved] (CLOUDSTACK-4358) [Automation] [vmware] Few VM deployment failed with IndexOutOfBoundsException at "VolumeManagerImpl.java:2534"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4358. - Resolution: Fixed I believe IndexOutOfBoundsException issue is fixed by VMware sessi

[jira] [Commented] (CLOUDSTACK-4430) [Automation][vmware] Failed to deploy vm, if one host is down in a cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750877#comment-13750877 ] Kelven Yang commented on CLOUDSTACK-4430: - This is a regresion from object_st

[jira] [Resolved] (CLOUDSTACK-4464) Parallel deployment - Vmware - When deploying 30 parallel Vms , Vm fails to get deployed due to "StartCommand failed due to Exception: javax.xml.ws.soap.SOAPFaultEx

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4464. - Resolution: Fixed Please retry with this commit commit 046a8a889a3338ff86914b42eded

[jira] [Assigned] (CLOUDSTACK-4522) [upgrade][vmware] Creation of VM from ISO is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4522: --- Assignee: Kelven Yang > [upgrade][vmware] Creation of VM from ISO is failing

[jira] [Resolved] (CLOUDSTACK-4522) [upgrade][vmware] Creation of VM from ISO is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4522. - Resolution: Fixed > [upgrade][vmware] Creation of VM from ISO is failing >

[jira] [Created] (CLOUDSTACK-4529) VM internal name should not be retrived seperatly inside a loop, this will cause big performance impact

Kelven Yang created CLOUDSTACK-4529: --- Summary: VM internal name should not be retrived seperatly inside a loop, this will cause big performance impact Key: CLOUDSTACK-4529 URL: https://issues.apache.org/jira/bro

[jira] [Assigned] (CLOUDSTACK-4529) VM internal name should not be retrived seperatly inside a loop, this will cause big performance impact

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4529: --- Assignee: Kelven Yang > VM internal name should not be retrived seperatly in

[jira] [Resolved] (CLOUDSTACK-4529) VM internal name should not be retrived seperatly inside a loop, this will cause big performance impact

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4529. - Resolution: Fixed > VM internal name should not be retrived seperatly inside a l

[jira] [Commented] (CLOUDSTACK-4464) Parallel deployment - Vmware - When deploying 30 parallel Vms , Vm fails to get deployed due to "StartCommand failed due to Exception: javax.xml.ws.soap.SOAPFaultE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751814#comment-13751814 ] Kelven Yang commented on CLOUDSTACK-4464: - commit 687e87faa7a2d828fa428ac0b01

[jira] [Resolved] (CLOUDSTACK-4483) VMWARE:API: VM SNAPSHOTS: VM StartCommand failed with exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4483. - Resolution: Fixed > VMWARE:API: VM SNAPSHOTS: VM StartCommand failed with except

[jira] [Commented] (CLOUDSTACK-4483) VMWARE:API: VM SNAPSHOTS: VM StartCommand failed with exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751831#comment-13751831 ] Kelven Yang commented on CLOUDSTACK-4483: - This is fixed in the effort to sup

[jira] [Resolved] (CLOUDSTACK-4518) unable to start router vm on vmware4.1 after upgrade; hitting exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4518. - Resolution: Fixed > unable to start router vm on vmware4.1 after upgrade; hittin

[jira] [Resolved] (CLOUDSTACK-4464) Parallel deployment - Vmware - When deploying 30 parallel Vms , Vm fails to get deployed due to "StartCommand failed due to Exception: javax.xml.ws.soap.SOAPFaultEx

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4464. - Resolution: Fixed > Parallel deployment - Vmware - When deploying 30 parallel Vm

[jira] [Commented] (CLOUDSTACK-4462) [Automation][vmware] Failed to find vmdk filed during deployment; and deployment failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751974#comment-13751974 ] Kelven Yang commented on CLOUDSTACK-4462: - This should have been fixed with t

[jira] [Resolved] (CLOUDSTACK-4462) [Automation][vmware] Failed to find vmdk filed during deployment; and deployment failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4462. - Resolution: Fixed > [Automation][vmware] Failed to find vmdk filed during deploy

[jira] [Resolved] (CLOUDSTACK-4519) hitting java.lang.RuntimeException during volume deletion of router vm in vmware

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4519. - Resolution: Fixed > hitting java.lang.RuntimeException during volume deletion of

[jira] [Resolved] (CLOUDSTACK-4458) [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4458. - Resolution: Fixed > [VMWare] Failed to create Snapshot on Data Disk because of b

[jira] [Commented] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753329#comment-13753329 ] Kelven Yang commented on CLOUDSTACK-4546: - I looked at the log and checked th

[jira] [Resolved] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4546. - Resolution: Invalid > [Vmware] - Unable to deploy guest VM > ---

[jira] [Resolved] (CLOUDSTACK-4521) [upgrade][vmware]Attaching an uploaded volume to a VM throws NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4521. - Resolution: Cannot Reproduce Not able to reproduce in latest build

[jira] [Commented] (CLOUDSTACK-4521) [upgrade][vmware]Attaching an uploaded volume to a VM throws NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754222#comment-13754222 ] Kelven Yang commented on CLOUDSTACK-4521: - The problem comes from the useless

[jira] [Resolved] (CLOUDSTACK-4362) VM's are failing to start after its DATA volume is migrated to other primary storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4362. - Resolution: Fixed > VM's are failing to start after its DATA volume is migrated

[jira] [Resolved] (CLOUDSTACK-4585) [VMWare] [Upgrade] Failed to start instance after reverting the VM snapshot on a Private Zone which was created prior to upgrade

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4585. - Resolution: Fixed > [VMWare] [Upgrade] Failed to start instance after reverting

[jira] [Created] (CLOUDSTACK-4659) VMware worker VMs garbage collection

Kelven Yang created CLOUDSTACK-4659: --- Summary: VMware worker VMs garbage collection Key: CLOUDSTACK-4659 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4659 Project: CloudStack Issue

[jira] [Resolved] (CLOUDSTACK-4659) VMware worker VMs garbage collection

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4659. - Resolution: Fixed > VMware worker VMs garbage collection > -

[jira] [Commented] (CLOUDSTACK-4659) VMware worker VMs garbage collection

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767203#comment-13767203 ] Kelven Yang commented on CLOUDSTACK-4659: - Test instructions 1) Operate Clou

[jira] [Assigned] (CLOUDSTACK-4734) Creating snapshot from ROOT volume fails with error message - "Failed to create snapshot due to an internal error creating snapshot for volume 14”

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4734: --- Assignee: Kelven Yang > Creating snapshot from ROOT volume fails with error

[jira] [Created] (CLOUDSTACK-4790) [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM

Kelven Yang created CLOUDSTACK-4790: --- Summary: [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM Key: CLOUDSTACK-4790 URL: https://issues.apache.org/jira/browse/

[jira] [Assigned] (CLOUDSTACK-4790) [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang reassigned CLOUDSTACK-4790: --- Assignee: Kelven Yang > [VMware] Reserved SCSI device number prevents CloudStack

[jira] [Resolved] (CLOUDSTACK-4790) [VMware] Reserved SCSI device number prevents CloudStack to attach more than 6 data volumes to a VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4790. - Resolution: Fixed > [VMware] Reserved SCSI device number prevents CloudStack to atta

[jira] [Created] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2

Kelven Yang created CLOUDSTACK-4802: --- Summary: [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2 Key: CLOUDSTACK-4802 URL: https://issues.apache.org/jira/browse/CLOUDST

[jira] [Resolved] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4802. - Resolution: Fixed > [VMware] Unable to start VM if VM has VM snapshot been taken in

[jira] [Created] (CLOUDSTACK-4863) Count CPU hyper-threading as logical CPU core for allocation

Kelven Yang created CLOUDSTACK-4863: --- Summary: Count CPU hyper-threading as logical CPU core for allocation Key: CLOUDSTACK-4863 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4863 Project: C

[jira] [Resolved] (CLOUDSTACK-4863) Count CPU hyper-threading as logical CPU core for allocation

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4863. - Resolution: Fixed > Count CPU hyper-threading as logical CPU core for allocation > -

[jira] [Commented] (CLOUDSTACK-2218) [web.context.ContextLoader] (main:null) Context initialization failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647802#comment-13647802 ] Kelven Yang commented on CLOUDSTACK-2218: - >From the log, it appears to be an

[jira] [Commented] (CLOUDSTACK-2218) [web.context.ContextLoader] (main:null) Context initialization failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651358#comment-13651358 ] Kelven Yang commented on CLOUDSTACK-2218: - >From the information inside the l

[jira] [Resolved] (CLOUDSTACK-2218) [web.context.ContextLoader] (main:null) Context initialization failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-2218. - Resolution: Won't Fix The issue most likely is an environment or a setup issue

[jira] [Created] (CLOUDSTACK-2925) Don't rely on XS to cleanup idle session but proactively close it from console proxy

Kelven Yang created CLOUDSTACK-2925: --- Summary: Don't rely on XS to cleanup idle session but proactively close it from console proxy Key: CLOUDSTACK-2925 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2925

[jira] [Resolved] (CLOUDSTACK-2925) Don't rely on XS to cleanup idle session but proactively close it from console proxy

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-2925. - Resolution: Fixed > Don't rely on XS to cleanup idle session but proactively clo

[jira] [Commented] (CLOUDSTACK-2925) Don't rely on XS to cleanup idle session but proactively close it from console proxy

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680106#comment-13680106 ] Kelven Yang commented on CLOUDSTACK-2925: - Fixed in commit f38c4e9ea684cdec22

[jira] [Created] (CLOUDSTACK-3433) Relax the same package restriction for Command and its derived classes in ArrayTypeAdaptor

Kelven Yang created CLOUDSTACK-3433: --- Summary: Relax the same package restriction for Command and its derived classes in ArrayTypeAdaptor Key: CLOUDSTACK-3433 URL: https://issues.apache.org/jira/browse/CLOUDSTAC

[jira] [Resolved] (CLOUDSTACK-3433) Relax the same package restriction for Command and its derived classes in ArrayTypeAdaptor

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3433. - Resolution: Fixed > Relax the same package restriction for Command and its deriv

[jira] [Created] (CLOUDSTACK-3456) We need to proactively close XAPI initiated console session from console proxy to avoid Deny of Service behave to XenServer host

Kelven Yang created CLOUDSTACK-3456: --- Summary: We need to proactively close XAPI initiated console session from console proxy to avoid Deny of Service behave to XenServer host Key: CLOUDSTACK-3456 URL: https://

[jira] [Commented] (CLOUDSTACK-3456) We need to proactively close XAPI initiated console session from console proxy to avoid Deny of Service behave to XenServer host

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707360#comment-13707360 ] Kelven Yang commented on CLOUDSTACK-3456: - Patch has been submitted to 4.1 br

[jira] [Resolved] (CLOUDSTACK-3456) We need to proactively close XAPI initiated console session from console proxy to avoid Deny of Service behave to XenServer host

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-3456. - Resolution: Fixed > We need to proactively close XAPI initiated console session

[jira] [Updated] (CLOUDSTACK-1276) Remove autoscanning for 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang updated CLOUDSTACK-1276: Priority: Blocker (was: Major) > Remove autoscanning for 4.1 > --

[jira] [Commented] (CLOUDSTACK-1276) Remove autoscanning for 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609679#comment-13609679 ] Kelven Yang commented on CLOUDSTACK-1276: - I raised to blocker as the solutio

[jira] [Resolved] (CLOUDSTACK-1276) Remove autoscanning for 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-1276. - Resolution: Fixed Patch has been submitted > Remove autoscanning fo

[jira] [Resolved] (CLOUDSTACK-1729) Ensure adapter execution order in runtime

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-1729. - Resolution: Fixed Patch has been submitted to 4.1 > Ensure adapter

[jira] [Commented] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611417#comment-13611417 ] Kelven Yang commented on CLOUDSTACK-1664: - This is caused by that nested Even

[jira] [Created] (CLOUDSTACK-1795) Customize AOP to fully support legacy CloudStack @DB and @ActionEvent semantics

Kelven Yang created CLOUDSTACK-1795: --- Summary: Customize AOP to fully support legacy CloudStack @DB and @ActionEvent semantics Key: CLOUDSTACK-1795 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1795

[jira] [Commented] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611982#comment-13611982 ] Kelven Yang commented on CLOUDSTACK-1664: - I'll try to make the fix available

[jira] [Created] (CLOUDSTACK-1818) DatabaseCreator is not invoking UpgradeChecker to run upgrade logic written in Java, which is required for a success upgrade process

Kelven Yang created CLOUDSTACK-1818: --- Summary: DatabaseCreator is not invoking UpgradeChecker to run upgrade logic written in Java, which is required for a success upgrade process Key: CLOUDSTACK-1818 URL: https

[jira] [Commented] (CLOUDSTACK-1818) DatabaseCreator is not invoking UpgradeChecker to run upgrade logic written in Java, which is required for a success upgrade process

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614743#comment-13614743 ] Kelven Yang commented on CLOUDSTACK-1818: - Checked with Alex, we decided to k

[jira] [Resolved] (CLOUDSTACK-1818) DatabaseCreator is not invoking UpgradeChecker to run upgrade logic written in Java, which is required for a success upgrade process

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-1818. - Resolution: Fixed > DatabaseCreator is not invoking UpgradeChecker to run upgrad

[jira] [Resolved] (CLOUDSTACK-1795) Customize AOP to fully support legacy CloudStack @DB and @ActionEvent semantics

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-1795. - Resolution: Fixed Patch has been submitted to 4.1 review board > Cu

[jira] [Resolved] (CLOUDSTACK-1811) Upgrade 4.0->4.1 - When upgrade scripts fail , component loading continues and management server starts.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-1811. - Resolution: Fixed This has been fixed in custom AOP patch. > Upgra

[jira] [Resolved] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-1664. - Resolution: Fixed Event interception semantic has been fully restored in custom Spri

  1   2   >