[jira] [Resolved] (CLOUDSTACK-8319) [VMware] VM's configuration files are left behind on source primary storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8319. Resolution: Fixed [VMware] VM's configuration files are left behind on source

[jira] [Created] (CLOUDSTACK-8611) CS waits indefinitely for CheckS2SVpnConnectionsCommand to return

Likitha Shetty created CLOUDSTACK-8611: -- Summary: CS waits indefinitely for CheckS2SVpnConnectionsCommand to return Key: CLOUDSTACK-8611 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8611

[jira] [Created] (CLOUDSTACK-8612) [VMware] Make vCenter session timeout configurable for volume snapshot

Likitha Shetty created CLOUDSTACK-8612: -- Summary: [VMware] Make vCenter session timeout configurable for volume snapshot Key: CLOUDSTACK-8612 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8612

[jira] [Created] (CLOUDSTACK-8609) [VMware] VM is not accessible after a migration across clusters.

Likitha Shetty created CLOUDSTACK-8609: -- Summary: [VMware] VM is not accessible after a migration across clusters. Key: CLOUDSTACK-8609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8609

[jira] [Created] (CLOUDSTACK-8610) [VMWARE] Unable to attach 7th Disk to a Windows server 2012R2 instance

Likitha Shetty created CLOUDSTACK-8610: -- Summary: [VMWARE] Unable to attach 7th Disk to a Windows server 2012R2 instance Key: CLOUDSTACK-8610 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8610

[jira] [Created] (CLOUDSTACK-8608) Fix unpleasant admin experience with VMware fresh installs/upgrades - System VM's failed to start due to permissions issue

Likitha Shetty created CLOUDSTACK-8608: -- Summary: Fix unpleasant admin experience with VMware fresh installs/upgrades - System VM's failed to start due to permissions issue Key: CLOUDSTACK-8608 URL:

[jira] [Created] (CLOUDSTACK-8602) MigrateVirtualMachineWithVolume leaves old chain data for volume

Likitha Shetty created CLOUDSTACK-8602: -- Summary: MigrateVirtualMachineWithVolume leaves old chain data for volume Key: CLOUDSTACK-8602 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8602

[jira] [Commented] (CLOUDSTACK-8602) MigrateVirtualMachineWithVolume leaves old chain data for volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609756#comment-14609756 ] Likitha Shetty commented on CLOUDSTACK-8602: +Steps to reproduce+ 1. Have

[jira] [Updated] (CLOUDSTACK-8597) [VMware] Failed to migrate a volume from zone-wide to cluster-wide storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8597: --- Summary: [VMware] Failed to migrate a volume from zone-wide to cluster-wide

[jira] [Updated] (CLOUDSTACK-8597) [VMware] Failed to migrate a volume from zone-wide to cluster-wide storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8597: --- Description: +Steps to reproduce+ 1. Have a VMware setup 2 clusters with a ESXi

[jira] [Created] (CLOUDSTACK-8597) Failed to migrate a volume from zone-wide to cluster-wide storage.

Likitha Shetty created CLOUDSTACK-8597: -- Summary: Failed to migrate a volume from zone-wide to cluster-wide storage. Key: CLOUDSTACK-8597 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8597

[jira] [Updated] (CLOUDSTACK-8598) CS reports volume migration as successful but the volume is not migrated in vCenter.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8598: --- Description: +Steps to reproduce+ 1. Deploy a VMware setup with 1 cluster, 2

[jira] [Updated] (CLOUDSTACK-8598) CS reports volume migration as successful but the volume is not migrated in vCenter.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8598: --- Description: +Steps to reproduce+ 1. Deploy a VMware setup with 1 cluster, 2

[jira] [Created] (CLOUDSTACK-8599) CS reports failure for a successful migration in case of low vCenter session timeouts

Likitha Shetty created CLOUDSTACK-8599: -- Summary: CS reports failure for a successful migration in case of low vCenter session timeouts Key: CLOUDSTACK-8599 URL:

