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

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

Commit 30161f8592d9e7d06942c73e131b40d79a90ad54 in branch 
refs/heads/master-6-17-stable from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=30161f8 ]

CLOUDSTACK-2592 [Automation]: Scale up VM on VMWARE without license doesn't 
throw appropriate error

Now ESXi server license would be fetched to see if HOTPLUG feature is license 
or not.
Throw Exception if the feature is not licensed.

Also added FeatureKeyConstants enum type to maintain list of various features 
to be checked whether licensed or not.

                
> [Automation]: Scale up VM on VMWARE without license doesn't throw appropriate 
> error
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2592
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2592
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API, VMware
>    Affects Versions: 4.2.0
>         Environment: Master
>            Reporter: Parth Jagirdar
>            Assignee: Sateesh Chodapuneedi
>             Fix For: 4.2.0
>
>
> Stacktrace
>   File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
>     testMethod()
>   File 
> "/data/Repo2/qa/incubator-cloudstack/test/integration/smoke/test_scale_vm.py",
>  line 213, in test_01_scale_vm
>     "Check service offering of the VM"
>   File "/usr/local/lib/python2.7/unittest/case.py", line 494, in assertEqual
>     assertion_func(first, second, msg=msg)
>   File "/usr/local/lib/python2.7/unittest/case.py", line 902, in 
> assertMultiLineEqual
>     self.fail(self._formatMessage(msg, standardMsg))
>   File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
>     raise self.failureException(msg)
> Check service offering of the VM
> Upon manual verification ::
> Setup was unable to scale up the VM. Choosing a larger offering actually 
> doesnt give any errors.
> But the VM details still reflects old service offering.
> Digging around reveled from MS log:
> 2013-05-20 16:13:26,004 ERROR [vmware.resource.VmwareResource] 
> (DirectAgent-1:10.223.250.130) Unexpected exception:
> java.lang.RuntimeException: License not available to perform the operation.
>         at 
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291)
>         at 
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:806)
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2272)
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:500)
>         at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:722)
> If license is not available then CS should throw appropriate error as 
> "Feature not supported".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to