You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Alexis Lesieur (JIRA)" <ji...@apache.org> on 2017/04/20 23:52:04 UTC
[jira] [Created] (LIBCLOUD-912) [python] Requests tries to connect
to 127.0.0.1:443
Alexis Lesieur created LIBCLOUD-912:
---------------------------------------
Summary: [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
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)