[jira] [Created] (CLOUDSTACK-8598) CS reports volume migration as successful but the volume is not migrated in vCenter.

Likitha Shetty created CLOUDSTACK-8598: -- Summary: CS reports volume migration as successful but the volume is not migrated in vCenter. Key: CLOUDSTACK-8598 URL:

[jira] [Created] (CLOUDSTACK-8601) VMFS storage added as local storage can be re added as shared storage.

Likitha Shetty created CLOUDSTACK-8601: -- Summary: VMFS storage added as local storage can be re added as shared storage. Key: CLOUDSTACK-8601 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8601

[jira] [Created] (CLOUDSTACK-8600) Clean up VM folders in storage

Likitha Shetty created CLOUDSTACK-8600: -- Summary: Clean up VM folders in storage Key: CLOUDSTACK-8600 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8600 Project: CloudStack

[jira] [Created] (CLOUDSTACK-8405) [vCenter 5.5] Restore VM on a migrated VM results in the deletion of the data disk.

Likitha Shetty created CLOUDSTACK-8405: -- Summary: [vCenter 5.5] Restore VM on a migrated VM results in the deletion of the data disk. Key: CLOUDSTACK-8405 URL:

[jira] [Updated] (CLOUDSTACK-8405) [vCenter 5.5] Restore VM on a migrated VM results in the deletion of the data disk.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8405: --- Fix Version/s: (was: Future) 4.6.0 [vCenter 5.5] Restore

[jira] [Resolved] (CLOUDSTACK-8405) [vCenter 5.5] Restore VM on a migrated VM results in the deletion of the data disk.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8405. Resolution: Fixed +Issue+ In case of vSphere 5.5, if VM restore is performed

[jira] [Created] (CLOUDSTACK-8411) Volume is stuck in Copying state after a failed attach

Likitha Shetty created CLOUDSTACK-8411: -- Summary: Volume is stuck in Copying state after a failed attach Key: CLOUDSTACK-8411 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8411 Project:

[jira] [Resolved] (CLOUDSTACK-8411) Volume is stuck in Copying state after a failed attach

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8411. Resolution: Fixed Volume is stuck in Copying state after a failed attach

[jira] [Resolved] (CLOUDSTACK-8412) VM migration with storage fails in a clustered management server setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8412. Resolution: Fixed +Root Cause Analysis+ When a request is made to migrate a VM

[jira] [Created] (CLOUDSTACK-8410) VMware ESXi host disconnects frequently

Likitha Shetty created CLOUDSTACK-8410: -- Summary: VMware ESXi host disconnects frequently Key: CLOUDSTACK-8410 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8410 Project: CloudStack

[jira] [Resolved] (CLOUDSTACK-8410) VMware ESXi host disconnects frequently

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8410. Resolution: Fixed VMware ESXi host disconnects frequently

[jira] [Created] (CLOUDSTACK-8412) VM migration with storage fails in a clustered management server setup

Likitha Shetty created CLOUDSTACK-8412: -- Summary: VM migration with storage fails in a clustered management server setup Key: CLOUDSTACK-8412 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8412

[jira] [Created] (CLOUDSTACK-8415) [VMware] SSVM shutdown during snapshot operation results in disks to be left behind

Likitha Shetty created CLOUDSTACK-8415: -- Summary: [VMware] SSVM shutdown during snapshot operation results in disks to be left behind Key: CLOUDSTACK-8415 URL:

[jira] [Resolved] (CLOUDSTACK-8318) Storage vMotion fails in case of VMFS storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8318. Resolution: Fixed Storage vMotion fails in case of VMFS storage.

[jira] [Commented] (CLOUDSTACK-8320) Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358262#comment-14358262 ] Likitha Shetty commented on CLOUDSTACK-8320: author Likitha Shetty

[jira] [Resolved] (CLOUDSTACK-8320) Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8320. Resolution: Fixed Upon a failed migration, a dummy volume is created which

[jira] [Commented] (CLOUDSTACK-8320) Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358260#comment-14358260 ] Likitha Shetty commented on CLOUDSTACK-8320: Stale volumes will be left

