[jira] [Commented] (CLOUDSTACK-5700) [Vmsync] - kvm- "paused" state of Vm is not synced to CS.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211939#comment-14211939 ] Bharat Kumar commented on CLOUDSTACK-5700: -- Hi, Cloudstack considers paused

[jira] [Resolved] (CLOUDSTACK-5700) [Vmsync] - kvm- "paused" state of Vm is not synced to CS.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5700. -- Resolution: Fixed > [Vmsync] - kvm- "paused" state of Vm is not synced to CS. > ---

[jira] [Commented] (CLOUDSTACK-7300) Cannot create Snapshot on KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211941#comment-14211941 ] Bharat Kumar commented on CLOUDSTACK-7300: -- not an issue in 4.5, Snapshots a

[jira] [Commented] (CLOUDSTACK-7004) [Automation] [KVM] Deploying a VM with rootdisksize less than the size of template does not fail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212097#comment-14212097 ] Bharat Kumar commented on CLOUDSTACK-7004: -- could not reproduce on 4.5 > [A

[jira] [Created] (CLOUDSTACK-7922) CLONE - [Automation] [KVM] Deploying a VM with rootdisksize less than the size of template does not fail

Bharat Kumar created CLOUDSTACK-7922: Summary: CLONE - [Automation] [KVM] Deploying a VM with rootdisksize less than the size of template does not fail Key: CLOUDSTACK-7922 URL: https://issues.apache.org/jira/

[jira] [Updated] (CLOUDSTACK-7922) CLONE - [Automation] [KVM] Deploying a VM with rootdisksize less than the size of template does not fail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7922: - Fix Version/s: (was: 4.5.0) > CLONE - [Automation] [KVM] Deploying a VM with root

[jira] [Updated] (CLOUDSTACK-7004) [Automation] [KVM] Deploying a VM with rootdisksize less than the size of template does not fail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7004: - Fix Version/s: (was: 4.4.0) > [Automation] [KVM] Deploying a VM with rootdisksize

[jira] [Resolved] (CLOUDSTACK-7004) [Automation] [KVM] Deploying a VM with rootdisksize less than the size of template does not fail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-7004. -- Resolution: Cannot Reproduce > [Automation] [KVM] Deploying a VM with rootdisksize

[jira] [Updated] (CLOUDSTACK-7300) Cannot create Snapshot on KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7300: - Status: Reviewable (was: In Progress) > Cannot create Snapshot on KVM >

[jira] [Commented] (CLOUDSTACK-7501) System VM fails to move from one cluster to another cluster when hypervisor type differs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213475#comment-14213475 ] Bharat Kumar commented on CLOUDSTACK-7501: -- if we do not mention any default

[jira] [Resolved] (CLOUDSTACK-7501) System VM fails to move from one cluster to another cluster when hypervisor type differs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-7501. -- Resolution: Fixed > System VM fails to move from one cluster to another cluster whe

[jira] [Comment Edited] (CLOUDSTACK-7501) System VM fails to move from one cluster to another cluster when hypervisor type differs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213475#comment-14213475 ] Bharat Kumar edited comment on CLOUDSTACK-7501 at 11/15/14 9:39 AM: ---

[jira] [Updated] (CLOUDSTACK-7300) Cannot create Snapshot on KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7300: - Status: Open (was: Reviewable) > Cannot create Snapshot on KVM > ---

[jira] [Created] (CLOUDSTACK-7939) when a template is deleted an copied over again the removed column is not updated properly.

Bharat Kumar created CLOUDSTACK-7939: Summary: when a template is deleted an copied over again the removed column is not updated properly. Key: CLOUDSTACK-7939 URL: https://issues.apache.org/jira/browse/CLOUDS

[jira] [Updated] (CLOUDSTACK-7939) when a template is deleted and copied over again the removed column is not updated properly.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7939: - Summary: when a template is deleted and copied over again the removed column is not u

[jira] [Resolved] (CLOUDSTACK-6873) [Automation] Ability to execute tests in sequence

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-6873. -- Resolution: Fixed > [Automation] Ability to execute tests in sequence > ---

[jira] [Resolved] (CLOUDSTACK-7710) Triage and fix Coverity defects

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-7710. -- Resolution: Duplicate > Triage and fix Coverity defects > -

[jira] [Created] (CLOUDSTACK-8353) Including windows guest performance improvement flags like hv_vapic and hv_spinlock in CCP

