[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-04-22 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980253#comment-15980253
 ] 

ASF subversion and git services commented on CLOUDSTACK-9653:
-

Commit 1be37e41edd525d7c95ccc387d23cf8a7f78a45a in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1be37e4 ]

Merge pull request #1819 from Accelerite/ListCapacityIssue

CLOUDSTACK-9653 The system capacity was not getting calculated correctly

> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-04-22 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15979993#comment-15979993
 ] 

ASF subversion and git services commented on CLOUDSTACK-9653:
-

Commit 1be37e41edd525d7c95ccc387d23cf8a7f78a45a in cloudstack's branch 
refs/heads/4.9 from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1be37e4 ]

Merge pull request #1819 from Accelerite/ListCapacityIssue

CLOUDSTACK-9653 The system capacity was not getting calculated correctly

> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-02-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869677#comment-15869677
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user rashmidixit commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Looked at the errors. None of them have anything to do with the code 
changes.

ping @karuturi.


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-14 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822882#comment-15822882
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Trillian test result (tid-784)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42626 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1819-t784-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_router_nics.py
Test completed. 46 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 404.61 | 
test_privategw_acl.py
test_01_create_volume | `Error` | 279.54 | test_volumes.py
test_01_vpc_site2site_vpn | Success | 160.51 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 65.81 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 240.05 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 443.52 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 813.10 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 503.65 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1400.18 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 552.32 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 754.83 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1292.83 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 151.31 | test_volumes.py
test_08_resize_volume | Success | 156.28 | test_volumes.py
test_07_resize_fail | Success | 156.39 | test_volumes.py
test_06_download_detached_volume | Success | 156.12 | test_volumes.py
test_05_detach_volume | Success | 235.91 | test_volumes.py
test_04_delete_attached_volume | Success | 151.14 | test_volumes.py
test_03_download_attached_volume | Success | 156.42 | test_volumes.py
test_02_attach_volume | Success | 185.59 | test_volumes.py
test_deploy_vm_multiple | Success | 332.88 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.51 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 185.26 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.64 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.08 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.99 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.67 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.13 | test_vm_life_cycle.py
test_01_stop_vm | Success | 125.64 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 65.44 | test_templates.py
test_08_list_system_templates | Success | 0.02 | test_templates.py
test_07_list_public_templates | Success | 0.02 | test_templates.py
test_05_template_permissions | Success | 0.04 | test_templates.py
test_04_extract_template | Success | 5.15 | test_templates.py
test_03_delete_template | Success | 5.08 | test_templates.py
test_02_edit_template | Success | 90.15 | test_templates.py
test_01_create_template | Success | 125.72 | test_templates.py
test_10_destroy_cpvm | Success | 161.49 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.38 | test_ssvm.py
test_08_reboot_cpvm | Success | 131.64 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.87 | test_ssvm.py
test_06_stop_cpvm | Success | 131.53 | test_ssvm.py
test_05_stop_ssvm | Success | 133.48 | test_ssvm.py
test_04_cpvm_internals | Success | 1.16 | test_ssvm.py
test_03_ssvm_internals | Success | 3.98 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.09 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.09 | test_ssvm.py
test_01_snapshot_root_disk | Success | 16.13 | test_snapshots.py
test_04_change_offering_small | Success | 239.71 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.04 | test_service_offerings.py
test_01_create_service_offering | Success | 0.08 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.09 | test_secondary_storage.py

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-14 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822881#comment-15822881
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Trillian test result (tid-784)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42626 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1819-t784-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_router_nics.py
Test completed. 46 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 404.61 | 
test_privategw_acl.py
test_01_create_volume | `Error` | 279.54 | test_volumes.py
test_01_vpc_site2site_vpn | Success | 160.51 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 65.81 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 240.05 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 443.52 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 813.10 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 503.65 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1400.18 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 552.32 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 754.83 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1292.83 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 151.31 | test_volumes.py
test_08_resize_volume | Success | 156.28 | test_volumes.py
test_07_resize_fail | Success | 156.39 | test_volumes.py
test_06_download_detached_volume | Success | 156.12 | test_volumes.py
test_05_detach_volume | Success | 235.91 | test_volumes.py
test_04_delete_attached_volume | Success | 151.14 | test_volumes.py
test_03_download_attached_volume | Success | 156.42 | test_volumes.py
test_02_attach_volume | Success | 185.59 | test_volumes.py
test_deploy_vm_multiple | Success | 332.88 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.51 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 185.26 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.64 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.08 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.99 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.67 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.13 | test_vm_life_cycle.py
test_01_stop_vm | Success | 125.64 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 65.44 | test_templates.py
test_08_list_system_templates | Success | 0.02 | test_templates.py
test_07_list_public_templates | Success | 0.02 | test_templates.py
test_05_template_permissions | Success | 0.04 | test_templates.py
test_04_extract_template | Success | 5.15 | test_templates.py
test_03_delete_template | Success | 5.08 | test_templates.py
test_02_edit_template | Success | 90.15 | test_templates.py
test_01_create_template | Success | 125.72 | test_templates.py
test_10_destroy_cpvm | Success | 161.49 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.38 | test_ssvm.py
test_08_reboot_cpvm | Success | 131.64 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.87 | test_ssvm.py
test_06_stop_cpvm | Success | 131.53 | test_ssvm.py
test_05_stop_ssvm | Success | 133.48 | test_ssvm.py
test_04_cpvm_internals | Success | 1.16 | test_ssvm.py
test_03_ssvm_internals | Success | 3.98 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.09 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.09 | test_ssvm.py
test_01_snapshot_root_disk | Success | 16.13 | test_snapshots.py
test_04_change_offering_small | Success | 239.71 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.04 | test_service_offerings.py
test_01_create_service_offering | Success | 0.08 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.09 | test_secondary_storage.py

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822713#comment-15822713
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@blueorangutan test


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822712#comment-15822712
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822709#comment-15822709
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@blueorangutan test


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822710#comment-15822710
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822574#comment-15822574
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Packaging result: ✔centos6 ✔centos7 ✖debian. JID-458


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822537#comment-15822537
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822535#comment-15822535
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822534#comment-15822534
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822532#comment-15822532
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@blueorangutan package


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821590#comment-15821590
 ] 

