[jira] [Updated] (CLOUDSTACK-6407) NPE while collecting VM statistics

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6407: - Fix Version/s: 4.4.0 NPE while collecting VM statistics

[jira] [Commented] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969199#comment-13969199 ] Sailaja Mada commented on CLOUDSTACK-6382: -- This issue is fixed with below

[jira] [Commented] (CLOUDSTACK-6407) NPE while collecting VM statistics

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969226#comment-13969226 ] Sailaja Mada commented on CLOUDSTACK-6407: -- 2014-04-15 10:18:17,788 DEBUG

[jira] [Created] (CLOUDSTACK-6386) DB Exceptions while starting the Management server first time

Sailaja Mada created CLOUDSTACK-6386: Summary: DB Exceptions while starting the Management server first time Key: CLOUDSTACK-6386 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6386

[jira] [Updated] (CLOUDSTACK-6386) DB Exceptions while starting the Management server first time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6386: - Attachment: management-server.log DB Exceptions while starting the Management

[jira] [Updated] (CLOUDSTACK-6386) DB Exceptions while starting the Management server first time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6386: - Fix Version/s: 4.4.0 DB Exceptions while starting the Management server first time

[jira] [Created] (CLOUDSTACK-6372) [UI]Incorrect Field name while adding Primary Storage (*label.path)

Sailaja Mada created CLOUDSTACK-6372: Summary: [UI]Incorrect Field name while adding Primary Storage (*label.path) Key: CLOUDSTACK-6372 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6372

[jira] [Updated] (CLOUDSTACK-6372) [UI]Incorrect Field name while adding Primary Storage (*label.path)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6372: - Attachment: addPSsnap.png [UI]Incorrect Field name while adding Primary Storage

[jira] [Updated] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6382: - Fix Version/s: 4.4.0 System VM's failing to start with XenServer 6.2.5

[jira] [Created] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5

Sailaja Mada created CLOUDSTACK-6382: Summary: System VM's failing to start with XenServer 6.2.5 Key: CLOUDSTACK-6382 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6382 Project: CloudStack

