[jira] [Resolved] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-2670. --- Resolution: Fixed > [Object_Store_Refactor] UI/API: migrate volume does not

[jira] [Assigned] (CLOUDSTACK-3893) Remove Hyperv option from Zone and Cluster configuration screen hypervisors dropdown list

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3893: - Assignee: Devdeep Singh > Remove Hyperv option from Zone and Cluster con

[jira] [Resolved] (CLOUDSTACK-3893) Remove Hyperv option from Zone and Cluster configuration screen hypervisors dropdown list

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3893. --- Resolution: Fixed > Remove Hyperv option from Zone and Cluster configuration

[jira] [Assigned] (CLOUDSTACK-4268) ASF 4.1 to 4.2 Upgrade: Guest OS Category of "Other Ubuntu 32bit" is different on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-4268: - Assignee: Devdeep Singh (was: Sanjay Tripathi) > ASF 4.1 to 4.2 Upgrade

[jira] [Resolved] (CLOUDSTACK-4268) ASF 4.1 to 4.2 Upgrade: Guest OS Category of "Other Ubuntu 32bit" is different on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4268. --- Resolution: Fixed > ASF 4.1 to 4.2 Upgrade: Guest OS Category of "Other Ubun

[jira] [Updated] (CLOUDSTACK-1236) Warning while adding Xen 6.1 host [Unable to create local link network]

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-1236: -- Priority: Major (was: Minor) > Warning while adding Xen 6.1 host [Unable to c

[jira] [Resolved] (CLOUDSTACK-4268) ASF 4.1 to 4.2 Upgrade: Guest OS Category of "Other Ubuntu 32bit" is different on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4268. --- Resolution: Fixed Checked it against the latest build. In a fresh 4.2 setup too

[jira] [Commented] (CLOUDSTACK-4257) [Automation] test_storage_motion test cases failed during with unexpected result in listStoragePool API call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739599#comment-13739599 ] Devdeep Singh commented on CLOUDSTACK-4257: --- The test requires that there a

[jira] [Assigned] (CLOUDSTACK-4372) [XenServer] Commands info which are executed via xenserver are not logged in SMlog

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-4372: - Assignee: Devdeep Singh > [XenServer] Commands info which are executed v

[jira] [Updated] (CLOUDSTACK-4372) [XenServer] Commands info which are executed via xenserver are not logged in SMlog

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-4372: -- Description: ll Any command info wich CS executes via xenserver is supposed to be

[jira] [Commented] (CLOUDSTACK-4372) [XenServer] Commands info which are executed via xenserver are not logged in SMlog

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743177#comment-13743177 ] Devdeep Singh commented on CLOUDSTACK-4372: --- I looked at the setup on which

[jira] [Resolved] (CLOUDSTACK-4372) [XenServer] Commands info which are executed via xenserver are not logged in SMlog

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4372. --- Resolution: Cannot Reproduce Looked at the setup on which the problem was report

[jira] [Commented] (CLOUDSTACK-4397) Failed to create instance with "Implicit Dedication planner" even when empty host is found

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743720#comment-13743720 ] Devdeep Singh commented on CLOUDSTACK-4397: --- Can you share details about yo

[jira] [Assigned] (CLOUDSTACK-4397) Failed to create instance with "Implicit Dedication planner" even when empty host is found

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-4397: - Assignee: Devdeep Singh > Failed to create instance with "Implicit Dedic

[jira] [Resolved] (CLOUDSTACK-4397) Failed to create instance with "Implicit Dedication planner" even when empty host is found

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4397. --- Resolution: Invalid System vms (SSVM and console proxy vm) are not ignored by th

[jira] [Resolved] (CLOUDSTACK-4449) Possibility of /tmp/xapilog filling up the Root disk on Xenserver

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4449. --- Resolution: Duplicate Looks like 2 bugs got created for the same issue.

[jira] [Assigned] (CLOUDSTACK-4470) findHostsForMigration API is not setting 'requiresStorageMotion' flag wrongly

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-4470: - Assignee: Devdeep Singh > findHostsForMigration API is not setting 'requ

[jira] [Resolved] (CLOUDSTACK-4470) findHostsForMigration API is not setting 'requiresStorageMotion' flag wrongly

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4470. --- Resolution: Fixed > findHostsForMigration API is not setting 'requiresStorag

[jira] [Commented] (CLOUDSTACK-3992) create template from volume is failiing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726052#comment-13726052 ] Devdeep Singh commented on CLOUDSTACK-3992: --- It looks like /bin/vhd-util is

[jira] [Commented] (CLOUDSTACK-3992) create template from volume is failiing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726123#comment-13726123 ] Devdeep Singh commented on CLOUDSTACK-3992: --- I tried it with a clean setup

[jira] [Assigned] (CLOUDSTACK-4009) [Upgrade] [2.2.16 to 4.2] "healthcheck.update.interval" global config missing after upgrade

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-4009: - Assignee: Devdeep Singh > [Upgrade] [2.2.16 to 4.2] "healthcheck.update.

[jira] [Resolved] (CLOUDSTACK-4009) [Upgrade] [2.2.16 to 4.2] "healthcheck.update.interval" global config missing after upgrade

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4009. --- Resolution: Fixed > [Upgrade] [2.2.16 to 4.2] "healthcheck.update.interval"

[jira] [Assigned] (CLOUDSTACK-4079) UPGRADE: storage_motion_supported field is not updated for xenserver6.1 in hypervisor_capabilities table after upgrade

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-4079: - Assignee: Devdeep Singh > UPGRADE: storage_motion_supported field is not

[jira] [Resolved] (CLOUDSTACK-4079) UPGRADE: storage_motion_supported field is not updated for xenserver6.1 in hypervisor_capabilities table after upgrade

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-4079. --- Resolution: Fixed > UPGRADE: storage_motion_supported field is not updated f

[jira] [Assigned] (CLOUDSTACK-2188) Parsing error with Download Monitor while checking the health of downloaded templates

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-2188: - Assignee: Devdeep Singh (was: Sanjay Tripathi) > Parsing error with Dow

[jira] [Resolved] (CLOUDSTACK-3774) [XenServer]NPE while creating template from snapshot on a upgraded setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3774. --- Resolution: Fixed > [XenServer]NPE while creating template from snapshot on

[jira] [Resolved] (CLOUDSTACK-2188) Parsing error with Download Monitor while checking the health of downloaded templates

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-2188. --- Resolution: Fixed Fixed in commit 41f7820709f8856a93473818f13093c6dd6dd7ca and

[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733266#comment-13733266 ] Devdeep Singh commented on CLOUDSTACK-2670: --- Looking at the issue. Right no

[jira] [Commented] (CLOUDSTACK-4179) [Performance Testing] Time taken for Deploy VM async job to complete is considerably higher

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733493#comment-13733493 ] Devdeep Singh commented on CLOUDSTACK-4179: --- The for loops are unnecessary.

[jira] [Commented] (CLOUDSTACK-4179) [Performance Testing] Time taken for Deploy VM async job to complete is considerably higher

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733504#comment-13733504 ] Devdeep Singh commented on CLOUDSTACK-4179: --- Hi Koushik, I have updated th

[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734427#comment-13734427 ] Devdeep Singh commented on CLOUDSTACK-2670: --- The bug should be fixed for 4.

[jira] [Updated] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-2670: -- Priority: Critical (was: Major) > [Object_Store_Refactor] UI/API: migrate vol

[jira] [Assigned] (CLOUDSTACK-3552) Domain/Account details are not displayed for the implicitly dedicated hosts neither in UI nor in DB.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3552: - Assignee: Devdeep Singh > Domain/Account details are not displayed for t

[jira] [Resolved] (CLOUDSTACK-3552) Domain/Account details are not displayed for the implicitly dedicated hosts neither in UI nor in DB.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3552. --- Resolution: Won't Fix op_host_planner_reservation table is meant for internal ho

[jira] [Assigned] (CLOUDSTACK-3630) [Storage]No option for migration of local data volume.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3630: - Assignee: Devdeep Singh > [Storage]No option for migration of local data

[jira] [Resolved] (CLOUDSTACK-3630) [Storage]No option for migration of local data volume.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3630. --- Resolution: Invalid When a data disk is created, user chooses the disk offering

[jira] [Created] (CLOUDSTACK-3661) Keep getting IndexOutOfBoundException in the connect process to the secondary storage vm

Devdeep Singh created CLOUDSTACK-3661: - Summary: Keep getting IndexOutOfBoundException in the connect process to the secondary storage vm Key: CLOUDSTACK-3661 URL: https://issues.apache.org/jira/browse/CLOUDST

[jira] [Assigned] (CLOUDSTACK-3622) Built-in template download failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3622: - Assignee: Devdeep Singh (was: Alex Huang) > Built-in template download

[jira] [Resolved] (CLOUDSTACK-3622) Built-in template download failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3622. --- Resolution: Fixed Fixed in commit bd54fa13a3bf864474d7875f1fcffd32e6914beb. Didn

[jira] [Comment Edited] (CLOUDSTACK-3622) Built-in template download failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713421#comment-13713421 ] Devdeep Singh edited comment on CLOUDSTACK-3622 at 7/19/13 7:43 AM: ---

[jira] [Closed] (CLOUDSTACK-3661) Keep getting IndexOutOfBoundException in the connect process to the secondary storage vm

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh closed CLOUDSTACK-3661. - > Keep getting IndexOutOfBoundException in the connect process to the secondary > s

[jira] [Commented] (CLOUDSTACK-3708) [Regression] Migration of volume from one storage pool to another isn't working

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715066#comment-13715066 ] Devdeep Singh commented on CLOUDSTACK-3708: --- The regression seems to be cau

[jira] [Created] (CLOUDSTACK-3708) [Regression] Migration of volume from one storage pool to another isn't working

Devdeep Singh created CLOUDSTACK-3708: - Summary: [Regression] Migration of volume from one storage pool to another isn't working Key: CLOUDSTACK-3708 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3708

[jira] [Commented] (CLOUDSTACK-3708) [Regression] Migration of volume from one storage pool to another isn't working

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715159#comment-13715159 ] Devdeep Singh commented on CLOUDSTACK-3708: --- Fix is ready. The asf server i

[jira] [Resolved] (CLOUDSTACK-3708) [Regression] Migration of volume from one storage pool to another isn't working

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3708. --- Resolution: Fixed > [Regression] Migration of volume from one storage pool t

[jira] [Commented] (CLOUDSTACK-3774) [XenServer]NPE while creating template from snapshot on a upgraded setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718305#comment-13718305 ] Devdeep Singh commented on CLOUDSTACK-3774: --- Can you look into the secondar

[jira] [Commented] (CLOUDSTACK-3502) CloudStack will not allow migration of volumes of stopped VMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718327#comment-13718327 ] Devdeep Singh commented on CLOUDSTACK-3502: --- Will address it is as a fix fo

[jira] [Resolved] (CLOUDSTACK-3502) CloudStack will not allow migration of volumes of stopped VMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3502. --- Resolution: Duplicate Issue is a duplicate of CLOUDSTACK-2670 >

[jira] [Resolved] (CLOUDSTACK-2768) [SXM] snapshot on a migrated volume is getting NULL path

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-2768. --- Resolution: Cannot Reproduce I tried it multiple times with the latest 4.2 branc

[jira] [Commented] (CLOUDSTACK-2821) [XenServer] ModifyStoragePoolCommand fails with error "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e62

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719472#comment-13719472 ] Devdeep Singh commented on CLOUDSTACK-2821: --- Cloudstack doesn't allow addin

[jira] [Updated] (CLOUDSTACK-2821) [XenServer] ModifyStoragePoolCommand fails with error "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e6216

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-2821: -- Fix Version/s: (was: 4.2.0) Future > [XenServer] Modify

[jira] [Resolved] (CLOUDSTACK-3590) Adding new Xen server host to cluster fails in first attempt - Need to add the host again

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3590. --- Resolution: Fixed > Adding new Xen server host to cluster fails in first att

[jira] [Commented] (CLOUDSTACK-2821) [XenServer] ModifyStoragePoolCommand fails with error "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e62

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720455#comment-13720455 ] Devdeep Singh commented on CLOUDSTACK-2821: --- We need to implement the abili

[jira] [Updated] (CLOUDSTACK-2821) [XenServer] ModifyStoragePoolCommand fails with error "com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e6216

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-2821: -- Issue Type: Improvement (was: Bug) > [XenServer] ModifyStoragePoolCommand fai

[jira] [Updated] (CLOUDSTACK-3501) Cannot create instances on XenServer with multiple cores per socket

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-3501: -- Priority: Critical (was: Major) > Cannot create instances on XenServer with m

[jira] [Resolved] (CLOUDSTACK-3501) Cannot create instances on XenServer with multiple cores per socket

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3501. --- Resolution: Fixed > Cannot create instances on XenServer with multiple cores

[jira] [Resolved] (CLOUDSTACK-3774) [XenServer]NPE while creating template from snapshot on a upgraded setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3774. --- Resolution: Cannot Reproduce Tried it against an upgraded setup and we weren't a

[jira] [Resolved] (CLOUDSTACK-3875) Snapshots which are created from volume are not deleted from secondary storage when Volume is deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3875. --- Resolution: Invalid Assignee: Devdeep Singh (was: Kishan Kavala) > Sn

[jira] [Commented] (CLOUDSTACK-3875) Snapshots which are created from volume are not deleted from secondary storage when Volume is deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722205#comment-13722205 ] Devdeep Singh commented on CLOUDSTACK-3875: --- This is an expected behavior.

[jira] [Assigned] (CLOUDSTACK-3890) xenserver, when deleted the storagePool storage is not getting deleted from xenserver.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3890: - Assignee: Devdeep Singh > xenserver, when deleted the storagePool stora

[jira] [Resolved] (CLOUDSTACK-3890) xenserver, when deleted the storagePool storage is not getting deleted from xenserver.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3890. --- Resolution: Fixed > xenserver, when deleted the storagePool storage is not

[jira] [Commented] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support

[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802849#comment-13802849 ] Devdeep Singh commented on CLOUDSTACK-999: -- Update on the what is being targe

[jira] [Comment Edited] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support

[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802849#comment-13802849 ] Devdeep Singh edited comment on CLOUDSTACK-999 at 10/23/13 12:34 PM: ---

[jira] [Comment Edited] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support

[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802849#comment-13802849 ] Devdeep Singh edited comment on CLOUDSTACK-999 at 10/23/13 12:38 PM: ---

[jira] [Updated] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support

[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-999: - Description: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+2012+%283

[jira] [Assigned] (CLOUDSTACK-5217) [Hyper-V] Attach volume command fails with NPE

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5217: - Assignee: Devdeep Singh > [Hyper-V] Attach volume command fails with NPE > -

[jira] [Commented] (CLOUDSTACK-5249) [Hyper-V] System VMs fail to launch, throws NPE while trying create VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831282#comment-13831282 ] Devdeep Singh commented on CLOUDSTACK-5249: --- The hyperv agent needs to be u

[jira] [Assigned] (CLOUDSTACK-5304) Hyper-V] Creation of a VM on shared primary storage is failing with "network path not found"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5304: - Assignee: Devdeep Singh > Hyper-V] Creation of a VM on shared primary storag

[jira] [Commented] (CLOUDSTACK-5304) Hyper-V] Creation of a VM on shared primary storage is failing with "network path not found"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837729#comment-13837729 ] Devdeep Singh commented on CLOUDSTACK-5304: --- Fixed in commit 80a5dd75cdaaab

[jira] [Resolved] (CLOUDSTACK-5304) Hyper-V] Creation of a VM on shared primary storage is failing with "network path not found"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5304. --- Resolution: Fixed > Hyper-V] Creation of a VM on shared primary storage is faili

[jira] [Resolved] (CLOUDSTACK-5178) [Hyper-V] Deploy VM from ISO fails with "Unsupported Command"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5178. --- Resolution: Fixed > [Hyper-V] Deploy VM from ISO fails with "Unsupported Command

[jira] [Resolved] (CLOUDSTACK-5362) [Hyper-v] System vms does not come up with CIFS as the shared primary storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5362. --- Resolution: Invalid The host is in domain1 and the smb share is under domain2. T

[jira] [Updated] (CLOUDSTACK-5210) Need Support for the Hyper-V for the Report sockets CS-4908

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5210: -- Priority: Critical (was: Blocker) > Need Support for the Hyper-V for the Report s

[jira] [Updated] (CLOUDSTACK-5210) Need Support for the Hyper-V for the Report sockets

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5210: -- Summary: Need Support for the Hyper-V for the Report sockets (was: Need Support f

[jira] [Updated] (CLOUDSTACK-5210) Need Support for the Hyper-V for the Report sockets

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5210: -- Affects Version/s: 4.3.0 > Need Support for the Hyper-V for the Report sockets > -

[jira] [Commented] (CLOUDSTACK-5210) Need Support for the Hyper-V for the Report sockets

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840027#comment-13840027 ] Devdeep Singh commented on CLOUDSTACK-5210: --- This is a new thing that needs

[jira] [Assigned] (CLOUDSTACK-3281) StartCommand carries VolumeObjectTO with format field of NULL

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3281: - Assignee: Devdeep Singh > StartCommand carries VolumeObjectTO with format fi

[jira] [Resolved] (CLOUDSTACK-3281) StartCommand carries VolumeObjectTO with format field of NULL

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3281. --- Resolution: Not A Problem If the format field isn't given, agent code tries to g

[jira] [Assigned] (CLOUDSTACK-5339) VHDX file type not recognised by CloudStack

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5339: - Assignee: Devdeep Singh (was: Rajesh Battala) > VHDX file type not recognis

[jira] [Resolved] (CLOUDSTACK-5339) VHDX file type not recognised by CloudStack

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5339. --- Resolution: Fixed > VHDX file type not recognised by CloudStack > --

[jira] [Updated] (CLOUDSTACK-5412) Zone Creation Wizard mislabels CIFS Server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5412: -- Assignee: (was: Devdeep Singh) > Zone Creation Wizard mislabels CIFS Server >

[jira] [Resolved] (CLOUDSTACK-5202) [Hyper-V] Too many mount points created for secondary storage in management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5202. --- Resolution: Fixed > [Hyper-V] Too many mount points created for secondary storag

[jira] [Assigned] (CLOUDSTACK-5202) [Hyper-V] Too many mount points created for secondary storage in management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5202: - Assignee: Devdeep Singh > [Hyper-V] Too many mount points created for second

[jira] [Resolved] (CLOUDSTACK-5248) [Hyper-V] Failure to create mount point for secondary storage as cloud user, system VMs fail to come up

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5248. --- Resolution: Fixed > [Hyper-V] Failure to create mount point for secondary storag

[jira] [Resolved] (CLOUDSTACK-5275) [Hyper-V] Adding host requires an agent restart to be performed for successful addition

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5275. --- Resolution: Fixed > [Hyper-V] Adding host requires an agent restart to be perfor

[jira] [Updated] (CLOUDSTACK-5415) SMB/cifs path should tell user to start with slash

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5415: -- Affects Version/s: 4.3.0 > SMB/cifs path should tell user to start with slash > --

[jira] [Updated] (CLOUDSTACK-5415) SMB/cifs path should tell user to start with slash

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5415: -- Fix Version/s: 4.3.0 > SMB/cifs path should tell user to start with slash > --

[jira] [Resolved] (CLOUDSTACK-5415) SMB/cifs path should tell user to start with slash

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5415. --- Resolution: Won't Fix The user is expected the begin the path with '/'. The beha

[jira] [Resolved] (CLOUDSTACK-5455) [Hyper-V] Detach ISO from VM is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5455. --- Resolution: Fixed > [Hyper-V] Detach ISO from VM is failing > --

[jira] [Assigned] (CLOUDSTACK-5455) [Hyper-V] Detach ISO from VM is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5455: - Assignee: Devdeep Singh > [Hyper-V] Detach ISO from VM is failing >

[jira] [Created] (CLOUDSTACK-5473) Hyper-v agent service name needs to be fixed

Devdeep Singh created CLOUDSTACK-5473: - Summary: Hyper-v agent service name needs to be fixed Key: CLOUDSTACK-5473 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5473 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-5473) Hyper-v agent service name needs to be fixed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh updated CLOUDSTACK-5473: -- Labels: hyper-V, (was: ) > Hyper-v agent service name needs to be fixed > ---

[jira] [Resolved] (CLOUDSTACK-5473) Hyper-v agent service name needs to be fixed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5473. --- Resolution: Fixed > Hyper-v agent service name needs to be fixed > -

[jira] [Resolved] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5462. --- Resolution: Fixed Reviewed and pushed the changes by Donal > Hyper-V Agent conf

[jira] [Resolved] (CLOUDSTACK-5311) [Hyper-V] Global settings missing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5311. --- Resolution: Fixed > [Hyper-V] Global settings missing >

[jira] [Assigned] (CLOUDSTACK-5439) CloudStack does not deal with existing Hyper-V System VMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5439: - Assignee: Devdeep Singh > CloudStack does not deal with existing Hyper-V Sys

[jira] [Resolved] (CLOUDSTACK-5439) CloudStack does not deal with existing Hyper-V System VMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5439. --- Resolution: Won't Fix It is expected that when a new hyperv host is added to cle

[jira] [Assigned] (CLOUDSTACK-5489) [Hyper-V] Cloud user doesn't have permissions to create systemvm folder, due to which systemvm creation fails

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5489: - Assignee: Devdeep Singh > [Hyper-V] Cloud user doesn't have permissions to c

[jira] [Resolved] (CLOUDSTACK-5489) [Hyper-V] Cloud user doesn't have permissions to create systemvm folder, due to which systemvm creation fails

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5489. --- Resolution: Fixed > [Hyper-V] Cloud user doesn't have permissions to create syst

[jira] [Commented] (CLOUDSTACK-4356) [Automation] TestImplicitPlanner test case failed to deploy VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762763#comment-13762763 ] Devdeep Singh commented on CLOUDSTACK-4356: --- Explicit and implicit dedicati

  1   2   3   4   >