Bharat Kumar created CLOUDSTACK-8353: Summary: Including windows guest performance improvement flags like hv_vapic and hv_spinlock in CCP Key: CLOUDSTACK-8353 URL: https://issues.apache.org/jira/browse/CLOUDST

[jira] [Updated] (CLOUDSTACK-8353) Including windows guest performance improvement flags like hv_vapic and hv_spinlock in CCP

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-8353: - Description: There is a bug in KVM that causes a BSOD for Windows 2008 R2 and 7 or ea

[jira] [Commented] (CLOUDSTACK-8360) Install issue: RPM install failing with a DB error message

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394246#comment-14394246 ] Bharat Kumar commented on CLOUDSTACK-8360: -- might happen in a upgraded setup

[jira] [Created] (CLOUDSTACK-6623) register template dose not work as expected. when using simulator and xen simultaneously

Bharat Kumar created CLOUDSTACK-6623: Summary: register template dose not work as expected. when using simulator and xen simultaneously Key: CLOUDSTACK-6623 URL: https://issues.apache.org/jira/browse/CLOUDSTA

[jira] [Updated] (CLOUDSTACK-6623) register template dose not work as expected, when deploying simulator and xen zones simultaneously on a single management server.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-6623: - Summary: register template dose not work as expected, when deploying simulator and x

[jira] [Commented] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013308#comment-14013308 ] Bharat Kumar commented on CLOUDSTACK-6794: -- Hi , This fix is environment sp

[jira] [Closed] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-6794. Resolution: Fixed > [Automation]: test_iso suite is failing because of no path to iso

[jira] [Reopened] (CLOUDSTACK-6769) [Automation]: Test case failure in test_iso.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reopened CLOUDSTACK-6769: -- Hi, This issue occurred because of a environment issue which i have fixed. now the t

[jira] [Commented] (CLOUDSTACK-6769) [Automation]: Test case failure in test_iso.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017855#comment-14017855 ] Bharat Kumar commented on CLOUDSTACK-6769: -- Hi, In case of kvm the followin

[jira] [Created] (CLOUDSTACK-6874) automation test failures.

Bharat Kumar created CLOUDSTACK-6874: Summary: automation test failures. Key: CLOUDSTACK-6874 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6874 Project: CloudStack Issue Type: Bu

[jira] [Created] (CLOUDSTACK-6875) test_volumes is failing on simulator runs