[jira] [Closed] (CLOUDSTACK-4445) [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter with Chrome Browser

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4445. This is not observed now. Hence closing the bug. [UI]Edit Icon is used for Dedicate

[jira] [Closed] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-1889. This is displayed with update Resource count and hence closing the bug. Instance

[jira] [Closed] (CLOUDSTACK-3266) [UI] Failed to delete Anti affinitygroup for the first time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-3266. This is not observed now. Hence closing the bug. [UI] Failed to delete Anti

[jira] [Created] (CLOUDSTACK-5359) Failed to add second VMWARE cluster on a standard vSwitch enabled zone when vCenter details are passed in the addCluster wizard

Sailaja Mada created CLOUDSTACK-5359: Summary: Failed to add second VMWARE cluster on a standard vSwitch enabled zone when vCenter details are passed in the addCluster wizard Key: CLOUDSTACK-5359 URL:

[jira] [Updated] (CLOUDSTACK-5359) Failed to add second VMWARE cluster on a standard vSwitch enabled zone when vCenter details are passed in the addCluster wizard

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5359: - Fix Version/s: 4.3.0 Failed to add second VMWARE cluster on a standard vSwitch

[jira] [Closed] (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:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-3715. I tried with latest builds. Live Migration worked only when i have a VM with 1

[jira] [Reopened] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance on a mixed storage setup(Cluster and Zone wide) and when Cluster wide primary storage is moved to maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-5027: -- This is valid issue . But there is an issue filed for the similar reason @

[jira] [Resolved] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance on a mixed storage setup(Cluster and Zone wide) and when Cluster wide primary storage is moved to maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada resolved CLOUDSTACK-5027. -- Resolution: Duplicate [VMWARE] Failed to Deploy instance on a mixed storage

[jira] [Closed] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance on a mixed storage setup(Cluster and Zone wide) and when Cluster wide primary storage is moved to maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-5027. Closing the duplicate issue as its tracked @ CLOUDSTACK-4587 [VMWARE] Failed to Deploy

[jira] [Updated] (CLOUDSTACK-5016) Failed to reboot the VM which has VM Snapshots and Migrated Volumes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5016: - Attachment: alllogs.rar Failed to reboot the VM which has VM Snapshots and

[jira] [Updated] (CLOUDSTACK-5142) Guest IP address for F5 is not being selected from the defined IP Range in Shared Network

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5142: - Fix Version/s: 4.2.1 Guest IP address for F5 is not being selected from the

[jira] [Created] (CLOUDSTACK-5142) Guest IP address for F5 is not being selected from the defined IP Range in Shared Network

Sailaja Mada created CLOUDSTACK-5142: Summary: Guest IP address for F5 is not being selected from the defined IP Range in Shared Network Key: CLOUDSTACK-5142 URL:

[jira] [Updated] (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 ] Sailaja Mada updated CLOUDSTACK-4587: - Attachment: logs.rar VM is failing to deploy on a Legacy zone after adding zone

[jira] [Updated] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance on a mixed storage setup(Cluster and Zone wide) and when Cluster wide primary storage is moved to maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5027: - Summary: [VMWARE] Failed to Deploy instance on a mixed storage setup(Cluster and

[jira] [Updated] (CLOUDSTACK-5104) [VMWARE]Support to Clone a Virtual Machine instance from a running Instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5104: - Attachment: cloneVM.png [VMWARE]Support to Clone a Virtual Machine instance from a

[jira] [Reopened] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance when primary storage of a different zone are in maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-5027: -- Hi, This issue was consistent in my setup when it was reported. I have attached

[jira] [Updated] (CLOUDSTACK-5098) [VMWARE] Entries in vmware_data_center and vmware_data_center_zone_map are not cleaned up when there is a failure to add the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5098: - Description: Steps: 1. Enable Nexus flag at the global level 2. Tried to

[jira] [Created] (CLOUDSTACK-5098) [VMWARE] Entries in vmware_data_center and vmware_data_center_zone_map are not cleaned up when there is a failure to add the cluster

Sailaja Mada created CLOUDSTACK-5098: Summary: [VMWARE] Entries in vmware_data_center and vmware_data_center_zone_map are not cleaned up when there is a failure to add the cluster Key: CLOUDSTACK-5098 URL:

[jira] [Updated] (CLOUDSTACK-5098) [VMWARE] Entries in vmware_data_center and vmware_data_center_zone_map are not cleaned up when there is a failure to add the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5098: - Description: Steps: 1. Enable Nexus flag at the global level 2. Tried to

[jira] [Updated] (CLOUDSTACK-5098) [VMWARE] Entries in vmware_data_center and vmware_data_center_zone_map are not cleaned up when there is a failure to add the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5098: - Fix Version/s: 4.2.1 [VMWARE] Entries in vmware_data_center and

[jira] [Updated] (CLOUDSTACK-5098) [VMWARE] Entries in vmware_data_center and vmware_data_center_zone_map are not cleaned up when there is a failure to add the cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5098: - Attachment: management-server.log apilog.log [VMWARE] Entries in

[jira] [Closed] (CLOUDSTACK-5068) [VMWARE]Failed to deploy VM with NPE while copying the template from Secondary to Primary storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-5068. Assignee: Likitha Shetty (was: Sateesh Chodapuneedi) This is fixed now. Hence

[jira] [Closed] (CLOUDSTACK-4964) Cisco VNMC: Nexus password gets logged in MS logs during guest n/w implementation with VNMC provider

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4964. This is fixed now.Hence closing the bug. 2013-11-06 22:58:01,102 DEBUG

[jira] [Created] (CLOUDSTACK-5068) [VMWARE]Failed to deploy VM with NPE while copying the template from Secondary to Primary storage

Sailaja Mada created CLOUDSTACK-5068: Summary: [VMWARE]Failed to deploy VM with NPE while copying the template from Secondary to Primary storage Key: CLOUDSTACK-5068 URL:

[jira] [Updated] (CLOUDSTACK-5068) [VMWARE]Failed to deploy VM with NPE while copying the template from Secondary to Primary storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5068: - Fix Version/s: 4.2.1 [VMWARE]Failed to deploy VM with NPE while copying the

[jira] [Updated] (CLOUDSTACK-5068) [VMWARE]Failed to deploy VM with NPE while copying the template from Secondary to Primary storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5068: - Attachment: failuretodeploy.rar [VMWARE]Failed to deploy VM with NPE while copying

[jira] [Commented] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13814597#comment-13814597 ] Sailaja Mada commented on CLOUDSTACK-4907: -- When account is deleted then the

[jira] [Updated] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4907: - Fix Version/s: (was: 4.3.0) 4.2.1 [VMWARE]Volume Snapshot

[jira] [Commented] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13814599#comment-13814599 ] Sailaja Mada commented on CLOUDSTACK-4907: -- Hence moving back to 4.2.1 to

[jira] [Updated] (CLOUDSTACK-5028) Instance is failing to start after releasing the primary storage from maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5028: - Fix Version/s: 4.2.1 Instance is failing to start after releasing the primary

[jira] [Updated] (CLOUDSTACK-5028) Instance is failing to start after releasing the primary storage from maintenance mode

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5028: - Attachment: startvmlogs.rar Instance is failing to start after releasing the

[jira] [Closed] (CLOUDSTACK-4717) associate IP does not work on shared networks with out source NAT service

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4717. This is fixed now. Hence closing the bug. associate IP does not work on shared networks

[jira] [Updated] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5030: - Fix Version/s: 4.2.1 [Doc] Document the Procedure to create custom role in vCenter

[jira] [Created] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform

Sailaja Mada created CLOUDSTACK-5030: Summary: [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform Key: CLOUDSTACK-5030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5030

[jira] [Updated] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5030: - Labels: doc (was: ) [Doc] Document the Procedure to create custom role in vCenter

[jira] [Created] (CLOUDSTACK-5027) [VMWARE] Failed to Deploy instance when primary storage of a different zone are in maintenance mode

Sailaja Mada created CLOUDSTACK-5027: Summary: [VMWARE] Failed to Deploy instance when primary storage of a different zone are in maintenance mode Key: CLOUDSTACK-5027 URL:

[jira] [Created] (CLOUDSTACK-5016) Failed to reboot the VM which has VM Snapshots and Migrated Volumes

Sailaja Mada created CLOUDSTACK-5016: Summary: Failed to reboot the VM which has VM Snapshots and Migrated Volumes Key: CLOUDSTACK-5016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5016

[jira] [Updated] (CLOUDSTACK-5016) Failed to reboot the VM which has VM Snapshots and Migrated Volumes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5016: - Fix Version/s: 4.2.1 Failed to reboot the VM which has VM Snapshots and Migrated

[jira] [Updated] (CLOUDSTACK-5016) Failed to reboot the VM which has VM Snapshots and Migrated Volumes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5016: - Attachment: startvm.png Failed to reboot the VM which has VM Snapshots and

[jira] [Updated] (CLOUDSTACK-5016) Failed to reboot the VM which has VM Snapshots and Migrated Volumes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5016: - Attachment: logsall.rar Failed to reboot the VM which has VM Snapshots and

[jira] [Created] (CLOUDSTACK-5000) UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod

Sailaja Mada created CLOUDSTACK-5000: Summary: UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod Key: CLOUDSTACK-5000 URL:

[jira] [Updated] (CLOUDSTACK-5000) UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5000: - Attachment: NoAddPrimarySscreen.png UI does not invoke a screen to add second

[jira] [Updated] (CLOUDSTACK-5000) UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5000: - Fix Version/s: 4.2.1 UI does not invoke a screen to add second Primary storage if

[jira] [Updated] (CLOUDSTACK-5000) UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5000: - Attachment: alllogs.rar UI does not invoke a screen to add second Primary storage

[jira] [Created] (CLOUDSTACK-5001) Cluster details are not getting displayed after completing the Add cluster Task

Sailaja Mada created CLOUDSTACK-5001: Summary: Cluster details are not getting displayed after completing the Add cluster Task Key: CLOUDSTACK-5001 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5001

[jira] [Updated] (CLOUDSTACK-5001) Cluster details are not getting displayed after completing the Add cluster Task

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5001: - Fix Version/s: 4.2.1 Cluster details are not getting displayed after completing

[jira] [Updated] (CLOUDSTACK-5001) Cluster details are not getting displayed after completing the Add cluster Task

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5001: - Attachment: alllogs.rar errorsnap1.png Cluster details are not

[jira] [Created] (CLOUDSTACK-5008) [VMWARE]Failed to start the VM after performing Cold Migration of Volume to Second Zone wide primary Storage

Sailaja Mada created CLOUDSTACK-5008: Summary: [VMWARE]Failed to start the VM after performing Cold Migration of Volume to Second Zone wide primary Storage Key: CLOUDSTACK-5008 URL:

[jira] [Updated] (CLOUDSTACK-5008) [VMWARE]Failed to start the VM after performing Cold Migration of Volume to Second Zone wide primary Storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5008: - Fix Version/s: 4.2.1 [VMWARE]Failed to start the VM after performing Cold

[jira] [Updated] (CLOUDSTACK-5008) [VMWARE]Failed to start the VM after performing Cold Migration of Volume to Second Zone wide primary Storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5008: - Attachment: migrationlogs.rar [VMWARE]Failed to start the VM after performing Cold

[jira] [Updated] (CLOUDSTACK-4594) [VMWARE] [Upgrade] Failed to revert VM Snapshot which were created before Live Storage Migrating the VM to other Cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4594: - Description: Upgraded setup : 307 Setup with 2 clusters ( Cluster1 – 2 ESXi 5.0

[jira] [Commented] (CLOUDSTACK-4594) [VMWARE] [Upgrade] Failed to revert VM Snapshot which were created before Live Storage Migrating the VM to other Cluster

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809930#comment-13809930 ] Sailaja Mada commented on CLOUDSTACK-4594: -- Both the clusters would have had

[jira] [Closed] (CLOUDSTACK-3583) Management server stop is not removing the PID

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-3583. This issue is fixed now. Hence closing the bug. [root@rhelASA management]# service

[jira] [Created] (CLOUDSTACK-4975) NPE while deleting the volume

Sailaja Mada created CLOUDSTACK-4975: Summary: NPE while deleting the volume Key: CLOUDSTACK-4975 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4975 Project: CloudStack Issue

[jira] [Updated] (CLOUDSTACK-4975) NPE while deleting the volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4975: - Attachment: newlogs.rar NPE while deleting the volume

[jira] [Updated] (CLOUDSTACK-4975) NPE while deleting the volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4975: - Fix Version/s: 4.2.1 NPE while deleting the volume -

[jira] [Commented] (CLOUDSTACK-4717) associate IP does not work on shared networks with out source NAT service

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801535#comment-13801535 ] Sailaja Mada commented on CLOUDSTACK-4717: -- Thanks Murali. Do you want to

[jira] [Closed] (CLOUDSTACK-3873) No error notification is generated when Primary storage (Cluster level) is added with wrong path

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-3873. This is fixed. But there is an issue with with status message. That is tracked as a

[jira] [Reopened] (CLOUDSTACK-2412) [UI]Disable CiscoVnmc provider for PF/SourceNat/StaticNAT/Firewall dropdown list with Shared guest type and VPC Network Offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-2412: -- Hi Jessica, For both the options. It is supported only with isolated guest networks.

[jira] [Closed] (CLOUDSTACK-4584) [VMWARE]System VM's failed to start if nexus is enabled at cloud level before upgrade but all the VMWARE clusters are with Standard vSwitch

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4584. Agree with it. Hence closing the bug. [VMWARE]System VM's failed to start if nexus is

[jira] [Created] (CLOUDSTACK-4905) [VMWARE]System Vm's are failing to start with permission issue while unpacking the OVA file

Sailaja Mada created CLOUDSTACK-4905: Summary: [VMWARE]System Vm's are failing to start with permission issue while unpacking the OVA file Key: CLOUDSTACK-4905 URL:

[jira] [Updated] (CLOUDSTACK-4905) [VMWARE]System Vm's are failing to start with permission issue while unpacking the OVA file

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4905: - Attachment: logs.rar [VMWARE]System Vm's are failing to start with permission

[jira] [Updated] (CLOUDSTACK-4905) [VMWARE]System Vm's are failing to start with permission issue while unpacking the OVA file

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4905: - Fix Version/s: 4.2.1 [VMWARE]System Vm's are failing to start with permission

[jira] [Closed] (CLOUDSTACK-4905) [VMWARE]System Vm's are failing to start with permission issue while unpacking the OVA file

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4905. Resolution: Invalid Secondary storage was seeded with wrong template. After seeding

[jira] [Assigned] (CLOUDSTACK-3994) Wrong error notification is generated when Primary storage (Cluster wide) is added with wrong path

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reassigned CLOUDSTACK-3994: Assignee: Sailaja Mada Wrong error notification is generated when Primary

[jira] [Reopened] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-1889: -- This is not fixed yet. I could see only Total VM, Bytes Received and Sent. I can

[jira] [Updated] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-1889: - Attachment: ConsumedresourcesUSage.png [UI] Consumed Resource usage details are

[jira] [Updated] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-1889: - Attachment: new.rar [UI] Consumed Resource usage details are not available for all

[jira] [Closed] (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 ] Sailaja Mada closed CLOUDSTACK-1236. This issue is fixed now. Hence closing the bug. Warning while adding Xen 6.1 host

[jira] [Created] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

Sailaja Mada created CLOUDSTACK-4907: Summary: [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot Key: CLOUDSTACK-4907 URL:

[jira] [Updated] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4907: - Attachment: issue.rar [VMWARE]Volume Snapshot Entries are not deleted from DB when

[jira] [Updated] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4907: - Fix Version/s: 4.2.1 [VMWARE]Volume Snapshot Entries are not deleted from DB when

[jira] [Commented] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13800526#comment-13800526 ] Sailaja Mada commented on CLOUDSTACK-4907: -- 2013-10-21 15:47:10,919 DEBUG

[jira] [Closed] (CLOUDSTACK-3418) Failed to update snapshot state with NPE while creating the snpashot when Primary Storage is in Prepare Maintanance state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-3418. Regressed with latest builds. There is no NPE observed now. But we are leaving failed

[jira] [Reopened] (CLOUDSTACK-2414) NPE while deleting Cisco VNMC provider

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-2414: -- I do not agree this defect being wont fix. Even though operation is successful, It

[jira] [Updated] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4907: - Attachment: listsnaps.png [VMWARE]Volume Snapshot Entries are not deleted from DB

[jira] [Reopened] (CLOUDSTACK-4717) associate IP does not work on shared networks with out source NAT service

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-4717: -- Tried to create shared network offering with LB,DNS,DHCP services / It failed to

[jira] [Commented] (CLOUDSTACK-4847) UI Error Failed to delete storage pool on host

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791582#comment-13791582 ] Sailaja Mada commented on CLOUDSTACK-4847: -- We have the similar defect

[jira] [Reopened] (CLOUDSTACK-3715) Live Migration of Virtual instances operation is getting timedout on a multinode mgmt setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-3715: -- Issue is happening even on a single node Management server: Hence reopening the

[jira] [Updated] (CLOUDSTACK-3715) Live Migration of Virtual instances operation is getting timedout on a multinode mgmt setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3715: - Priority: Critical (was: Blocker) Live Migration of Virtual instances

[jira] [Updated] (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:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3715: - Summary: Live Migration of Virtual instances operation is getting timedout (was:

[jira] [Updated] (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:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3715: - Attachment: migrationlogs.rar Live Migration of Virtual instances operation is

[jira] [Updated] (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:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3715: - Component/s: VMware Live Migration of Virtual instances operation is getting

[jira] [Updated] (CLOUDSTACK-4680) [UI] Provide an option to perform Assign VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4680: - Fix Version/s: 4.2.1 [UI] Provide an option to perform Assign VM

[jira] [Created] (CLOUDSTACK-4680) [UI] Provide an option to perform Assign VM

Sailaja Mada created CLOUDSTACK-4680: Summary: [UI] Provide an option to perform Assign VM Key: CLOUDSTACK-4680 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4680 Project: CloudStack

[jira] [Closed] (CLOUDSTACK-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4089. Fixed now. Hence closing the ticket. Provide a drop down to specify

[jira] [Closed] (CLOUDSTACK-4664) [ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4664. This is fixed now. Hence closing the ticket. [ZWPS] High delay to

[jira] [Resolved] (CLOUDSTACK-4663) [VMWARE][ZWPS]Failed to start one of the VM if two stopped VM's are started in parallel

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada resolved CLOUDSTACK-4663. -- Resolution: Fixed Assignee: Prachi Damle This issue got fixed with below

[jira] [Updated] (CLOUDSTACK-4664) [ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4664: - Fix Version/s: 4.2.1 [ZWPS] High delay to start a stopped VM which has

[jira] [Closed] (CLOUDSTACK-4663) [VMWARE][ZWPS]Failed to start one of the VM if two stopped VM's are started in parallel

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4663. This issue is fixed now. Hence closing the ticket.

<    1   2   3   4   5   6   7   8   9   >