[jira] [Assigned] (CLOUDSTACK-1001) Doc - Hyper V Support

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-1001: Assignee: Radhika Nair > Doc - Hyper V Support > - > >

[jira] [Updated] (CLOUDSTACK-4834) [Automation] Failed to create volume; failed with error "Invalid parameter diskofferingid value"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-4834: --- Assignee: (was: Gaurav Aradhye) > [Automation] Failed to create volume; fail

[jira] [Updated] (CLOUDSTACK-4835) [Automation] [BVT] Update global configuration test cases failed in master

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-4835: --- Assignee: (was: Gaurav Aradhye) > [Automation] [BVT] Update global configura

[jira] [Updated] (CLOUDSTACK-4833) [Automation][BVT] Template and ISO test cases failing from BVT suite, during LIST api call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-4833: --- Assignee: (was: Gaurav Aradhye) > [Automation][BVT] Template and ISO test ca

[jira] [Created] (CLOUDSTACK-4957) ISO/Template registration "OS Type" drop down list should be depend on hypervisor support

Shanker Balan created CLOUDSTACK-4957: - Summary: ISO/Template registration "OS Type" drop down list should be depend on hypervisor support Key: CLOUDSTACK-4957 URL: https://issues.apache.org/jira/browse/CLOUDS

[jira] [Commented] (CLOUDSTACK-4833) [Automation][BVT] Template and ISO test cases failing from BVT suite, during LIST api call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805071#comment-13805071 ] Harikrishna Patnala commented on CLOUDSTACK-4833: - CLOUDSTACK-4927 is

[jira] [Commented] (CLOUDSTACK-4927) [Automation][BVT] ISO and Template test cases failing duing listiso api call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805070#comment-13805070 ] Harikrishna Patnala commented on CLOUDSTACK-4927: - https://issues.apa

[jira] [Updated] (CLOUDSTACK-4956) CLONE - Add global configuration parameters for SMTP timeout

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-4956: --- Fix Version/s: (was: 4.2.1) 4.3.0 > CLONE - Add global co

[jira] [Created] (CLOUDSTACK-4956) CLONE - Add global configuration parameters for SMTP timeout

Anshul Gangwar created CLOUDSTACK-4956: -- Summary: CLONE - Add global configuration parameters for SMTP timeout Key: CLOUDSTACK-4956 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4956 Proj

[jira] [Comment Edited] (CLOUDSTACK-4927) [Automation][BVT] ISO and Template test cases failing duing listiso api call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805008#comment-13805008 ] Girish Shilamkar edited comment on CLOUDSTACK-4927 at 10/25/13 4:49 AM: ---

[jira] [Commented] (CLOUDSTACK-4927) [Automation][BVT] ISO and Template test cases failing duing listiso api call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805008#comment-13805008 ] Girish Shilamkar commented on CLOUDSTACK-4927: -- Hari, Could you please

[jira] [Commented] (CLOUDSTACK-4833) [Automation][BVT] Template and ISO test cases failing from BVT suite, during LIST api call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805005#comment-13805005 ] Girish Shilamkar commented on CLOUDSTACK-4833: -- This is a product issue,

[jira] [Resolved] (CLOUDSTACK-4913) Disable security group for bridge mode non-security group zone

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang resolved CLOUDSTACK-4913. Resolution: Fixed Fix Version/s: 4.3.0 Notice, this patch would only avoid enab

[jira] [Commented] (CLOUDSTACK-4913) Disable security group for bridge mode non-security group zone

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804924#comment-13804924 ] ASF subversion and git services commented on CLOUDSTACK-4913: -

[jira] [Commented] (CLOUDSTACK-4913) Disable security group for bridge mode non-security group zone

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804923#comment-13804923 ] ASF subversion and git services commented on CLOUDSTACK-4913: -

[jira] [Resolved] (CLOUDSTACK-754) nTier Apps 2.0 : Remote access VPN to VPC