rashmidixit commented on CLOUDSTACK-9653:
-

Github user koushik-das commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Code changes LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821589#comment-15821589
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user koushik-das commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Code changes LGTM


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-03 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794575#comment-15794575
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-03 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794510#comment-15794510
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Packaging result: ✔centos6 ✔centos7 ✖debian. JID-442


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-02 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794411#comment-15794411
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-02 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794408#comment-15794408
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@blueorangutan package


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2016-12-30 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15787341#comment-15787341
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


GitHub user rashmidixit reopened a pull request:

https://github.com/apache/cloudstack/pull/1819

CLOUDSTACK-9653 The system capacity was not getting calculated correctly

When listCapacity is used with the sortBy=usage option, the capacity was 
not getting calculated correctly.

Root Cause: The group by options for pod and zone was incorrectly 
specified. Results were additionally added up. Result was incorrect.

Once the correct group by clause is specified, only the results of the 
query need to be returned.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack ListCapacityIssue

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1819.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1819


commit 97b6b117e1448115613318aef1679ac00c93375e
Author: rashmidixit 
Date:   2016-12-05T08:55:27Z

The system capacity was not getting calculated correctly




> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2016-12-30 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15787340#comment-15787340
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user rashmidixit closed the pull request at:

https://github.com/apache/cloudstack/pull/1819


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2016-12-07 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731306#comment-15731306
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Packaging result: ✔centos6 ✔centos7 ✖debian. JID-348


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2016-12-07 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731166#comment-15731166
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2016-12-07 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731165#comment-15731165
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
LGTM.
@blueorangutan package


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2016-12-07 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728367#comment-15728367
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9653:


GitHub user rashmidixit opened a pull request:

https://github.com/apache/cloudstack/pull/1819

CLOUDSTACK-9653 The system capacity was not getting calculated correctly

When listCapacity is used with the sortBy=usage option, the capacity was 
not getting calculated correctly.

Root Cause: The group by options for pod and zone was incorrectly 
specified. Results were additionally added up. Result was incorrect.

Once the correct group by clause is specified, only the results of the 
query need to be returned.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack ListCapacityIssue

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1819.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1819


commit 97b6b117e1448115613318aef1679ac00c93375e
Author: rashmidixit 
Date:   2016-12-05T08:55:27Z

The system capacity was not getting calculated correctly




> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)