[jira] [Resolved] (CLOUDSTACK-8181) Overprovisioning hosts happens when using first fit allocator + high disable threshold

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-8181. - Resolution: Fixed > Overprovisioning hosts happens when using first fit allocator + h

[jira] [Created] (CLOUDSTACK-8181) Overprovisioning hosts happens when using first fit allocator + high disable threshold

Nitin Mehta created CLOUDSTACK-8181: --- Summary: Overprovisioning hosts happens when using first fit allocator + high disable threshold Key: CLOUDSTACK-8181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-81

[jira] [Updated] (CLOUDSTACK-8181) Overprovisioning hosts happens when using first fit allocator + high disable threshold

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-8181: Description: 1) In the host allocator, under a given cluster, we list all the hosts whi

[jira] [Assigned] (CLOUDSTACK-8181) Overprovisioning hosts happens when using first fit allocator + high disable threshold

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta reassigned CLOUDSTACK-8181: --- Assignee: Nitin Mehta > Overprovisioning hosts happens when using first fit allo

[jira] [Commented] (CLOUDSTACK-7920) NPE in Volume sync causing ssvm agent to not connect

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283011#comment-14283011 ] Nitin Mehta commented on CLOUDSTACK-7920: - [~bhaisaab] I dont think it is ver

[jira] [Updated] (CLOUDSTACK-6658) Unknown parameters...ctxdetails seen in the logs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6658: Summary: Unknown parameters...ctxdetails seen in the logs (was: Unknown parameters...c

[jira] [Updated] (CLOUDSTACK-6658) Unknown parameters...ctxsdetails seen in the logs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6658: Summary: Unknown parameters...ctxsdetails seen in the logs (was: Unknown parameters...

[jira] [Comment Edited] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266396#comment-14266396 ] Nitin Mehta edited comment on CLOUDSTACK-6772 at 1/6/15 5:02 PM: --

[jira] [Commented] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266396#comment-14266396 ] Nitin Mehta commented on CLOUDSTACK-6772: - We dont have the capability in the

[jira] [Commented] (CLOUDSTACK-2919) Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Secondary Storage locations

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232655#comment-14232655 ] Nitin Mehta commented on CLOUDSTACK-2919: - Unfortunately, I havent been able

[jira] [Commented] (CLOUDSTACK-5997) Template state changes side affects

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231017#comment-14231017 ] Nitin Mehta commented on CLOUDSTACK-5997: - [~bhaisaab] I was on leave so coul

[jira] [Resolved] (CLOUDSTACK-7920) NPE in Volume sync causing ssvm agent to not connect

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7920. - Resolution: Fixed > NPE in Volume sync causing ssvm agent to not connect > -

[jira] [Created] (CLOUDSTACK-7920) NPE in Volume sync causing ssvm agent to not connect

Nitin Mehta created CLOUDSTACK-7920: --- Summary: NPE in Volume sync causing ssvm agent to not connect Key: CLOUDSTACK-7920 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7920 Project: CloudStac

[jira] [Resolved] (CLOUDSTACK-7919) In vmware, when host crashed and the VR migrated because of HA, Vmsync didnt notice a change in the state and so didnt reprogram the VR

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7919. - Resolution: Fixed > In vmware, when host crashed and the VR migrated because of HA, V

[jira] [Updated] (CLOUDSTACK-7919) In vmware, when host crashed and the VR migrated because of HA, Vmsync didnt notice a change in the state and so didnt reprogram the VR

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7919: Summary: In vmware, when host crashed and the VR migrated because of HA, Vmsync didnt n

[jira] [Created] (CLOUDSTACK-7919) In vmware, when host crashed and the VR migrated because of HA Vmsync couldnt notice a change in the state (logs pasted above by me) and so didnt reprogram the VR

Nitin Mehta created CLOUDSTACK-7919: --- Summary: In vmware, when host crashed and the VR migrated because of HA Vmsync couldnt notice a change in the state (logs pasted above by me) and so didnt reprogram the VR Key: CLOUDSTACK-7

[jira] [Resolved] (CLOUDSTACK-7916) Generate Alerts if System VMs cannot be started

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7916. - Resolution: Fixed > Generate Alerts if System VMs cannot be started > ---

[jira] [Updated] (CLOUDSTACK-6698) listResourceDetals - normal user able to list details not belonging to it

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6698: Fix Version/s: (was: 4.5.0) 4.6.0 > listResourceDetals - normal

[jira] [Commented] (CLOUDSTACK-6698) listResourceDetals - normal user able to list details not belonging to it

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212818#comment-14212818 ] Nitin Mehta commented on CLOUDSTACK-6698: - Punting for 4.6 since this seem to

[jira] [Commented] (CLOUDSTACK-7916) Generate Alerts if System VMs cannot be started

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212737#comment-14212737 ] Nitin Mehta commented on CLOUDSTACK-7916: - If CPVM or SSVM cannot be started

[jira] [Created] (CLOUDSTACK-7916) Generate Alerts if System VMs cannot be started

Nitin Mehta created CLOUDSTACK-7916: --- Summary: Generate Alerts if System VMs cannot be started Key: CLOUDSTACK-7916 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7916 Project: CloudStack

[jira] [Resolved] (CLOUDSTACK-7909) Enabling the cluster from disabled state is changing the capacity_state to enabled even for disabled hosts in op_host_capacity table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7909. - Resolution: Fixed > Enabling the cluster from disabled state is changing the capacity

[jira] [Updated] (CLOUDSTACK-7909) Enabling the cluster from disabled state is changing the capacity_state to enabled even for disabled hosts in op_host_capacity table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7909: Description: steps: 1. Deployed CS with 1 zone,1pod,1 cluster and 2 hosts host1 and ho

[jira] [Created] (CLOUDSTACK-7909) Enabling the cluster from disabled state is changing the capacity_state to enabled even for disabled hosts in op_host_capacity table

Nitin Mehta created CLOUDSTACK-7909: --- Summary: Enabling the cluster from disabled state is changing the capacity_state to enabled even for disabled hosts in op_host_capacity table Key: CLOUDSTACK-7909 URL: http

[jira] [Resolved] (CLOUDSTACK-7870) When Vm deployments fail and end in error state volume count should be decremented

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7870. - Resolution: Fixed > When Vm deployments fail and end in error state volume count shou

[jira] [Created] (CLOUDSTACK-7870) When Vm deployments fail and end in error state volume count should be decremented

Nitin Mehta created CLOUDSTACK-7870: --- Summary: When Vm deployments fail and end in error state volume count should be decremented Key: CLOUDSTACK-7870 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7870

[jira] [Commented] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197199#comment-14197199 ] Nitin Mehta commented on CLOUDSTACK-6772: - We can log it but cant say the pri

[jira] [Resolved] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6772. - Resolution: Won't Fix > [UI]need to change popup message fo Attach volume failure "

[jira] [Updated] (CLOUDSTACK-2112) VM went in stopped state after live migration failed while vmscaleup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2112: Fix Version/s: (was: 4.4.0) Future > VM went in stopped state af

[jira] [Updated] (CLOUDSTACK-3658) [DB Upgrade] - Deprecate several old object storage tables and columns as a part of 41-42 db upgrade

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-3658: Fix Version/s: (was: 4.5.0) 4.6.0 > [DB Upgrade] - Deprecate sev

[jira] [Updated] (CLOUDSTACK-7289) Bugs seen when declaring a class variable as native type (long) and have its getter method returning the corresponding object (Long) and vice versa

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7289: Fix Version/s: (was: 4.5.0) 4.6.0 > Bugs seen when declaring a c

[jira] [Updated] (CLOUDSTACK-7290) VO classes shouldn¹t have any class variables declared as native type

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7290: Fix Version/s: (was: 4.5.0) 4.6.0 > VO classes shouldn¹t have an

[jira] [Resolved] (CLOUDSTACK-7825) Volume Snapshot - Incorrect size in usage_event table when snapshot is created- Volume's virtual size is reported instead of the actual snapshot's size.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7825. - Resolution: Fixed > Volume Snapshot - Incorrect size in usage_event table when snapsh

[jira] [Updated] (CLOUDSTACK-7825) Volume Snapshot - Incorrect size in usage_event table when snapshot is created- Volume's virtual size is reported instead of the actual snapshot's size.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7825: Priority: Critical (was: Major) > Volume Snapshot - Incorrect size in usage_event tabl

[jira] [Updated] (CLOUDSTACK-7825) Volume Snapshot - Incorrect size in usage_event table when snapshot is created- Volume's virtual size is reported instead of the actual snapshot's size.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7825: Affects Version/s: 4.5.0 > Volume Snapshot - Incorrect size in usage_event table when s

[jira] [Created] (CLOUDSTACK-7825) Volume Snapshot - Incorrect size in usage_event table when snapshot is created- Volume's virtual size is reported instead of the actual snapshot's size.

Nitin Mehta created CLOUDSTACK-7825: --- Summary: Volume Snapshot - Incorrect size in usage_event table when snapshot is created- Volume's virtual size is reported instead of the actual snapshot's size. Key: CLOUDSTACK-7825

[jira] [Resolved] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7820. - Resolution: Fixed > Don't consider disabled hosts for calculating disable threshold.

[jira] [Updated] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7820: Priority: Critical (was: Major) > Don't consider disabled hosts for calculating disabl

[jira] [Updated] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7820: Fix Version/s: (was: 4.6.0) 4.5.0 > Don't consider disabled host

[jira] [Updated] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7820: Description: Don't consider disabled hosts for calculating disable threshold. Disabled

[jira] [Updated] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7820: Affects Version/s: 4.5.0 > Don't consider disabled hosts for calculating disable thresh

[jira] [Created] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

Nitin Mehta created CLOUDSTACK-7820: --- Summary: Don't consider disabled hosts for calculating disable threshold. Key: CLOUDSTACK-7820 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7820 Proje

[jira] [Updated] (CLOUDSTACK-7820) Don't consider disabled hosts for calculating disable threshold.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7820: Fix Version/s: 4.6.0 > Don't consider disabled hosts for calculating disable threshold.

[jira] [Updated] (CLOUDSTACK-7773) CLONE - UI - listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offer

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7773: Component/s: (was: Management Server) UI > CLONE - UI - listServic

[jira] [Commented] (CLOUDSTACK-7773) CLONE - UI - listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service off

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180706#comment-14180706 ] Nitin Mehta commented on CLOUDSTACK-7773: - Look at CLOUDSTACK-4201 for unders

[jira] [Updated] (CLOUDSTACK-7773) CLONE - listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7773: Assignee: Jessica Wang (was: Nitin Mehta) > CLONE - listServiceOfferings API needs to

[jira] [Updated] (CLOUDSTACK-7773) CLONE - UI - listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offer

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7773: Summary: CLONE - UI - listServiceOfferings API needs to be able to take virtualmachinei

[jira] [Created] (CLOUDSTACK-7773) CLONE - listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

Nitin Mehta created CLOUDSTACK-7773: --- Summary: CLONE - listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering Key: CLOUDSTACK-

[jira] [Updated] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7771: Priority: Major (was: Critical) > Restore vm shouldnt go through if the template is al

[jira] [Commented] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180686#comment-14180686 ] Nitin Mehta commented on CLOUDSTACK-4201: - Issue - listServiceOfferings API t

[jira] [Comment Edited] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180680#comment-14180680 ] Nitin Mehta edited comment on CLOUDSTACK-7771 at 10/22/14 10:33 PM: ---

[jira] [Commented] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180680#comment-14180680 ] Nitin Mehta commented on CLOUDSTACK-7771: - Issue - 1. User launches a VM fro

[jira] [Updated] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7771: Affects Version/s: 4.5.0 > Restore vm shouldnt go through if the template is already de

[jira] [Updated] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7771: Fix Version/s: 4.5.0 > Restore vm shouldnt go through if the template is already delete

[jira] [Updated] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4201: Fix Version/s: (was: 4.5.0) 4.6.0 > listServiceOfferings API nee

[jira] [Updated] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7771: Fix Version/s: (was: 4.5.0) 4.6.0 > Restore vm shouldnt go throu

[jira] [Resolved] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7771. - Resolution: Fixed > Restore vm shouldnt go through if the template is already deleted

[jira] [Resolved] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-4201. - Resolution: Fixed > listServiceOfferings API needs to be able to take virtualmachinei

[jira] [Created] (CLOUDSTACK-7771) Restore vm shouldnt go through if the template is already deleted

Nitin Mehta created CLOUDSTACK-7771: --- Summary: Restore vm shouldnt go through if the template is already deleted Key: CLOUDSTACK-7771 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7771 Proje

[jira] [Issue Comment Deleted] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offe

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4201: Comment: was deleted (was: This is a good to have but not a critical. Downgrading the p

[jira] [Commented] (CLOUDSTACK-7754) 'vm_template.source_template_id' of Template created from Snapshot was NULL

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178793#comment-14178793 ] Nitin Mehta commented on CLOUDSTACK-7754: - Issue - Templates source_template_

[jira] [Resolved] (CLOUDSTACK-7754) 'vm_template.source_template_id' of Template created from Snapshot was NULL

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7754. - Resolution: Fixed > 'vm_template.source_template_id' of Template created from Snapsh

[jira] [Updated] (CLOUDSTACK-7754) 'vm_template.source_template_id' of Template created from Snapshot was NULL

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7754: Description: Here is the procedure to reproduce the issue. This is consistent on my en

[jira] [Created] (CLOUDSTACK-7754) 'vm_template.source_template_id' of Template created from Snapshot was NULL

Nitin Mehta created CLOUDSTACK-7754: --- Summary: 'vm_template.source_template_id' of Template created from Snapshot was NULL Key: CLOUDSTACK-7754 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7754

[jira] [Updated] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4201: Fix Version/s: (was: 4.6.0) 4.5.0 > listServiceOfferings API nee

[jira] [Updated] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4201: Environment: listServiceOfferings API needs to be able to take virtualmachineid of Syst

[jira] [Updated] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4201: Fix Version/s: (was: 4.5.0) 4.6.0 > listServiceOfferings API nee

[jira] [Comment Edited] (CLOUDSTACK-4201) listServiceOfferings API needs to be able to take virtualmachineid of SystemVM and return service offerings available for the vm to change service offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840417#comment-13840417 ] Nitin Mehta edited comment on CLOUDSTACK-4201 at 10/17/14 10:39 PM: ---

[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172984#comment-14172984 ] Nitin Mehta commented on CLOUDSTACK-7532: - If there is a UI bug as well pleas

[jira] [Issue Comment Deleted] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7532: Comment: was deleted (was: [~nvnp_sanjeev] - If there is a UI bug as well please open i

[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172981#comment-14172981 ] Nitin Mehta commented on CLOUDSTACK-7532: - [~nvnp_sanjeev] - If there is a UI

[jira] [Resolved] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7532. - Resolution: Fixed > [Templates] Template status is not shown in UI/API response for n

[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172934#comment-14172934 ] Nitin Mehta commented on CLOUDSTACK-7532: - Issue - Template status is not sho

[jira] [Resolved] (CLOUDSTACK-7699) Disable attach/detach root volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7699. - Resolution: Fixed > Disable attach/detach root volume >

[jira] [Commented] (CLOUDSTACK-7699) Disable attach/detach root volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169963#comment-14169963 ] Nitin Mehta commented on CLOUDSTACK-7699: - Please note this is disabled in 4.

[jira] [Created] (CLOUDSTACK-7699) Disable attach/detach root volume

Nitin Mehta created CLOUDSTACK-7699: --- Summary: Disable attach/detach root volume Key: CLOUDSTACK-7699 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7699 Project: CloudStack Issue T

[jira] [Updated] (CLOUDSTACK-7699) Disable attach/detach root volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7699: Affects Version/s: 4.5.0 > Disable attach/detach root volume > ---

[jira] [Updated] (CLOUDSTACK-7699) Disable attach/detach root volume

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7699: Fix Version/s: 4.5.0 > Disable attach/detach root volume > ---

[jira] [Resolved] (CLOUDSTACK-6284) Root volume detach support

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6284. - Resolution: Implemented Nothing was needed to be done for Vmware and KVM > Root volu

[jira] [Resolved] (CLOUDSTACK-6826) Ability to gracefully expire urls and clean them up when ssvm is destroyed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6826. - Resolution: Fixed > Ability to gracefully expire urls and clean them up when ssvm is

[jira] [Commented] (CLOUDSTACK-6826) Ability to gracefully expire urls and clean them up when ssvm is destroyed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169611#comment-14169611 ] Nitin Mehta commented on CLOUDSTACK-6826: - Issue1 - When download urls expir

[jira] [Updated] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5641: Fix Version/s: 4.5.0 > Local disk usage on host don't show up in the admin's webui > --

[jira] [Commented] (CLOUDSTACK-6023) Non windows instances are created on XenServer with a vcpu-max above supported xenserver limits

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156799#comment-14156799 ] Nitin Mehta commented on CLOUDSTACK-6023: - What is the fix version here ? >

[jira] [Updated] (CLOUDSTACK-6945) Null pointer exception when starting a VM that had its template deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6945: Priority: Critical (was: Minor) > Null pointer exception when starting a VM that had i

[jira] [Resolved] (CLOUDSTACK-7588) [Vmware] Creating templates (with same names) from volumes get deleted from CS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7588. - Resolution: Fixed > [Vmware] Creating templates (with same names) from volumes get d

[jira] [Updated] (CLOUDSTACK-7588) [Vmware] Creating templates (with same names) from volumes get deleted from CS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7588: Description: When createTemplate is used to create templates having the same name all o

[jira] [Updated] (CLOUDSTACK-7588) [Vmware] Creating templates (with same names) from volumes get deleted from CS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7588: Description: When createTemplate is used to create templates having the same name all o

[jira] [Updated] (CLOUDSTACK-7588) [Vmware] Creating templates (with same names) from volumes get deleted from CS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7588: Fix Version/s: 4.5.0 > [Vmware] Creating templates (with same names) from volumes get

[jira] [Created] (CLOUDSTACK-7588) [Vmware] Creating templates (with same names) from volumes get deleted from CS

Nitin Mehta created CLOUDSTACK-7588: --- Summary: [Vmware] Creating templates (with same names) from volumes get deleted from CS Key: CLOUDSTACK-7588 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7588

[jira] [Resolved] (CLOUDSTACK-7533) [Vmware] Wrong download URL generated when using multiple SSVMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7533. - Resolution: Fixed > [Vmware] Wrong download URL generated when using multiple SSVMs >

[jira] [Updated] (CLOUDSTACK-7533) [Vmware] Wrong download URL generated when using multiple SSVMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7533: Summary: [Vmware] Wrong download URL generated when using multiple SSVMs (was: Wrong d

[jira] [Resolved] (CLOUDSTACK-7513) listServiceOfferings API when called with VM's id also returns offerings to which it cant be upgraded

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7513. - Resolution: Fixed > listServiceOfferings API when called with VM's id also returns of

[jira] [Comment Edited] (CLOUDSTACK-7533) Wrong download URL generated when using multiple SSVMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129447#comment-14129447 ] Nitin Mehta edited comment on CLOUDSTACK-7533 at 9/11/14 12:44 AM:

[jira] [Commented] (CLOUDSTACK-7533) Wrong download URL generated when using multiple SSVMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129447#comment-14129447 ] Nitin Mehta commented on CLOUDSTACK-7533: - I have multiple SSVMs and when the

[jira] [Created] (CLOUDSTACK-7533) Wrong download URL generated when using multiple SSVMs

Nitin Mehta created CLOUDSTACK-7533: --- Summary: Wrong download URL generated when using multiple SSVMs Key: CLOUDSTACK-7533 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7533 Project: CloudSta

[jira] [Comment Edited] (CLOUDSTACK-5685) [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in state detected by cloudstack resulting in VR not bieng programmed with any rules.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129408#comment-14129408 ] Nitin Mehta edited comment on CLOUDSTACK-5685 at 9/11/14 12:07 AM:

[jira] [Commented] (CLOUDSTACK-5685) [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in state detected by cloudstack resulting in VR not bieng programmed with any rules.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129406#comment-14129406 ] Nitin Mehta commented on CLOUDSTACK-5685: - commit ee2adab7c7c9cf42eaf93c7eedb

[jira] [Commented] (CLOUDSTACK-5685) [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in state detected by cloudstack resulting in VR not bieng programmed with any rules.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129408#comment-14129408 ] Nitin Mehta commented on CLOUDSTACK-5685: - Basically the logic is something l

[jira] [Updated] (CLOUDSTACK-7513) listServiceOfferings API when called with VM's id also returns offerings to which it cant be upgraded

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7513: Description: When making the listServiceOfferings api call such as follows: http://loca

[jira] [Created] (CLOUDSTACK-7513) listServiceOfferings API when called with VM's id also returns offerings to which it cant be upgraded

Nitin Mehta created CLOUDSTACK-7513: --- Summary: listServiceOfferings API when called with VM's id also returns offerings to which it cant be upgraded Key: CLOUDSTACK-7513 URL: https://issues.apache.org/jira/brows

  1   2   3   4   5   6   7   8   9   >