cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-3102) [DR] [add/list] ResourceDetail APIs only works for resourceType "volume/nic"
Date Tue, 06 Aug 2013 06:54:50 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

venkata swamybabu budumuru closed CLOUDSTACK-3102.
--------------------------------------------------


As per the fix, currently we are allowing only nic and volume details to be populated but,
everything else will throw an exception like below. Closing the issue.


013-08-06 12:22:41,443 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-29:job-93 = [
8abb2109-dfa1-4e9c-bd9d-75974f8b47c9 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AddResourceDetailCmd
com.cloud.exception.InvalidParameterValueException: The resource type Network is not supported
by the API yet
	at com.cloud.metadata.ResourceMetaDataManagerImpl.addResourceMetaData(ResourceMetaDataManagerImpl.java:221)
	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
	at org.apache.cloudstack.api.command.user.volume.AddResourceDetailCmd.execute(AddResourceDetailCmd.java:113)
	at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
	at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
	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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:679)

                
> [DR] [add/list] ResourceDetail APIs only works for resourceType "volume/nic" 
> -----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3102
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3102
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: commit # 971c40d98e07ab6cddb8e6db5095c1acea935815
>            Reporter: venkata swamybabu budumuru
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have CloudStack setup with at least 1 advanced zone
> 2. Try to insert key, value into user_vm_details using the following API
> http://10.147.59.194:8096/api?command=addResourceDetail&resourceid=38&resourcetype=uservm&details[0].key=test&details[0].value=test
> Tried to pass the vm id i.e. 38 and key, value in to user_details
> Observations :-
> (i) It went fine but, it inserted those key, values into nic_details table.
> mysql> select * from nic_details;
> +----+--------+------+-------+----------------+
> | id | nic_id | name | value | display_detail |
> +----+--------+------+-------+----------------+
> |  1 |     38 | test | test  |              1 |
> +----+--------+------+-------+----------------+
> (ii)Tried to check the same with listResourceDetail and it fetches the info from nic_details
table.
> http://10.147.59.194:8096/api?command=listResourceDetails&resourceType=uservm&resourceid=38
> <listresourcedetailsresponse cloud-stack-version="4.2.0-SNAPSHOT"><count>1</count><nicdetail><resourcetype>Nic</resourcetype><key>test</key><value>test</value></nicdetail></listresourcedetailsresponse>
> (iii) looked into the code and found that if addResourceDetail is executed on Volume
then things go fine otherwise, we are inserting everything into nic_details table.

--
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

Mime
View raw message