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

Tomaz Muraus commented on LIBCLOUD-183:
---------------------------------------

I've applied the patch (LIBCLOUD-183-vcloud_1_5-2.patch) against the latest 
master and the tests fail with the following error:

Traceback (most recent call last):
  File "/w/lc/trunk/test/compute/test_vcloud.py", line 164, in 
test_ex_undeploy_with_error
    node = 
self.driver.ex_undeploy_node(Node('https://test/api/vApp/undeployErrorTest', 
'testNode', state=0, public_ips=[], private_ips=[], driver=self.driver))
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 899, in 
ex_undeploy_node
    'Content-Type': 'application/vnd.vmware.vcloud.undeployVAppParams+xml'
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 239, in request
    self._get_auth_token()
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 711, in 
_get_auth_token
    raise InvalidCredsError()
InvalidCredsError: 'Invalid credentials with the provider'

Can you please have a look?
                
> Implement support for vCloud v1.5
> ---------------------------------
>
>                 Key: LIBCLOUD-183
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-183
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Compute
>    Affects Versions: 0.9.1
>            Reporter: Michal Galet
>         Attachments: LIBCLOUD-183-vcloud_1_5-2.patch, 
> LIBCLOUD-183-vcloud_1_5.patch, create_node_ex_net.recommended.xml, 
> create_node_ex_net.test.txt
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> The current version of libcloud has support only for vCloud v0.8 and is 
> incompatible with the recent version of vCloud v1.5. 
> It would be nice if the newer version was supported by libcloud: 
> http://communities.vmware.com/thread/302725

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to