You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/03/29 01:21:25 UTC

[jira] [Commented] (CLOUDSTACK-9199) deployVirtualMachine API does not throw an error when cpunumber is specified for static compute offering

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

ASF GitHub Bot commented on CLOUDSTACK-9199:
--------------------------------------------

Github user bvbharatk commented on the pull request:

    https://github.com/apache/cloudstack/pull/1280#issuecomment-202622942
  
    ### ACS CI BVT Run
     **Sumarry:**
     Build Number 141
     Hypervisor xenserver
     NetworkType Advanced
     Passed=101
     Failed=5
     Skipped=4
    
    _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
    
    
    **Failed tests:**
    * integration.smoke.test_loadbalance.TestLoadBalance
    
     * test_01_create_lb_rule_src_nat Failed
    
     * test_02_create_lb_rule_non_nat Failed
    
     * test_assign_and_removal_lb Failed
    
    * integration.smoke.test_volumes.TestCreateVolume
    
     * test_01_create_volume Failed
    
     * test_06_download_detached_volume Failed
    
    
    **Skipped tests:**
    test_vm_nic_adapter_vmxnet3
    test_deploy_vgpu_enabled_vm
    test_06_copy_template
    test_06_copy_iso
    
    **Passed test suits:**
    integration.smoke.test_deploy_vm_with_userdata.TestDeployVmWithUserData
    integration.smoke.test_affinity_groups_projects.TestDeployVmWithAffinityGroup
    integration.smoke.test_portable_publicip.TestPortablePublicIPAcquire
    integration.smoke.test_over_provisioning.TestUpdateOverProvision
    integration.smoke.test_global_settings.TestUpdateConfigWithScope
    integration.smoke.test_guest_vlan_range.TestDedicateGuestVlanRange
    integration.smoke.test_scale_vm.TestScaleVm
    integration.smoke.test_service_offerings.TestCreateServiceOffering
    integration.smoke.test_routers.TestRouterServices
    integration.smoke.test_reset_vm_on_reboot.TestResetVmOnReboot
    integration.smoke.test_snapshots.TestSnapshotRootDisk
    integration.smoke.test_deploy_vms_with_varied_deploymentplanners.TestDeployVmWithVariedPlanners
    integration.smoke.test_network.TestDeleteAccount
    integration.smoke.test_non_contigiousvlan.TestUpdatePhysicalNetwork
    integration.smoke.test_deploy_vm_iso.TestDeployVMFromISO
    integration.smoke.test_public_ip_range.TestDedicatePublicIPRange
    integration.smoke.test_multipleips_per_nic.TestDeployVM
    integration.smoke.test_regions.TestRegions
    integration.smoke.test_affinity_groups.TestDeployVmWithAffinityGroup
    integration.smoke.test_network_acl.TestNetworkACL
    integration.smoke.test_pvlan.TestPVLAN
    integration.smoke.test_ssvm.TestSSVMs
    integration.smoke.test_nic.TestNic
    integration.smoke.test_deploy_vm_root_resize.TestDeployVM
    integration.smoke.test_resource_detail.TestResourceDetail
    integration.smoke.test_secondary_storage.TestSecStorageServices
    integration.smoke.test_vm_life_cycle.TestDeployVM
    integration.smoke.test_disk_offerings.TestCreateDiskOffering


> deployVirtualMachine API does not throw an error when cpunumber is specified for static compute offering
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9199
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9199
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>
> When a dynamic compute offering is chosen, deployVirtualMachine API requires details[0].cpuSpeed, details[0].cpuNumber and details[0]memory parameters to deploy a VM.
> But when a static compute offering is chosen and these parameters are provided, then the API should throw an error as there is conflict.
> ACTUAL BEHAVIOR :
> VM is getting deployed with static compute offering's parameters
> http://10.220.135.6/client/api?command=deployVirtualMachine&name=olotwo&response=&zoneid=ab6e4154-62a3-42a8-9627-3cbdc66bcbb6&templateid=3aaaace6-91b4-11e5-b6fc-e26c2aa1d1d0&hypervisor=XenServer&serviceofferingid=39643075-4b45-489d-afac-88f09d536bdd&details[0].cpuNumber=1&details[0].cpuSpeed=1000&details[0].memory=1000&securitygroupids=60844698-91b4-11e5-b6fc-e26c2aa1d1d0&_=1448277187743



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