[jira] [Commented] (CLOUDSTACK-8318) Storage vMotion fails in case of VMFS storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358211#comment-14358211 ] Likitha Shetty commented on CLOUDSTACK-8318: Since we are enabling

[jira] [Commented] (CLOUDSTACK-8318) Storage vMotion fails in case of VMFS storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358252#comment-14358252 ] Likitha Shetty commented on CLOUDSTACK-8318: author Likitha Shetty

[jira] [Closed] (CLOUDSTACK-8317) Storage vMotion fails in case of VMFS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty closed CLOUDSTACK-8317. -- Resolution: Invalid Storage vMotion fails in case of VMFS

[jira] [Created] (CLOUDSTACK-8319) [VMware] VM's configuration files are left behind on source primary storage

Likitha Shetty created CLOUDSTACK-8319: -- Summary: [VMware] VM's configuration files are left behind on source primary storage Key: CLOUDSTACK-8319 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8319

[jira] [Created] (CLOUDSTACK-8320) Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.

Likitha Shetty created CLOUDSTACK-8320: -- Summary: Upon a failed migration, a dummy volume is created which remains in 'Expunging' state. Key: CLOUDSTACK-8320 URL:

[jira] [Created] (CLOUDSTACK-8317) Storage vMotion fails in case of VMFS

Likitha Shetty created CLOUDSTACK-8317: -- Summary: Storage vMotion fails in case of VMFS Key: CLOUDSTACK-8317 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8317 Project: CloudStack

[jira] [Created] (CLOUDSTACK-8318) Storage vMotion fails in case of VMFS storage.

Likitha Shetty created CLOUDSTACK-8318: -- Summary: Storage vMotion fails in case of VMFS storage. Key: CLOUDSTACK-8318 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8318 Project:

[jira] [Commented] (CLOUDSTACK-5485) Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14267272#comment-14267272 ] Likitha Shetty commented on CLOUDSTACK-5485: With the above commit the