[ https://issues.apache.org/jira/browse/CLOUDSTACK-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang resolved CLOUDSTACK-754. --- Resolution: Fixed > nTier Apps 2.0 : Remote access VPN to VPC > -

[jira] [Commented] (CLOUDSTACK-754) nTier Apps 2.0 : Remote access VPN to VPC

[ https://issues.apache.org/jira/browse/CLOUDSTACK-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804868#comment-13804868 ] ASF subversion and git services commented on CLOUDSTACK-754: ---

[jira] [Commented] (CLOUDSTACK-754) nTier Apps 2.0 : Remote access VPN to VPC

[ https://issues.apache.org/jira/browse/CLOUDSTACK-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804855#comment-13804855 ] ASF subversion and git services commented on CLOUDSTACK-754: ---

[jira] [Closed] (CLOUDSTACK-4955) VM security group doesn't work after vm migration on XS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu closed CLOUDSTACK-4955. -- > VM security group doesn't work after vm migration on XS > --

[jira] [Resolved] (CLOUDSTACK-4955) VM security group doesn't work after vm migration on XS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu resolved CLOUDSTACK-4955. Resolution: Duplicate > VM security group doesn't work after vm migration on XS >

[jira] [Commented] (CLOUDSTACK-4955) VM security group doesn't work after vm migration on XS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804791#comment-13804791 ] Anthony Xu commented on CLOUDSTACK-4955: duplicate with CLOUDSTACK-4624 > V

[jira] [Created] (CLOUDSTACK-4955) VM security group doesn't work after vm migration on XS

Anthony Xu created CLOUDSTACK-4955: -- Summary: VM security group doesn't work after vm migration on XS Key: CLOUDSTACK-4955 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4955 Project: CloudStac

[jira] [Comment Edited] (CLOUDSTACK-4952) [event framework] The topic grammar - eventSource.eventCategory.eventType.resourceType.resourceUuid is incorrect, eventType.resourceType should swap

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804714#comment-13804714 ] Nitin Mehta edited comment on CLOUDSTACK-4952 at 10/24/13 10:34 PM: ---

[jira] [Updated] (CLOUDSTACK-4953) VMsnapshot - Revert VM from running/stopped to a disk+memory snapshot DOES NOT result in running state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-4953: -- Attachment: management-server.log.gz > VMsnapshot - Revert VM from running/stopped

[jira] [Created] (CLOUDSTACK-4954) [event framework] In memory bus implementation required. Currently need to use Rabbit MQ

Nitin Mehta created CLOUDSTACK-4954: --- Summary: [event framework] In memory bus implementation required. Currently need to use Rabbit MQ Key: CLOUDSTACK-4954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-

[jira] [Updated] (CLOUDSTACK-4953) VMsnapshot - Revert VM from running/stopped to a disk+memory snapshot DOES NOT result in running state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-4953: -- Attachment: vm1.png > VMsnapshot - Revert VM from running/stopped to a disk+memory

[jira] [Created] (CLOUDSTACK-4953) VMsnapshot - Revert VM from running/stopped to a disk+memory snapshot DOES NOT result in running state

angeline shen created CLOUDSTACK-4953: - Summary: VMsnapshot - Revert VM from running/stopped to a disk+memory snapshot DOES NOT result in running state Key: CLOUDSTACK-4953 URL: https://issues.apache.org/jira

[jira] [Commented] (CLOUDSTACK-4952) [event framework] The topic grammar - eventSource.eventCategory.eventType.resourceType.resourceUuid is incorrect, eventType.resourceType should swap

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804714#comment-13804714 ] Nitin Mehta commented on CLOUDSTACK-4952: - Exacmple - management-server.Usag

[jira] [Created] (CLOUDSTACK-4952) [event framework] The topic grammar - eventSource.eventCategory.eventType.resourceType.resourceUuid is incorrect, eventType.resourceType should swap

Nitin Mehta created CLOUDSTACK-4952: --- Summary: [event framework] The topic grammar - eventSource.eventCategory.eventType.resourceType.resourceUuid is incorrect, eventType.resourceType should swap Key: CLOUDSTACK-4952

[jira] [Updated] (CLOUDSTACK-4951) [event framework] Action events do not have UUID

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4951: Summary: [event framework] Action events do not have UUID (was: Action events do not

[jira] [Created] (CLOUDSTACK-4951) Action events do not have UUID

Nitin Mehta created CLOUDSTACK-4951: --- Summary: Action events do not have UUID Key: CLOUDSTACK-4951 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4951 Project: CloudStack Issue Type

[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804693#comment-13804693 ] ASF subversion and git services commented on CLOUDSTACK-4649: -

[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804691#comment-13804691 ] ASF subversion and git services commented on CLOUDSTACK-4649: -

[jira] [Resolved] (CLOUDSTACK-4846) Http connection error in marvin

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-4846. - Resolution: Fixed > Http connection error in marvin > --

[jira] [Closed] (CLOUDSTACK-4846) Http connection error in marvin

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-4846. --- > Http connection error in marvin > ---

[jira] [Commented] (CLOUDSTACK-4846) Http connection error in marvin

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804623#comment-13804623 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-4846: - I tested t

[jira] [Comment Edited] (CLOUDSTACK-4939) Failed to create snaphot (KVM, GFS2)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804407#comment-13804407 ] Ivan Kozlov edited comment on CLOUDSTACK-4939 at 10/24/13 7:15 PM:

[jira] [Commented] (CLOUDSTACK-4948) DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804548#comment-13804548 ] Prachi Damle commented on CLOUDSTACK-4948: -- Koushik, This is about the case

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

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

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

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804526#comment-13804526 ] ASF subversion and git services commented on CLOUDSTACK-4950: -

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

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804523#comment-13804523 ] ASF subversion and git services commented on CLOUDSTACK-4950: -

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

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

[jira] [Updated] (CLOUDSTACK-4949) UI > Instance Wizard > Step 4 > correct label from "Data Disk Offering" to "Disk Offering" since selected disk offering here refers to root disk volume when selected

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-4949: - Fix Version/s: 4.3.0 > UI > Instance Wizard > Step 4 > correct label from "Data Disk

[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804509#comment-13804509 ] ASF subversion and git services commented on CLOUDSTACK-4649: -

[jira] [Commented] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine API call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804508#comment-13804508 ] ASF subversion and git services commented on CLOUDSTACK-4505: -

[jira] [Resolved] (CLOUDSTACK-4949) UI > Instance Wizard > Step 4 > correct label from "Data Disk Offering" to "Disk Offering" since selected disk offering here refers to root disk volume when selecte

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-4949. -- Resolution: Fixed Author: Jessica Wang #mailto:jessicaw...@apache.org Aut

[jira] [Closed] (CLOUDSTACK-4949) UI > Instance Wizard > Step 4 > correct label from "Data Disk Offering" to "Disk Offering" since selected disk offering here refers to root disk volume when selected

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-4949. > UI > Instance Wizard > Step 4 > correct label from "Data Disk Offering" to > "Disk Offe

[jira] [Commented] (CLOUDSTACK-4948) DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804493#comment-13804493 ] Koushik Das commented on CLOUDSTACK-4948: - This should be fixed by commit 624

[jira] [Commented] (CLOUDSTACK-4913) Disable security group for bridge mode non-security group zone

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804495#comment-13804495 ] Sheng Yang commented on CLOUDSTACK-4913: Patch ready. In testing. > Disable

[jira] [Created] (CLOUDSTACK-4949) UI > Instance Wizard > Step 4 > correct label from "Data Disk Offering" to "Disk Offering" since selected disk offering here refers to root disk volume when selected

Jessica Wang created CLOUDSTACK-4949: Summary: UI > Instance Wizard > Step 4 > correct label from "Data Disk Offering" to "Disk Offering" since selected disk offering here refers to root disk volume when selected template is of ISO format, da

[jira] [Commented] (CLOUDSTACK-1049) provide a way to extract commit sha1 from packages generated on jenkins

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804469#comment-13804469 ] ASF subversion and git services commented on CLOUDSTACK-1049: -

[jira] [Created] (CLOUDSTACK-4948) DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage

Prachi Damle created CLOUDSTACK-4948: Summary: DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage Key: CLOUDSTACK-4948 URL: https:

[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804454#comment-13804454 ] ASF subversion and git services commented on CLOUDSTACK-4649: -

[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804423#comment-13804423 ] ASF subversion and git services commented on CLOUDSTACK-4649: -

[jira] [Updated] (CLOUDSTACK-4939) Failed to create snaphot (KVM, GFS2)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kozlov updated CLOUDSTACK-4939: Fix Version/s: 4.2.1 > Failed to create snaphot (KVM, GFS2) >

[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804412#comment-13804412 ] Alena Prokharchyk commented on CLOUDSTACK-4649: --- When resource detail i

[jira] [Commented] (CLOUDSTACK-4939) Failed to create snaphot (KVM, GFS2)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804407#comment-13804407 ] Ivan Kozlov commented on CLOUDSTACK-4939: - I have checked this with ocfs2 and

[jira] [Updated] (CLOUDSTACK-4939) Failed to create snaphot (KVM, GFS2)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kozlov updated CLOUDSTACK-4939: Affects Version/s: 4.2.1 > Failed to create snaphot (KVM, GFS2) >

[jira] [Reopened] (CLOUDSTACK-4691) [Automation] test case test_egress_after_host_maintainance need to move to host maintainance suite

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan reopened CLOUDSTACK-4691: - same test not removed from integration folder > [Automation] test case

[jira] [Commented] (CLOUDSTACK-4909) Add global configuration parameters for SMTP timeout

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804264#comment-13804264 ] ASF subversion and git services commented on CLOUDSTACK-4909: -

[jira] [Resolved] (CLOUDSTACK-4885) [Automation] Test starting and ending timestamp should be looged

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-4885. - Resolution: Fixed The issue is fixed. > [Automation] Test s

[jira] [Closed] (CLOUDSTACK-4885) [Automation] Test starting and ending timestamp should be looged

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-4885. --- > [Automation] Test starting and ending timestamp should be looged

[jira] [Created] (CLOUDSTACK-4947) if apply.allocation.algorithm.to.pods is set to true VM creationFails.

Bharat Kumar created CLOUDSTACK-4947: Summary: if apply.allocation.algorithm.to.pods is set to true VM creationFails. Key: CLOUDSTACK-4947 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4947

[jira] [Created] (CLOUDSTACK-4946) Restore VM with template id feature doesnt work on VMware

Likitha Shetty created CLOUDSTACK-4946: -- Summary: Restore VM with template id feature doesnt work on VMware Key: CLOUDSTACK-4946 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4946 Project:

[jira] [Updated] (CLOUDSTACK-4943) Can't create cluster in CS 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Finko updated CLOUDSTACK-4943: Priority: Critical (was: Major) > Can't create cluster in CS 4.2 > --

[jira] [Closed] (CLOUDSTACK-4862) Admin cannot delete shared network scoped to user account.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal closed CLOUDSTACK-4862. -- Verified on 4.2.1 build . Passed > Admin cannot delete shared network scoped to user

[jira] [Commented] (CLOUDSTACK-4540) Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails to get deployed due to "VmDataCommand failed due to Exception: java.lang.Exception Mes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804100#comment-13804100 ] shweta agarwal commented on CLOUDSTACK-4540: on latest 4.2.1 setup also h

[jira] [Closed] (CLOUDSTACK-4935) Adding same network to VM multiple times resulting in failure, No new NIC is generated each time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal closed CLOUDSTACK-4935. -- > Adding same network to VM multiple times resulting in failure, No new NIC is > gene

[jira] [Resolved] (CLOUDSTACK-4935) Adding same network to VM multiple times resulting in failure, No new NIC is generated each time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal resolved CLOUDSTACK-4935. Resolution: Invalid adding same network to VM is not supported . Test case nee

[jira] [Comment Edited] (CLOUDSTACK-4943) Can't create cluster in CS 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804077#comment-13804077 ] Denis Finko edited comment on CLOUDSTACK-4943 at 10/24/13 11:19 AM: ---

[jira] [Commented] (CLOUDSTACK-4943) Can't create cluster in CS 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804077#comment-13804077 ] Denis Finko commented on CLOUDSTACK-4943: - Ryan, thank you for your advice! I

[jira] [Updated] (CLOUDSTACK-4909) Add global configuration parameters for SMTP timeout

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-4909: --- Fix Version/s: 4.2.1 > Add global configuration parameters for SMTP timeout > --

[jira] [Commented] (CLOUDSTACK-3715) Live Migration of Virtual instances operation is getting timedout

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804053#comment-13804053 ] Likitha Shetty commented on CLOUDSTACK-3715: We see socket timeout in a V

[jira] [Updated] (CLOUDSTACK-4918) VR can not be LB service provider without requiring to be source nat service provider as well.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-4918: --- Assignee: Murali Reddy > VR can not be LB service provider without requi

[jira] [Created] (CLOUDSTACK-4945) [Doc] Pluggable VM Snapshot

Radhika Nair created CLOUDSTACK-4945: Summary: [Doc] Pluggable VM Snapshot Key: CLOUDSTACK-4945 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4945 Project: CloudStack Issue Type:

[jira] [Resolved] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine API call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-4505. -- Resolution: Fixed Fix Version/s: (was: Future) 4.3.0 > expun

[jira] [Commented] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine API call

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804027#comment-13804027 ] ASF subversion and git services commented on CLOUDSTACK-4505: -

[jira] [Commented] (CLOUDSTACK-4885) [Automation] Test starting and ending timestamp should be looged

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804014#comment-13804014 ] Santhosh Kumar Edukulla commented on CLOUDSTACK-4885: - 1. Apart f

[jira] [Commented] (CLOUDSTACK-4885) [Automation] Test starting and ending timestamp should be looged

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804005#comment-13804005 ] ASF subversion and git services commented on CLOUDSTACK-4885: -

[jira] [Created] (CLOUDSTACK-4944) Command sequence logic in agent code may lead to errors in clustered MS setup

Koushik Das created CLOUDSTACK-4944: --- Summary: Command sequence logic in agent code may lead to errors in clustered MS setup Key: CLOUDSTACK-4944 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4944

[jira] [Commented] (CLOUDSTACK-4936) System VM's Agent goes to disconnected state but VM state still up when they are stopped manually.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803979#comment-13803979 ] Koushik Das commented on CLOUDSTACK-4936: - Yes. Issue is same as CLOUDSTACK-4

[jira] [Resolved] (CLOUDSTACK-4936) System VM's Agent goes to disconnected state but VM state still up when they are stopped manually.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4936. - Resolution: Cannot Reproduce Fixed in latest build by fix for CLOUDSTACK-4937 > Sys

[jira] [Commented] (CLOUDSTACK-4922) Vmware :agent is not up in system VM using 64 bit system VM templates

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803966#comment-13803966 ] Sateesh Chodapuneedi commented on CLOUDSTACK-4922: -- Uploaded the 64b

[jira] [Commented] (CLOUDSTACK-4943) Can't create cluster in CS 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803963#comment-13803963 ] Ryan Lei commented on CLOUDSTACK-4943: -- I'm encountering the same problem using

[jira] [Commented] (CLOUDSTACK-4936) System VM's Agent goes to disconnected state but VM state still up when they are stopped manually.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803950#comment-13803950 ] Wei Zhou commented on CLOUDSTACK-4936: -- This may be same to CLOUDSTACK-4937 > S

[jira] [Created] (CLOUDSTACK-4943) Can't create cluster in CS 4.2

Denis Finko created CLOUDSTACK-4943: --- Summary: Can't create cluster in CS 4.2 Key: CLOUDSTACK-4943 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4943 Project: CloudStack Issue Type: