[
https://issues.apache.org/jira/browse/LIBCLOUD-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232417#comment-13232417
]
Tomaz Muraus commented on LIBCLOUD-165:
---------------------------------------
Ran the tests and they fail:
======================================================================
ERROR: test_gets_auth_2_0_endpoint_defaults_to_ord_region
(test.loadbalancer.test_rackspace.RackspaceUKLBTests)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/w/lc/trunk/test/loadbalancer/test_rackspace.py", line 88, in
test_gets_auth_2_0_endpoint_defaults_to_ord_region
driver.connection._populate_hosts_and_request_paths()
File "/w/lc/trunk/libcloud/common/openstack.py", line 404, in
_populate_hosts_and_request_paths
osa.authenticate()
File "/w/lc/trunk/libcloud/common/openstack.py", line 113, in authenticate
return self.authenticate_2_0_with_password()
File "/w/lc/trunk/libcloud/common/openstack.py", line 187, in
authenticate_2_0_with_password
return self.authenticate_2_0_with_body(reqbody)
File "/w/lc/trunk/libcloud/common/openstack.py", line 193, in
authenticate_2_0_with_body
method='POST')
File "/w/lc/trunk/libcloud/common/base.py", line 562, in request
headers=headers)
File "/w/lc/trunk/test/__init__.py", line 161, in request
meth = getattr(self, meth_name)
AttributeError: 'RackspaceLBMockHttp' object has no attribute '_v2_0_tokens'
Probably just need to re-sync your branch with trunk and re-create the patch.
> Rackspace LB/DNS Drivers: Support Auth 2.0 Methods
> --------------------------------------------------
>
> Key: LIBCLOUD-165
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-165
> Project: Libcloud
> Issue Type: New Feature
> Reporter: Dave King
> Priority: Minor
> Attachments: libcloud-165.patch
>
>
> Currently the Rackspace Loadbalancer and DNS providers are not returned by
> the Rackspace Auth Service Catalog, so we do not support them with auth 2.0
> authentication.
> This adds a workaround to allow these drivers to work with auth 2.0 -- we
> should remove this workaround once these are properly returned by the service
> catalog.
--
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