[jira] [Created] (CLOUDSTACK-8136) [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed.

Likitha Shetty created CLOUDSTACK-8136: -- Summary: [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. Key: CLOUDSTACK-8136 URL:

[jira] [Resolved] (CLOUDSTACK-8136) [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8136. Resolution: Fixed [VMware] Create VM snapshot fails if a previous attempt to

[jira] [Created] (CLOUDSTACK-8134) [VMware] Worker VMs don't have MS id set in the annotation.

Likitha Shetty created CLOUDSTACK-8134: -- Summary: [VMware] Worker VMs don't have MS id set in the annotation. Key: CLOUDSTACK-8134 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8134

[jira] [Updated] (CLOUDSTACK-8134) [VMware] Worker VMs don't have MS id set in vCenter annotation 'cloud.vm.workertag'.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8134: --- Summary: [VMware] Worker VMs don't have MS id set in vCenter annotation

[jira] [Resolved] (CLOUDSTACK-8134) [VMware] Worker VMs don't have MS id set in vCenter annotation 'cloud.vm.workertag'.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8134. Resolution: Fixed [VMware] Worker VMs don't have MS id set in vCenter

[jira] [Created] (CLOUDSTACK-8129) [VMware] Cold migration of VM across DCs leaves the VM behind.

Likitha Shetty created CLOUDSTACK-8129: -- Summary: [VMware] Cold migration of VM across DCs leaves the VM behind. Key: CLOUDSTACK-8129 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8129

[jira] [Updated] (CLOUDSTACK-8129) [VMware] Cold migration of VM across VMware DCs leaves the VM behind in the source host.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8129: --- Summary: [VMware] Cold migration of VM across VMware DCs leaves the VM behind in

[jira] [Resolved] (CLOUDSTACK-8129) [VMware] Cold migration of VM across VMware DCs leaves the VM behind in the source host.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8129. Resolution: Fixed +Root Cause Analysis+ This issue will only happen in case

[jira] [Created] (CLOUDSTACK-8122) NPE with root volume migration when its volume snapshot is in progress (BackingUp state)

Likitha Shetty created CLOUDSTACK-8122: -- Summary: NPE with root volume migration when its volume snapshot is in progress (BackingUp state) Key: CLOUDSTACK-8122 URL:

[jira] [Resolved] (CLOUDSTACK-8122) NPE with root volume migration when its volume snapshot is in progress (BackingUp state)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8122. Resolution: Fixed NPE with root volume migration when its volume snapshot is

[jira] [Created] (CLOUDSTACK-8123) VM re-install fails if 'vm.instancename.flag' is set to true

Likitha Shetty created CLOUDSTACK-8123: -- Summary: VM re-install fails if 'vm.instancename.flag' is set to true Key: CLOUDSTACK-8123 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8123

[jira] [Resolved] (CLOUDSTACK-8123) VM re-install fails if 'vm.instancename.flag' is set to true

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8123. Resolution: Fixed Issue - VM fails to start after the root disk has been

[jira] [Created] (CLOUDSTACK-8125) [VMware] After cold migration of a VM, VM starts with warning messages in MS logs

Likitha Shetty created CLOUDSTACK-8125: -- Summary: [VMware] After cold migration of a VM, VM starts with warning messages in MS logs Key: CLOUDSTACK-8125 URL:

[jira] [Updated] (CLOUDSTACK-8125) [VMware] After cold migration of a VM, VM starts with warning messages in MS logs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8125: --- Description: +Steps to reproduce+ 1. Deploy a vm. 2. Stop the VM. 3. Add another

[jira] [Resolved] (CLOUDSTACK-8125) [VMware] After cold migration of a VM, VM starts with warning messages in MS logs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8125. Resolution: Fixed +Root Cause Analysis+ Things to note * After VM migration,

[jira] [Created] (CLOUDSTACK-8126) [VMware] Fix cold migration across clusters

Likitha Shetty created CLOUDSTACK-8126: -- Summary: [VMware] Fix cold migration across clusters Key: CLOUDSTACK-8126 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8126 Project: CloudStack

[jira] [Resolved] (CLOUDSTACK-8126) [VMware] Fix cold migration across clusters

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8126. Resolution: Fixed [VMware] Fix cold migration across clusters

[jira] [Created] (CLOUDSTACK-8127) VM name is not displayed for an attached Datadisk.

Likitha Shetty created CLOUDSTACK-8127: -- Summary: VM name is not displayed for an attached Datadisk. Key: CLOUDSTACK-8127 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8127 Project:

[jira] [Resolved] (CLOUDSTACK-8127) VM name is not displayed for an attached Datadisk.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8127. Resolution: Fixed VM name is not displayed for an attached Datadisk.

[jira] [Created] (CLOUDSTACK-8128) [VMware] VM with Datadisk fails to start when storage is put into maintenance

Likitha Shetty created CLOUDSTACK-8128: -- Summary: [VMware] VM with Datadisk fails to start when storage is put into maintenance Key: CLOUDSTACK-8128 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8128

[jira] [Resolved] (CLOUDSTACK-8128) [VMware] VM with Datadisk fails to start when storage is put into maintenance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8128. Resolution: Fixed [VMware] VM with Datadisk fails to start when storage is

[jira] [Commented] (CLOUDSTACK-8111) NFS secondary storage repetitively mounted on MS with ESXi hypervisors

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256728#comment-14256728 ] Likitha Shetty commented on CLOUDSTACK-8111: +Verification Steps+ 1. Run

[jira] [Resolved] (CLOUDSTACK-8111) NFS secondary storage repetitively mounted on MS with ESXi hypervisors

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8111. Resolution: Fixed NFS secondary storage repetitively mounted on MS with ESXi

[jira] [Resolved] (CLOUDSTACK-8112) Creating VM using an existing display name fails when vm.instancename.flag is set to true.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8112. Resolution: Fixed During VM creation, if vm.instancename.flag is set to true

[jira] [Created] (CLOUDSTACK-8113) VM migration fails with Message: No such disk device: error

Likitha Shetty created CLOUDSTACK-8113: -- Summary: VM migration fails with Message: No such disk device: error Key: CLOUDSTACK-8113 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8113

[jira] [Resolved] (CLOUDSTACK-8113) VM migration fails with Message: No such disk device: error

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8113. Resolution: Fixed +Root Cause Analysis+ Volume migration /VM migration with

[jira] [Created] (CLOUDSTACK-8114) Stop and start of VM doesn't update volume path.

Likitha Shetty created CLOUDSTACK-8114: -- Summary: Stop and start of VM doesn't update volume path. Key: CLOUDSTACK-8114 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8114 Project:

[jira] [Resolved] (CLOUDSTACK-8114) Stop and start of VM doesn't update volume path.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8114. Resolution: Fixed Stop and start of VM doesn't update volume path.

[jira] [Created] (CLOUDSTACK-8118) Root volume migration fails with 'No such disk device' in case of vCenter 5.5 setup

Likitha Shetty created CLOUDSTACK-8118: -- Summary: Root volume migration fails with 'No such disk device' in case of vCenter 5.5 setup Key: CLOUDSTACK-8118 URL:

[jira] [Resolved] (CLOUDSTACK-8118) Root volume migration fails with 'No such disk device' in case of vCenter 5.5 setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8118. Resolution: Fixed In case of vSphere 5.5 + ESXi 5.5, CS ROOT volumes created

[jira] [Created] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

Likitha Shetty created CLOUDSTACK-8119: -- Summary: [VMware] Attaching multiple volumes to a VM is failing. Key: CLOUDSTACK-8119 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8119 Project:

[jira] [Updated] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8119: --- Description: +Steps to reproduce+ 1. Deploy a VM using default template. 2.

[jira] [Updated] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8119: --- Description: +Steps to reproduce+ 1. Deploy a VM using default template. 2.

[jira] [Resolved] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8119. Resolution: Fixed During the addition of the 9th disks, while trying to decide

[jira] [Created] (CLOUDSTACK-8120) Propagate error message to UI for attach/detach volume failure operations.

Likitha Shetty created CLOUDSTACK-8120: -- Summary: Propagate error message to UI for attach/detach volume failure operations. Key: CLOUDSTACK-8120 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8120

[jira] [Commented] (CLOUDSTACK-8120) Propagate error message to UI for attach/detach volume failure operations.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258012#comment-14258012 ] Likitha Shetty commented on CLOUDSTACK-8120: Commit

[jira] [Resolved] (CLOUDSTACK-8120) Propagate error message to UI for attach/detach volume failure operations.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8120. Resolution: Fixed Windows XP instance need to be powered off to perform

[jira] [Issue Comment Deleted] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8119: --- Comment: was deleted (was: Please ignore, this commit was meant to resolve

[jira] [Commented] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258026#comment-14258026 ] Likitha Shetty commented on CLOUDSTACK-8119: Please ignore, this commit

[jira] [Commented] (CLOUDSTACK-8119) [VMware] Attaching multiple volumes to a VM is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258027#comment-14258027 ] Likitha Shetty commented on CLOUDSTACK-8119: Please ignore, this commit

[jira] [Created] (CLOUDSTACK-8121) Creating/Deleting VM snapshots for a VM doesn't update the path and size of Data disks.

Likitha Shetty created CLOUDSTACK-8121: -- Summary: Creating/Deleting VM snapshots for a VM doesn't update the path and size of Data disks. Key: CLOUDSTACK-8121 URL:

[jira] [Resolved] (CLOUDSTACK-8121) Creating/Deleting VM snapshots for a VM doesn't update the path and size of Data disks.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8121. Resolution: Fixed Creating/Deleting VM snapshots for a VM doesn't update the

[jira] [Created] (CLOUDSTACK-8107) Failed to create snapshot from volume when the task is performed repeatedly in zone wide primary Storage.

Likitha Shetty created CLOUDSTACK-8107: -- Summary: Failed to create snapshot from volume when the task is performed repeatedly in zone wide primary Storage. Key: CLOUDSTACK-8107 URL:

[jira] [Resolved] (CLOUDSTACK-8107) Failed to create snapshot from volume when the task is performed repeatedly in zone wide primary Storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8107. Resolution: Fixed +Root Cause Analysis+ While taking snapshot of a volume, CS

[jira] [Created] (CLOUDSTACK-8108) vCenter admin name is logged in clear text with INFO level message in MS log

Likitha Shetty created CLOUDSTACK-8108: -- Summary: vCenter admin name is logged in clear text with INFO level message in MS log Key: CLOUDSTACK-8108 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8108

[jira] [Resolved] (CLOUDSTACK-8108) vCenter admin name is logged in clear text with INFO level message in MS log

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8108. Resolution: Fixed vCenter admin name is logged in clear text with INFO level

[jira] [Created] (CLOUDSTACK-8109) [VMware] Extract Template is failing.

Likitha Shetty created CLOUDSTACK-8109: -- Summary: [VMware] Extract Template is failing. Key: CLOUDSTACK-8109 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8109 Project: CloudStack

[jira] [Commented] (CLOUDSTACK-8109) [VMware] Extract Template is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256616#comment-14256616 ] Likitha Shetty commented on CLOUDSTACK-8109: When we create a private

[jira] [Resolved] (CLOUDSTACK-8109) [VMware] Extract Template is failing.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8109. Resolution: Fixed [VMware] Extract Template is failing.

[jira] [Created] (CLOUDSTACK-8110) Global config 'vm.instancename.flag' should set VM's name in vCenter to VM's DisplayName

Likitha Shetty created CLOUDSTACK-8110: -- Summary: Global config 'vm.instancename.flag' should set VM's name in vCenter to VM's DisplayName Key: CLOUDSTACK-8110 URL:

[jira] [Resolved] (CLOUDSTACK-8110) Global config 'vm.instancename.flag' should set VM's name in vCenter to VM's DisplayName

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-8110. Resolution: Fixed Global config 'vm.instancename.flag' should set VM's name

[jira] [Created] (CLOUDSTACK-8111) NFS secondary storage repetitively mounted on CCP server with ESXi hypervisors

Likitha Shetty created CLOUDSTACK-8111: -- Summary: NFS secondary storage repetitively mounted on CCP server with ESXi hypervisors Key: CLOUDSTACK-8111 URL:

[jira] [Updated] (CLOUDSTACK-8111) NFS secondary storage repetitively mounted on MS with ESXi hypervisors

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-8111: --- Summary: NFS secondary storage repetitively mounted on MS with ESXi hypervisors

[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-7759: --- Priority: Major (was: Critical) [VMWare]javax.xml.ws.soap.SOAPFaultException

[jira] [Commented] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213496#comment-14213496 ] Likitha Shetty commented on CLOUDSTACK-7759: Reducing the priority as it

[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-7759: --- Fix Version/s: (was: 4.5.0) 4.6.0

[jira] [Commented] (CLOUDSTACK-7791) [Snapshots] State transition in snapshot objects when snapshot is taken on Root/Data disk is not proper

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209362#comment-14209362 ] Likitha Shetty commented on CLOUDSTACK-7791: This is by design. In CCP,

[jira] [Resolved] (CLOUDSTACK-7791) [Snapshots] State transition in snapshot objects when snapshot is taken on Root/Data disk is not proper

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-7791. Resolution: Not a Problem [Snapshots] State transition in snapshot objects

[jira] [Resolved] (CLOUDSTACK-7651) Various operation intermittently fail in VMware with 'he object has already been deleted or has not been completely created' exceptions

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-7651. Resolution: Fixed Fixed by

[jira] [Resolved] (CLOUDSTACK-7102) Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-7102. Resolution: Fixed +Root Cause Analysis+ When global configuration

[jira] [Updated] (CLOUDSTACK-7713) Triage and fix Coverity defects

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-7713: --- Fix Version/s: (was: 4.5.0) Future Triage and fix

  1   2   3   4   5   6   >