cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7685) test_escalations_templates.TestTemplates.test_04_copy_template failing due to template copy method call failed
Date Thu, 30 Oct 2014 09:48:34 GMT

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

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

Commit a1e7feead91b22350f96114add4bf8d75a74b8b1 in cloudstack's branch refs/heads/4.5 from
[~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a1e7fee ]

CLOUDSTACK-7685: Fixed copy template method call in test_escalations_template.py. Removed
unbound method of the same name as bound method from base library and changed method call
accordingly

Signed-off-by: SrikanteswaraRao Talluri <talluri@apache.org>


> test_escalations_templates.TestTemplates.test_04_copy_template failing due to template
copy method call failed
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7685
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7685
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.5.0
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.5.0
>
>
> Error details:
> unbound method copy() must be called with Template instance as first argument (got CloudStackAPIClient
instance instead)
> Reason:
> There are bound and unbound methods "copy" in Template class with the same name. Apparently
when bound and unbound methods with same name are defined, call to unbound method fails.
> Solution:
> Keep only unbound method. And if call is made like a classmethod (Class.method()), then
explicitly pass the first argument as instance of class.



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

Mime
View raw message