libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Shaw (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443
Date Fri, 21 Apr 2017 06:18:04 GMT

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

Anthony Shaw commented on LIBCLOUD-912:
---------------------------------------

thanks for raising this. We need to get it fixed.

Can you give me a code snippet about how you instantiate the driver and what arguments you
use so I can reproduce it?

When you say Rackspace/openstack are you using the rackspace driver or the openstack one directly?

The behaviour you're seeing is because the OpenStack driver creates 2 connections, one to
the API and one to the authentication endpoint, the second is created after instantiation
of the first. If you see 127.0.0.1, thats the default host address (although it should be
none or something more obvious that it's broken).
I assume what's happening is the host isn't being passed to the second connection class. 

> [python] Requests tries to connect to 127.0.0.1:443
> ---------------------------------------------------
>
>                 Key: LIBCLOUD-912
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-912
>             Project: Libcloud
>          Issue Type: Bug
>         Environment: python 2.7
> apache-libcloud==2.0.0rc2
>            Reporter: Alexis Lesieur
>              Labels: newbie, python
>
> Hi!
> Sorry if this story is not created properly.
> I'm not that familiar with how you guys manage your Jira. Feel free to give me directions
or just modify the ticket :-)
> So we have been trying to upgrade the version of our libcloud python package, but it
breaks for our rackspace/openstack environment.
> I have been digging for a while and I couldn't find where the difference was between
1.x.x and 2.0.0rc2.
> Observed behavior:
> 1.x.x:
> 3 connections are created:
> - to 127.0.0.1:443
> - to host:3000 (ex_force_auth_url)
> - to host:8774/v2/... (don't know where it comes from)
> 2.0.0rc2:
> 2 connections
> - to 127.0.0.1:443
> - to host:3000 (ex_force_auth_url)
> and the last connection is done using 127.0.0.1:443 again, using the same connector created
in the first one
> I don't understand the change in behavior between the two versions.
> I tried use the ex_force_base_url flag, and while it does look like the path of that
url is respected, the host is always replaced by 127.0.0.1.
> Any idea of what is happening?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message