Bharat Kumar created CLOUDSTACK-6875: Summary: test_volumes is failing on simulator runs Key: CLOUDSTACK-6875 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6875 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-6876) test_deploy_vgpu_enabled_vm is failing on xen and Kvm runs.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-6876: - Summary: test_deploy_vgpu_enabled_vm is failing on xen and Kvm runs. (was: test_dep

[jira] [Created] (CLOUDSTACK-6876) test_deploy_vgpu_enabled_vm is failing on xen and ivm runs.

Bharat Kumar created CLOUDSTACK-6876: Summary: test_deploy_vgpu_enabled_vm is failing on xen and ivm runs. Key: CLOUDSTACK-6876 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6876 Project:

[jira] [Created] (CLOUDSTACK-6877) test_01_sys_vm_start from suite test_secondary storage is failing on xen and kvm

Bharat Kumar created CLOUDSTACK-6877: Summary: test_01_sys_vm_start from suite test_secondary storage is failing on xen and kvm Key: CLOUDSTACK-6877 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6877

[jira] [Created] (CLOUDSTACK-6878) test_snapshots.TestSnapshotRootDisk.test_01_snapshot_root_disk is failing on xen, kvm

Bharat Kumar created CLOUDSTACK-6878: Summary: test_snapshots.TestSnapshotRootDisk.test_01_snapshot_root_disk is failing on xen, kvm Key: CLOUDSTACK-6878 URL: https://issues.apache.org/jira/browse/CLOUDSTACK

[jira] [Updated] (CLOUDSTACK-6877) test_01_sys_vm_start from suite test_secondary storage is failing on xen

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-6877: - Summary: test_01_sys_vm_start from suite test_secondary storage is failing on xen (

[jira] [Updated] (CLOUDSTACK-6875) test_volumes.TestVolumes.test_09_delete_detached_volume is failing on simulator runs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-6875: - Summary: test_volumes.TestVolumes.test_09_delete_detached_volume is failing on simul

[jira] [Created] (CLOUDSTACK-6914) The present way of tagging the test cases as provisioning and simulator is not usable. Need to modify this.

Bharat Kumar created CLOUDSTACK-6914: Summary: The present way of tagging the test cases as provisioning and simulator is not usable. Need to modify this. Key: CLOUDSTACK-6914 URL: https://issues.apache.org/ji

[jira] [Reopened] (CLOUDSTACK-6769) [Automation]: Test case failure in test_iso.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reopened CLOUDSTACK-6769: -- > [Automation]: Test case failure in test_iso.py > ---

[jira] [Commented] (CLOUDSTACK-6769) [Automation]: Test case failure in test_iso.py

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033855#comment-14033855 ] Bharat Kumar commented on CLOUDSTACK-6769: -- Hi reopening this issue as the c

[jira] [Created] (CLOUDSTACK-6933) registering an iso fails in KVM deployment.

Bharat Kumar created CLOUDSTACK-6933: Summary: registering an iso fails in KVM deployment. Key: CLOUDSTACK-6933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6933 Project: CloudStack

[jira] [Created] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware.

Bharat Kumar created CLOUDSTACK-7026: Summary: mark the test_01_primary_storage_iscsi as test that requires hardware. Key: CLOUDSTACK-7026 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7026

[jira] [Updated] (CLOUDSTACK-7026) test that requires hardware.mark the test_01_primary_storage_iscsi as test that requires hardware

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7026: - Summary: test that requires hardware.mark the test_01_primary_storage_iscsi as test

[jira] [Updated] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7026: - Summary: mark the test_01_primary_storage_iscsi as test that requires hardware (was

[jira] [Resolved] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-7026. -- Resolution: Fixed > mark the test_01_primary_storage_iscsi as test that requires h

[jira] [Created] (CLOUDSTACK-7155) Re-copying templates to other zones doesn't work

Bharat Kumar created CLOUDSTACK-7155: Summary: Re-copying templates to other zones doesn't work Key: CLOUDSTACK-7155 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7155 Project: CloudStack

[jira] [Created] (CLOUDSTACK-7156) List templates API returns destroyed templates when recopying the template.

Bharat Kumar created CLOUDSTACK-7156: Summary: List templates API returns destroyed templates when recopying the template. Key: CLOUDSTACK-7156 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7156

[jira] [Created] (CLOUDSTACK-7158) listCapacity API missing types for certain zones

Bharat Kumar created CLOUDSTACK-7158: Summary: listCapacity API missing types for certain zones Key: CLOUDSTACK-7158 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7158 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-7158) listCapacity API missing types for certain zones

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7158: - Status: Reviewable (was: In Progress) > listCapacity API missing types for certain

[jira] [Updated] (CLOUDSTACK-7156) List templates API returns destroyed templates when recopying the template.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7156: - Status: Reviewable (was: In Progress) > List templates API returns destroyed templa

[jira] [Resolved] (CLOUDSTACK-5162) Usage details are not getting populated when using dynamic offerings.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5162. -- Resolution: Fixed > Usage details are not getting populated when using dynamic off

[jira] [Resolved] (CLOUDSTACK-5161) add dynamic compute support to scale vm and upgrade vm apis.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5161. -- Resolution: Fixed committed to 4.3 > add dynamic compute support to scale vm and

[jira] [Resolved] (CLOUDSTACK-5160) add a map to specify the custom parameters in the deployvm api.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5160. -- Resolution: Fixed 089c7bc9f8f0861bb2eedc340ae623f5abeccfc3 4.3 > add a map to s

[jira] [Assigned] (CLOUDSTACK-5472) UI shows incorrect vm statistics if vm deployed with dynamic compute offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reassigned CLOUDSTACK-5472: Assignee: Bharat Kumar > UI shows incorrect vm statistics if vm deployed with

[jira] [Commented] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848362#comment-13848362 ] Bharat Kumar commented on CLOUDSTACK-5495: -- was able to reproduce this on 4.

[jira] [Comment Edited] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848362#comment-13848362 ] Bharat Kumar edited comment on CLOUDSTACK-5495 at 12/14/13 2:00 PM: ---

[jira] [Commented] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848388#comment-13848388 ] Bharat Kumar commented on CLOUDSTACK-5495: -- Hi, In 4.3 i can see the execut

[jira] [Commented] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849072#comment-13849072 ] Bharat Kumar commented on CLOUDSTACK-5495: -- Hi, I was not able to reproduce

[jira] [Updated] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5495: - Attachment: xensource-unabel-to-stop-vm.log > [Automation] Unable to stop VM > -

[jira] [Commented] (CLOUDSTACK-5502) [Automation] createVlanIpRange API failing, if you pass VLAN

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850299#comment-13850299 ] Bharat Kumar commented on CLOUDSTACK-5502: -- This the expected behaviour. i.e

[jira] [Resolved] (CLOUDSTACK-5502) [Automation] createVlanIpRange API failing, if you pass VLAN

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5502. -- Resolution: Invalid > [Automation] createVlanIpRange API failing, if you pass VLAN

[jira] [Commented] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850411#comment-13850411 ] Bharat Kumar commented on CLOUDSTACK-5495: -- Note: The default value of the e

[jira] [Resolved] (CLOUDSTACK-5495) [Automation] Unable to stop VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5495. -- Resolution: Fixed > [Automation] Unable to stop VM > -

[jira] [Commented] (CLOUDSTACK-5502) [Automation] createVlanIpRange API failing, if you pass VLAN

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851726#comment-13851726 ] Bharat Kumar commented on CLOUDSTACK-5502: -- Hi, I saw the parameter descript

[jira] [Commented] (CLOUDSTACK-5585) [Automation]Unable to stop VM reported by HA Worker

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856261#comment-13856261 ] Bharat Kumar commented on CLOUDSTACK-5585: -- The stopVM command is successfu

[jira] [Resolved] (CLOUDSTACK-5585) [Automation]Unable to stop VM reported by HA Worker

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5585. -- Resolution: Fixed > [Automation]Unable to stop VM reported by HA Worker >

[jira] [Updated] (CLOUDSTACK-5472) UI shows incorrect vm statistics if vm deployed with dynamic compute offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5472: - Status: Ready To Review (was: In Progress) > UI shows incorrect vm statistics if vm

[jira] [Resolved] (CLOUDSTACK-5530) attempt to add secondary storage with the same name is ignored

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5530. -- Resolution: Fixed > attempt to add secondary storage with the same name is ignored

[jira] [Updated] (CLOUDSTACK-5711) allow scaling from the same offering when using custom compute offering.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5711: - Priority: Critical (was: Major) > allow scaling from the same offering when using c

[jira] [Created] (CLOUDSTACK-5711) allow scaling from the same offering when using custom compute offering.

Bharat Kumar created CLOUDSTACK-5711: Summary: allow scaling from the same offering when using custom compute offering. Key: CLOUDSTACK-5711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5711

[jira] [Created] (CLOUDSTACK-5750) Make default value of execute.in.sequence.hypervisor.commands false.

Bharat Kumar created CLOUDSTACK-5750: Summary: Make default value of execute.in.sequence.hypervisor.commands false. Key: CLOUDSTACK-5750 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5750

[jira] [Updated] (CLOUDSTACK-5742) #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for dynamic compute offering in usage_vm_instance table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5742: - Assignee: Harikrishna Patnala (was: Bharat Kumar) > #cpu,cpu speed, and ram is gett

[jira] [Commented] (CLOUDSTACK-5750) Make default value of execute.in.sequence.hypervisor.commands false.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862851#comment-13862851 ] Bharat Kumar commented on CLOUDSTACK-5750: -- As part of the fix to make the e

[jira] [Updated] (CLOUDSTACK-5750) Make default value of execute.in.sequence.hypervisor.commands false.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5750: - Status: Ready To Review (was: In Progress) > Make default value of execute.in.seque

[jira] [Resolved] (CLOUDSTACK-5472) UI shows incorrect vm statistics if vm deployed with dynamic compute offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5472. -- Resolution: Fixed Fix Version/s: 4.3.0 > UI shows incorrect vm statistics i

[jira] [Resolved] (CLOUDSTACK-5750) Make default value of execute.in.sequence.hypervisor.commands false.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5750. -- Resolution: Fixed > Make default value of execute.in.sequence.hypervisor.commands

[jira] [Updated] (CLOUDSTACK-5706) Multiple NPEs when host is put in maintenance after upgrading from 4.2.1 to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5706: - Assignee: (was: Bharat Kumar) > Multiple NPEs when host is put in maintenance af

[jira] [Resolved] (CLOUDSTACK-5579) description of "execute.in.sequence.hypervisor.commands" need to be updated in global config

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5579. -- Resolution: Fixed Assignee: Bharat Kumar > description of "execute.in.sequen

[jira] [Updated] (CLOUDSTACK-5742) #cpu,cpu speed, and ram is getting updated under wrong usage_type(2) for dynamic compute offering in usage_vm_instance table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5742: - Status: Ready To Review (was: In Progress) > #cpu,cpu speed, and ram is getting upd

[jira] [Comment Edited] (CLOUDSTACK-5651) deployVm: customparameters param name has to be changed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865392#comment-13865392 ] Bharat Kumar edited comment on CLOUDSTACK-5651 at 1/8/14 1:06 PM: -

[jira] [Commented] (CLOUDSTACK-5651) deployVm: customparameters param name has to be changed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865392#comment-13865392 ] Bharat Kumar commented on CLOUDSTACK-5651: -- Hi, The customParameter name i

[jira] [Updated] (CLOUDSTACK-5651) deployVm: customparameters param name has to be changed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-5651: - Status: Ready To Review (was: In Progress) > deployVm: customparameters param name

[jira] [Commented] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > ava

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727371#comment-13727371 ] Bharat Kumar commented on CLOUDSTACK-1695: -- The vms should be deployed only

[jira] [Assigned] (CLOUDSTACK-3753) Multiple VLAN range API need to accept a list rather than "add" or "remove" per command

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reassigned CLOUDSTACK-3753: Assignee: Bharat Kumar > Multiple VLAN range API need to accept a list rat

[jira] [Resolved] (CLOUDSTACK-3753) Multiple VLAN range API need to accept a list rather than "add" or "remove" per command

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3753. -- Resolution: Fixed > Multiple VLAN range API need to accept a list rather than

[jira] [Commented] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727609#comment-13727609 ] Bharat Kumar commented on CLOUDSTACK-3836: -- commit 60585b51819e4391373d71c63

[jira] [Resolved] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3836. -- Resolution: Fixed commit 65370f31bcb1ae5238be5e68462ea0d79df3296f in master.

[jira] [Comment Edited] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727609#comment-13727609 ] Bharat Kumar edited comment on CLOUDSTACK-3836 at 8/2/13 11:58 AM:

[jira] [Commented] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727610#comment-13727610 ] Bharat Kumar commented on CLOUDSTACK-3612: -- fixed the iso_id inconsistency.

[jira] [Resolved] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3612. -- Resolution: Fixed > 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies

[jira] [Closed] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-3612. Resolution: Fixed 60585b51819e4391373d71c63138e36f0a3c5898 in 4.2 > 3

[jira] [Reopened] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reopened CLOUDSTACK-3612: -- > 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded > Set

[jira] [Resolved] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > avai

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-1695. -- Resolution: Fixed 0951739e32fa6e2c9cee1bd1bca2817c2536ef50 hash in 4.2 80e2934bb7

[jira] [Resolved] (CLOUDSTACK-3763) [Automation] Fix the test_non_contiguous.py test case that tests addition/removal of non-contiguous VLANs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3763. -- Resolution: Fixed 6e83a54ffbf69e46a79fbaf0be63e63092385b65 commit in 4.2

[jira] [Commented] (CLOUDSTACK-3763) [Automation] Fix the test_non_contiguous.py test case that tests addition/removal of non-contiguous VLANs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729114#comment-13729114 ] Bharat Kumar commented on CLOUDSTACK-3763: -- 6e83a54ffbf69e46a79fbaf0be63e63

[jira] [Updated] (CLOUDSTACK-3763) [Automation] Fix the test_non_contiguous.py test case that tests addition/removal of non-contiguous VLANs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3763: - Assignee: Bharat Kumar > [Automation] Fix the test_non_contiguous.py test case t

[jira] [Closed] (CLOUDSTACK-3370) Add ipalias deletion to the network gc

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-3370. changed the desig not valid anymore. > Add ipalias deletion to the networ

[jira] [Created] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.1

Bharat Kumar created CLOUDSTACK-4100: Summary: Do not drop iso_id column while upgrading form 3.0.7 to 4.1 Key: CLOUDSTACK-4100 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4100 Project:

[jira] [Updated] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Summary: Do not drop iso_id column while upgrading form 3.0.7 to 4.2 (was: Do not d

[jira] [Updated] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Description: we need to preserve the data in iso_id cloumn while upgraign from 3.0.7

[jira] [Updated] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Description: we need to preserve the data in iso_id cloumn while upgrading from 3.0.

[jira] [Updated] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4105: - Assignee: Bharat Kumar > Vnet's from Phisical network's table are getting delete

[jira] [Updated] (CLOUDSTACK-3782) Data disk size is modified to KB from GB after it is attached to the instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3782: - Assignee: (was: Bharat Kumar) > Data disk size is modified to KB from GB aft

  1   2   3   4   5   >