[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=14256726#comment-14256726 ] ASF subversion and git services commented on CLOUDSTACK-8111:

[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] [Commented] (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:comment-tabpanelfocusedCommentId=14256740#comment-14256740 ] ASF subversion and git services commented on CLOUDSTACK-8112:

[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] [Commented] (CLOUDSTACK-7769) [Automation] Fix the script test_ssvm.py - SSVM Gateway Assertion is not valid in EIP-ELB case

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256752#comment-14256752 ] ASF subversion and git services commented on CLOUDSTACK-7769:

[jira] [Commented] (CLOUDSTACK-8096) [Automation] Fix failures in smoke/test_ssvm.py (reboot ssvm and cpvm test cases)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256753#comment-14256753 ] ASF subversion and git services commented on CLOUDSTACK-8096:

[jira] [Commented] (CLOUDSTACK-8096) [Automation] Fix failures in smoke/test_ssvm.py (reboot ssvm and cpvm test cases)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256755#comment-14256755 ] ASF subversion and git services commented on CLOUDSTACK-8096:

[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] [Commented] (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:comment-tabpanelfocusedCommentId=14256758#comment-14256758 ] ASF subversion and git services commented on 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] [Commented] (CLOUDSTACK-8098) [Automation] Fix smoke/test_vm_snapshots.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256772#comment-14256772 ] ASF subversion and git services commented on CLOUDSTACK-8098:

[jira] [Commented] (CLOUDSTACK-7762) [Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256771#comment-14256771 ] ASF subversion and git services commented on CLOUDSTACK-7762:

[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] [Commented] (CLOUDSTACK-8098) [Automation] Fix smoke/test_vm_snapshots.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256782#comment-14256782 ] ASF subversion and git services commented on CLOUDSTACK-8098:

[jira] [Commented] (CLOUDSTACK-7762) [Automation] - Fix test failure for test_02_revert_vm_snapshots in smoke/test_vm_snapshots.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256780#comment-14256780 ] ASF subversion and git services commented on CLOUDSTACK-7762:

[jira] [Commented] (CLOUDSTACK-8099) [Automation] Fix test_dynamic_compute_offering.py - unittest is not defined

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256783#comment-14256783 ] ASF subversion and git services commented on CLOUDSTACK-8099:

[jira] [Commented] (CLOUDSTACK-8099) [Automation] Fix test_dynamic_compute_offering.py - unittest is not defined

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256786#comment-14256786 ] ASF subversion and git services commented on CLOUDSTACK-8099:

[jira] [Commented] (CLOUDSTACK-7788) [Automation][Simulator] Fix the script test_dynamic_compute_offering.py - Test Cases failing on Simulator due to hardware resources requirement for test executio

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256785#comment-14256785 ] ASF subversion and git services commented on CLOUDSTACK-7788:

[jira] [Closed] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland closed CLOUDSTACK-5511. - Resolution: Fixed Please delete old releases from mirroring system

[jira] [Resolved] (CLOUDSTACK-7527) XenServer heartbeat-script: make it reboot faster (when fencing)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland resolved CLOUDSTACK-7527. --- Resolution: Fixed XenServer heartbeat-script: make it reboot faster (when

[jira] [Updated] (CLOUDSTACK-7781) Typo in calling /opt/cloud/bin/createipAlias.sh

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-7781: -- Fix Version/s: (was: 4.4.3) 4.4.2 Typo in calling

[jira] [Resolved] (CLOUDSTACK-7781) Typo in calling /opt/cloud/bin/createipAlias.sh

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland resolved CLOUDSTACK-7781. --- Resolution: Fixed please verify Typo in calling

[jira] [Updated] (CLOUDSTACK-7702) keytool not in sudoers file

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-7702: -- Fix Version/s: (was: 4.4.3) 4.4.1 keytool not in sudoers

[jira] [Resolved] (CLOUDSTACK-7702) keytool not in sudoers file

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland resolved CLOUDSTACK-7702. --- Resolution: Fixed keytool not in sudoers file ---

[jira] [Updated] (CLOUDSTACK-6485) [vpc] new private gateway network is registered wrong in network table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6485: -- Fix Version/s: 4.6.0 [vpc] new private gateway network is registered wrong in

[jira] [Updated] (CLOUDSTACK-6485) [vpc] new private gateway network is registered wrong in network table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6485: -- Fix Version/s: (was: 4.6.0) [vpc] new private gateway network is registered

[jira] [Resolved] (CLOUDSTACK-6485) [vpc] new private gateway network is registered wrong in network table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland resolved CLOUDSTACK-6485. --- Resolution: Fixed this hack will have to be acceptable for now. Private Gateway

[jira] [Reopened] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened CLOUDSTACK-5511: -- Please now delete 4.3.2. By the way, 4.3.2 does not appear on either the current download page or the

[jira] [Updated] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-5511: -- Assignee: Rohit Yadav (was: Daan Hoogland) Please delete old releases from

[jira] [Created] (CLOUDSTACK-8115) Update default ordering of HA investigators

Koushik Das created CLOUDSTACK-8115: --- Summary: Update default ordering of HA investigators Key: CLOUDSTACK-8115 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8115 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-8115) Update default ordering of HA investigators

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-8115: Description: The PingInvestigator goes through all other hosts in a pod to determine

[jira] [Commented] (CLOUDSTACK-8115) Update default ordering of HA investigators

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256841#comment-14256841 ] ASF subversion and git services commented on CLOUDSTACK-8115:

[jira] [Resolved] (CLOUDSTACK-8115) Update default ordering of HA investigators

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-8115. - Resolution: Fixed Update default ordering of HA investigators

[jira] [Commented] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256843#comment-14256843 ] Rohit Yadav commented on CLOUDSTACK-5511: - [~s...@apache.org] the 4.3.2

[jira] [Commented] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256849#comment-14256849 ] Sebb commented on CLOUDSTACK-5511: -- Sorry, did not notice that it was a recent

[jira] [Created] (CLOUDSTACK-8116) Move ldap config data to configurableData section in test_data.py and make related changes in the test case

Gaurav Aradhye created CLOUDSTACK-8116: -- Summary: Move ldap config data to configurableData section in test_data.py and make related changes in the test case Key: CLOUDSTACK-8116 URL:

[jira] [Closed] (CLOUDSTACK-4587) VM is failing to deploy on a Legacy zone after adding zone wide primary storage and moving cluster wide primary storage to maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-4587. After moving the cluster scoped primary storages into maintenance

[jira] [Commented] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256936#comment-14256936 ] Rohit Yadav commented on CLOUDSTACK-5511: - Thanks for the pointers. I'll add

[jira] [Closed] (CLOUDSTACK-5511) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav closed CLOUDSTACK-5511. --- Resolution: Fixed Closing since 4.3.2 is a new release, we should put it on

[jira] [Created] (CLOUDSTACK-8117) Increase the allowed margin (+/-) for memory of VM on hyperv used to equate with the memory specified in service offering

Gaurav Aradhye created CLOUDSTACK-8117: -- Summary: Increase the allowed margin (+/-) for memory of VM on hyperv used to equate with the memory specified in service offering Key: CLOUDSTACK-8117 URL:

[jira] [Commented] (CLOUDSTACK-7781) Typo in calling /opt/cloud/bin/createipAlias.sh

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256991#comment-14256991 ] Nux commented on CLOUDSTACK-7781: - The issue seemed fixed the last time I tried,

[jira] [Commented] (CLOUDSTACK-8103) Vmsync marks VM as stopped even after failing to stop it in HV

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257056#comment-14257056 ] ASF subversion and git services commented on CLOUDSTACK-8103:

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14257077#comment-14257077 ] ASF subversion and git services commented on CLOUDSTACK-8107:

[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=14257086#comment-14257086 ] ASF subversion and git services commented on CLOUDSTACK-8109:

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14257514#comment-14257514 ] ASF subversion and git services commented on CLOUDSTACK-8112:

[jira] [Updated] (CLOUDSTACK-8103) Vmsync marks VM as stopped even after failing to stop it in HV

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-8103: -- Fix Version/s: 4.4.3 Vmsync marks VM as stopped even after failing to stop it in

[jira] [Updated] (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 ] Daan Hoogland updated CLOUDSTACK-8107: -- Fix Version/s: (was: Future) 4.4.3 Failed to create

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

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-8109: -- Fix Version/s: (was: Future) 4.4.3 [VMware] Extract

[jira] [Updated] (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 ] Daan Hoogland updated CLOUDSTACK-8112: -- Fix Version/s: (was: Future) 4.4.3 Creating VM using an

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14257947#comment-14257947 ] ASF subversion and git services commented on CLOUDSTACK-8114:

[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] [Commented] (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:comment-tabpanelfocusedCommentId=14257969#comment-14257969 ] ASF subversion and git services commented on CLOUDSTACK-8118:

[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] [Commented] (CLOUDSTACK-8117) Increase the allowed margin (+/-) for memory of VM on hyperv used to equate with the memory specified in service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257976#comment-14257976 ] ASF subversion and git services commented on CLOUDSTACK-8117:

[jira] [Commented] (CLOUDSTACK-8116) Move ldap config data to configurableData section in test_data.py and make related changes in the test case

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257977#comment-14257977 ] ASF subversion and git services commented on CLOUDSTACK-8116:

[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=14257980#comment-14257980 ] ASF subversion and git services commented on CLOUDSTACK-8119:

[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] [Commented] (CLOUDSTACK-8117) Increase the allowed margin (+/-) for memory of VM on hyperv used to equate with the memory specified in service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257990#comment-14257990 ] ASF subversion and git services commented on CLOUDSTACK-8117:

[jira] [Commented] (CLOUDSTACK-8116) Move ldap config data to configurableData section in test_data.py and make related changes in the test case

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257989#comment-14257989 ] ASF subversion and git services commented on CLOUDSTACK-8116:

[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-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=14258008#comment-14258008 ] ASF subversion and git services commented on CLOUDSTACK-8119:

[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] [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=14258024#comment-14258024 ] ASF subversion and git services commented on CLOUDSTACK-8119:

[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] [Commented] (CLOUDSTACK-6463) password is not set for VMs created from password enabled template

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258061#comment-14258061 ] Andrija Panic commented on CLOUDSTACK-6463: --- Interesting stuff here - for

[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] [Commented] (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:comment-tabpanelfocusedCommentId=14258081#comment-14258081 ] ASF subversion and git services commented on CLOUDSTACK-8121:

[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