[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LIBCLOUD-912:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1037


> [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)

[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-912:
--

Commit b8ba6c10accdf6d9ce8a40787e2300a594437ebe in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b8ba6c1 ]

issues with LIBCLOUD-912


> [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)

[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[Alexis Lesieur (JIRA)]

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

Alexis Lesieur commented on LIBCLOUD-912:
-

Oh I'm dumb I didn't realize the PR was in response to my ticket... It's still 
too early in the morning ><

> [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)

[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[Alexis Lesieur (JIRA)]

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

Alexis Lesieur commented on LIBCLOUD-912:
-

How I couldn't find the PR during my search... Yeah the fix looks sound from my 
understanding of the issue and the little know-how I have of this code :-)
Well I guess I'll close this ticket then!

Thanks for the quick answers guys!

> [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)

[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LIBCLOUD-912:
-

GitHub user tonybaloney opened a pull request:

https://github.com/apache/libcloud/pull/1037

[WIP] issues with OpenStack auth raised in LIBCLOUD-912 and LIBCLOUD-904

Noticed so far:

The existing test fixture returns the host as 127.0.0.1 which also happens 
to be the default host for a connection class. 

The test I just added fails to demonstrate the issue with

requests_mock.exceptions.NoMockAddress: No mock address: GET 
https://127.0.0.1/v2/1337/servers/detail



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tonybaloney/libcloud openstack_auth_passing

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1037.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1037


commit b8ba6c10accdf6d9ce8a40787e2300a594437ebe
Author: Anthony Shaw 
Date:   2017-04-21T07:21:55Z

issues with LIBCLOUD-912




> [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)

[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[Anthony Shaw (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)