[
https://issues.apache.org/jira/browse/CLOUDSTACK-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579096#comment-13579096
]
Rohit Yadav commented on CLOUDSTACK-1291:
-----------------------------------------
You should not be using cloudapis, use marvin which generates cloudstackAPI,
the api bindings for Python.
This duplicate args bug was fixed on master/4.1, it was due to the way apidoc
would create a list of args and not set (set won't have duplicates).
> duplicate arguments in commands.xml prevents cloudapis.py to run to completion
> ------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1291
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1291
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.0.0, 4.0.1
> Environment: RHES63
> cloud-cli-4.0.1-1.el6.x86_64
> Reporter: Ove Everlid
> Priority: Critical
> Labels: API
> Fix For: 4.0.2
>
>
> Duplicate parameters ('account' and 'domainid') in the listVPC API call
> prevents cloudapis.py to generate a python API binding. Hackish fix to get
> going, remove the duplicates in commands.xml.
> [root@oel63-work-a ~]# python /usr/lib/python2.6/site-packages/cloudapis.py
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/cloudapis.py", line 23, in <module>
> from cloudtool.utils import describe
> File "/usr/lib/python2.6/site-packages/cloudtool/__init__.py", line 26, in
> <module>
> import cloudapis as apis
> File "/usr/lib/python2.6/site-packages/cloudapis.py", line 191, in <module>
> for name,meth in load_dynamic_methods():
> File "/usr/lib/python2.6/site-packages/cloudapis.py", line 182, in
> load_dynamic_methods
> exec code.strip() in namespace
> File "<string>", line 1
> SyntaxError: duplicate argument 'domainid' in function definition
> [root@oel63-work-a ~]#
--
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
